Specifying Logon DC in multisite domain

[Joel Justen]

We have a single domain in our company spread over several sites. These sites range in speed from 56k up to 1280k. Currently, when someone logs in under Windows 2000 Pro, you never know which DC at which site you are going to get to handle your logon request.

Does anyone know of a way to specify the logon server to use (local preferred!)?

Thanks
Joel J.

[Nigel]

Have you setup sites and subnets ?

A Windows 2000 pro box will try and authenticate in it's local site first.


------------
Joel Justen at 4/2/01 1:11:48 PM



We have a single domain in our company spread over several sites. These sites range in speed from 56k up to 1280k. Currently, when someone logs in under Windows 2000 Pro, you never know which DC at which site you are going to get to handle your logon request.

Does anyone know of a way to specify the logon server to use (local preferred!)?

Thanks
Joel J.

[mjdenn]

------------
Joel Justen at 4/2/01 1:11:48 PM
Joel

We are seeing the same issue. While our problem isn't solved yet my thinking is that DHCP/WINS resolution might just be the problem. In our network the DHCP scopes are set up with a Netbios Node type of H(0x8)hex. H Node will try for a WINS resolution before doing a local broadcast. Changing the node type to mixed node (0x4) would reverse this process. We haven't made this change yet so it's just an uneducated guess at this point.

Mjdenn


We have a single domain in our company spread over several sites. These sites range in speed from 56k up to 1280k. Currently, when someone logs in under Windows 2000 Pro, you never know which DC at which site you are going to get to handle your logon request.

Does anyone know of a way to specify the logon server to use (local preferred!)?

Thanks
Joel J.

[Mark Liedtke]

I think the Sites and Subnet suggestion will fix this. If you are using Win9x or NT clients, you need the AD client installed on them. There are also some things that you can do in DNS to prioritize DC's (sorta like MX records) but if you dont have the AD client software on the older OS's this wont help.


------------
mjdenn at 8/1/01 3:24:43 PM




------------
Joel Justen at 4/2/01 1:11:48 PM
Joel

We are seeing the same issue. While our problem isn't solved yet my thinking is that DHCP/WINS resolution might just be the problem. In our network the DHCP scopes are set up with a Netbios Node type of H(0x8)hex. H Node will try for a WINS resolution before doing a local broadcast. Changing the node type to mixed node (0x4) would reverse this process. We haven't made this change yet so it's just an uneducated guess at this point.

Mjdenn


We have a single domain in our company spread over several sites. These sites range in speed from 56k up to 1280k. Currently, when someone logs in under Windows 2000 Pro, you never know which DC at which site you are going to get to handle your logon request.

Does anyone know of a way to specify the logon server to use (local preferred!)?

Thanks
Joel J.