I have a problem that im using Active Directory in Win2k Server, when domain users logon to workstations they can't open sql server databases, SQL server is local installed on Workstation and operating system is XP.
When i give administrator rights to users the sql server works fine.
Tell me is there is a way to use sql server without giving to the user administrative rights?
thanksYou need to login as the account that the SQL Server is running in on their boxes (set up a SQL Server "account". You then need to go into SQL Server while logged in as this account and add Domain Users as a login in SQL Server and grant permissions. They can then login and do what they need to do.
Showing posts with label win2k. Show all posts
Showing posts with label win2k. Show all posts
Sunday, February 26, 2012
Domain to Workgroup connections
Hello everyone,
Here's the setup:
I'm trying to get an basic ADO application on my
workstation (Win2K Pro, on a domain), to talk to SQL 2000
on a server (Win2K Server, on a workgroup all by itself).
The SQL server is using Windows Authentication.
Any ideas how I can get this to work? Our application is
capable of 'impersonating' other users, but when I get it
to impersonate MYSERVER\Administrator it just says the
user id / password is invalid.
Can't get query analyser to talk to the server at all.
Thanks,
Mark.
The only way to make this work is to have identical usernames and password
on both machines. In other words, the Administrator account on the Worgroup
machine has to have the same password on the MYSERVER domain. This should
allow passthrough authentication to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Here's the setup:
I'm trying to get an basic ADO application on my
workstation (Win2K Pro, on a domain), to talk to SQL 2000
on a server (Win2K Server, on a workgroup all by itself).
The SQL server is using Windows Authentication.
Any ideas how I can get this to work? Our application is
capable of 'impersonating' other users, but when I get it
to impersonate MYSERVER\Administrator it just says the
user id / password is invalid.
Can't get query analyser to talk to the server at all.
Thanks,
Mark.
The only way to make this work is to have identical usernames and password
on both machines. In other words, the Administrator account on the Worgroup
machine has to have the same password on the MYSERVER domain. This should
allow passthrough authentication to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Domain to workgroup connections
Hello everyone,
Here's the setup:
I'm trying to get a basic ADO application on my
workstation (Win2K Pro, on a domain), to talk to SQL 2000
on a server (Win2K Server, on a workgroup all by itself).
The SQL server is using Windows Authentication.
Any ideas how I can get this to work? Our application is
capable of 'impersonating' other users, but when I get it
to impersonate MYSERVER\Administrator it just says the
user id / password is invalid.
Can't get query analyser to talk to the server at all.
Thanks,
Mark.This may be a Windows authenication issue alone. If you set up a local accou
nt on the workstation, then set up the same local account with the same pass
word on the server, then run your app with the local account. This setup wil
l allow your workstatino to
talk to the server (I'd try to get query analyser to work under this configu
ration first). This is a feature of Windows to allow standalone computers to
authenicate users.
Don't know how your app implements 'impersonating'. So 'impersonating' the l
ocal account under your app may or may not work.
-- Mark Hutchings wrote: --
Hello everyone,
Here's the setup:
I'm trying to get a basic ADO application on my
workstation (Win2K Pro, on a domain), to talk to SQL 2000
on a server (Win2K Server, on a workgroup all by itself).
The SQL server is using Windows Authentication.
Any ideas how I can get this to work? Our application is
capable of 'impersonating' other users, but when I get it
to impersonate MYSERVER\Administrator it just says the
user id / password is invalid.
Can't get query analyser to talk to the server at all.
Thanks,
Mark.
Here's the setup:
I'm trying to get a basic ADO application on my
workstation (Win2K Pro, on a domain), to talk to SQL 2000
on a server (Win2K Server, on a workgroup all by itself).
The SQL server is using Windows Authentication.
Any ideas how I can get this to work? Our application is
capable of 'impersonating' other users, but when I get it
to impersonate MYSERVER\Administrator it just says the
user id / password is invalid.
Can't get query analyser to talk to the server at all.
Thanks,
Mark.This may be a Windows authenication issue alone. If you set up a local accou
nt on the workstation, then set up the same local account with the same pass
word on the server, then run your app with the local account. This setup wil
l allow your workstatino to
talk to the server (I'd try to get query analyser to work under this configu
ration first). This is a feature of Windows to allow standalone computers to
authenicate users.
Don't know how your app implements 'impersonating'. So 'impersonating' the l
ocal account under your app may or may not work.
-- Mark Hutchings wrote: --
Hello everyone,
Here's the setup:
I'm trying to get a basic ADO application on my
workstation (Win2K Pro, on a domain), to talk to SQL 2000
on a server (Win2K Server, on a workgroup all by itself).
The SQL server is using Windows Authentication.
Any ideas how I can get this to work? Our application is
capable of 'impersonating' other users, but when I get it
to impersonate MYSERVER\Administrator it just says the
user id / password is invalid.
Can't get query analyser to talk to the server at all.
Thanks,
Mark.
Friday, February 24, 2012
Domain change has affected SQL need help
Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question :(
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question :(
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> > Hey,
> >
> > One of my clients has migrated from an old NT domain to an AD domain with
> > Win2K servers. When the migration was performed, SQL 7.0 came across as
> > well,
> > but now displays some strange characteristics. NT authentication no longer
> > works, only SQL authentication.
> > The MS Search service does not start but I have an article to fix this.
> >
> > Do I need to do anything else to SQL besides the MS Search service to get
> > SQL seeing the new domain correctly?
> >
> > I was never involved in the move of SQL, and now this damn server runs a
> > mission-critical CRM package on SQL that can in no way be interupted or go
> > down during the day, and rebuilding is out of the question :(
> >
> > Any help would be appreciated.
> > SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> >
> > Joe
>
>
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question :(
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question :(
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> > Hey,
> >
> > One of my clients has migrated from an old NT domain to an AD domain with
> > Win2K servers. When the migration was performed, SQL 7.0 came across as
> > well,
> > but now displays some strange characteristics. NT authentication no longer
> > works, only SQL authentication.
> > The MS Search service does not start but I have an article to fix this.
> >
> > Do I need to do anything else to SQL besides the MS Search service to get
> > SQL seeing the new domain correctly?
> >
> > I was never involved in the move of SQL, and now this damn server runs a
> > mission-critical CRM package on SQL that can in no way be interupted or go
> > down during the day, and rebuilding is out of the question :(
> >
> > Any help would be appreciated.
> > SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> >
> > Joe
>
>
Subscribe to:
Posts (Atom)