Click to See Complete Forum and Search --> : Logging onto Domain nor recognized by member server.
Allan Snow
10-07-1999, 02:21 PM
We have three servers in DomainA;
ServerA - PDC
ServerB - BDC
ServerC - member server
My NT Workstation is logged onto DomainA as UserA.
If I use Network Neighborhood and click on ServerA (the PDC) , it shows me
all the shares and doesn't ask me for any username password. Similarily if I
click on ServerB (the BDC).
However if I click on ServerC (member server) . It wants a
username/password. Why doesn't ServerC realize that I am already logged onto
the Domain (ie check with a domain controller) rather than ask me to log on
again. Also when I specify the username, I have to include the domain i.e.
"DomainAUserA". Just "UserA" won't work.
The problem is ServerC is soon to be a production SQLServer and has
integrated security. The clients log onto the domain, however, (I'm
speculating that) when they run a SQL application, SQLServer will not see an
NT login for verification. I havn't run ito this problem before as my
SQLServers have up to now also been domain controllers.
Anybody know what is happening and what the solution, if any, there is.
Glory
10-07-1999, 08:50 PM
We have a similar setup. SQL Server is a Member Server running accounting software. The only time I got the same problem is when I don't have permission to the server itself. As a Domain Admin, I can double-click on the member server and it doesn't ask me to "connect as". But when I try to access/double-click on the member server as regular Joe User that's not even a member of the Accounting group (Accounting group has permission to the member server), I get a "connect as" prompt. You may want to check your permissions and that the member server is a member of the same domain where your PDC and BDC are.
Hope this helps. Hope to know either way what worked for you.
Glory.
------------
Allan Snow at 10/7/99 3:21:51 PM
We have three servers in DomainA;
ServerA - PDC
ServerB - BDC
ServerC - member server
My NT Workstation is logged onto DomainA as UserA.
If I use Network Neighborhood and click on ServerA (the PDC) , it shows me
all the shares and doesn't ask me for any username password. Similarily if I
click on ServerB (the BDC).
However if I click on ServerC (member server) . It wants a
username/password. Why doesn't ServerC realize that I am already logged onto
the Domain (ie check with a domain controller) rather than ask me to log on
again. Also when I specify the username, I have to include the domain i.e.
"DomainAUserA". Just "UserA" won't work.
The problem is ServerC is soon to be a production SQLServer and has
integrated security. The clients log onto the domain, however, (I'm
speculating that) when they run a SQL application, SQLServer will not see an
NT login for verification. I havn't run ito this problem before as my
SQLServers have up to now also been domain controllers.
Anybody know what is happening and what the solution, if any, there is.
------------
Allan Snow at 10/7/99 3:21:51 PM
We have three servers in DomainA;
ServerA - PDC
ServerB - BDC
ServerC - member server
My NT Workstation is logged onto DomainA as UserA.
If I use Network Neighborhood and click on ServerA (the PDC) , it shows me
all the shares and doesn't ask me for any username password. Similarily if I
click on ServerB (the BDC).
However if I click on ServerC (member server) . It wants a
username/password. Why doesn't ServerC realize that I am already logged onto
the Domain (ie check with a domain controller) rather than ask me to log on
again. Also when I specify the username, I have to include the domain i.e.
"DomainAUserA". Just "UserA" won't work.
The problem is ServerC is soon to be a production SQLServer and has
integrated security. The clients log onto the domain, however, (I'm
speculating that) when they run a SQL application, SQLServer will not see an
NT login for verification. I havn't run ito this problem before as my
SQLServers have up to now also been domain controllers.
Anybody know what is happening and what the solution, if any, there is.
Drew Sweeney
10-13-1999, 09:03 AM
Allan,
I'm not sure of all of the details yet, but from what you describe, it sounds like ServerC is acting more like a server that is in a Workgroup than a Member server in your domain.
Verify that the server is not just in a Workgroup with the same name as your domain. If it is, then you need to see about 'joining the domain'. I've never had to do this, but you may have to re-install NT Server to do that.
Good luck.
drew ;-)
Allan Snow
10-13-1999, 12:30 PM
------------
Allan Snow at 10/7/99 3:21:51 PM
We have three servers in DomainA;
ServerA - PDC
ServerB - BDC
ServerC - member server
My NT Workstation is logged onto DomainA as UserA.
If I use Network Neighborhood and click on ServerA (the PDC) , it shows me
all the shares and doesn't ask me for any username password. Similarily if I
click on ServerB (the BDC).
However if I click on ServerC (member server) . It wants a
username/password. Why doesn't ServerC realize that I am already logged onto
the Domain (ie check with a domain controller) rather than ask me to log on
again. Also when I specify the username, I have to include the domain i.e.
"DomainAUserA". Just "UserA" won't work.
The problem is ServerC is soon to be a production SQLServer and has
integrated security. The clients log onto the domain, however, (I'm
speculating that) when they run a SQL application, SQLServer will not see an
NT login for verification. I havn't run ito this problem before as my
SQLServers have up to now also been domain controllers.
Anybody know what is happening and what the solution, if any, there is.
Alklan Sbow
10-13-1999, 12:38 PM
More information.
1. Looking at the Server Manager. ServerC is definitely a Member Server of DomainA.
2. I can log onto the ServerC console with username UserA with no problem.
3. On ServerC if I bring up User Manager for Domains. I see all the Users/Groups in DomainA
4. From a Win95 PC that is logged onto DomainA and click on Network Neigborhood and ServerC, I don't get prompted for username/password.
5. From my NT Workstation, which is logged onto DomainA and click on Network Neighborhood and ServerC, I do get prompted for username/password.
6. Both the Win95 PC and my NT W/S are using Novell's Client 32.
------------
Allan Snow at 10/7/99 3:21:51 PM
We have three servers in DomainA;
ServerA - PDC
ServerB - BDC
ServerC - member server
My NT Workstation is logged onto DomainA as UserA.
If I use Network Neighborhood and click on ServerA (the PDC) , it shows me
all the shares and doesn't ask me for any username password. Similarily if I
click on ServerB (the BDC).
However if I click on ServerC (member server) . It wants a
username/password. Why doesn't ServerC realize that I am already logged onto
the Domain (ie check with a domain controller) rather than ask me to log on
again. Also when I specify the username, I have to include the domain i.e.
"DomainAUserA". Just "UserA" won't work.
The problem is ServerC is soon to be a production SQLServer and has
integrated security. The clients log onto the domain, however, (I'm
speculating that) when they run a SQL application, SQLServer will not see an
NT login for verification. I havn't run ito this problem before as my
SQLServers have up to now also been domain controllers.
Anybody know what is happening and what the solution, if any, there is.
Allan Snow
10-14-1999, 02:25 PM
Ooooops. I finally figured out what the problem was. With the Novell client you have to pull down on the Details button to set (and see) the domain to log onto. I believed I've been logging onto DomainA, however all this time I've only been logging on locally to my workstation.
------------
Allan Snow at 10/7/99 3:21:51 PM
We have three servers in DomainA;
ServerA - PDC
ServerB - BDC
ServerC - member server
My NT Workstation is logged onto DomainA as UserA.
If I use Network Neighborhood and click on ServerA (the PDC) , it shows me
all the shares and doesn't ask me for any username password. Similarily if I
click on ServerB (the BDC).
However if I click on ServerC (member server) . It wants a
username/password. Why doesn't ServerC realize that I am already logged onto
the Domain (ie check with a domain controller) rather than ask me to log on
again. Also when I specify the username, I have to include the domain i.e.
"DomainAUserA". Just "UserA" won't work.
The problem is ServerC is soon to be a production SQLServer and has
integrated security. The clients log onto the domain, however, (I'm
speculating that) when they run a SQL application, SQLServer will not see an
NT login for verification. I havn't run ito this problem before as my
SQLServers have up to now also been domain controllers.
Anybody know what is happening and what the solution, if any, there is.