Logon Question

[Chris]

Ok this has been buggging me.

I have a simple little single W2K domain with three DC/GC.

In MN on subnet 192.168.1.0
In WA on subnet 192.168.2.0
In MO on subnet 192.168.3.0

Ok here is the question. Why do the MN desktop clients
use the MO server for logon? It adds about 30 seconds to
boot. MO was the last server added. Anyway I can change
this?

Thanks,
Chris

 

[ptwilliams]

First things first, check your sites to make sure there's no
misconfigurations. Is it possible that MN is assigned to .3.0 by mistake?

Also, where do the MN clients point to for DNS resolution? Are they
pointing to another subnet?


Paul.
_________________________________

 

[Joe Richards [MVP]]

What is your site/subnet configuration in Active Directory? That is how clients
figure out what DCs to use. If that is configured properly the clients should go
to the right place, if they aren't and it is configured, there is a problem that
needs to be troubleshot.

So again, back to square one, what is your site/subnet configuration?


joe

 

[Guest]

Ok getting back to this.

Default was renamed MN subnet 192.168.1.0
Site WA Subnet 192.168.2.0
Site MO Subnet 192.168.3.0

I think I used a guide from MS website when I set it up. I
don't remember.

(I don't get what the browse button on the location tab is
for. I just put in the city state manually)

DNS is set for the correct server. Dunno about this one.

The client should just say. "Hey that is a darn fast
connection to that server I will just use that one from
now on"

Chris

 

[Joe Richards [MVP]]

Do a

nltest /dsgetdc:domain.com

and look at the results to see if there is anything you didn't expect.

joe