logon process

[Chai]

Hi there,

Did anyone know what the steps/ processes from client PC
to logon to DC?

For example, when client logon - what happen? (check the
DNS? What ports open? how the client define which DC to
connectted when have multiple DC). How DC respond?

Cause my network is split to multi segment and each
segment have it own DC (for fast logon purposes). However,
it seem like all the client PCs only want to logon
(authenticated with the first DC - main server and cause
it logon slow!!

I have configure the segment DC as GC, DNS Server +
records also no problems, network connection fine.

Any ideas?

Thanks

 

[Simon Geary]

2000 and XP clients use DNS to locate the nearest domain controller so if
you have users who are authenticating against a remote DC when there is one
locally then DNS is the place to look. You can check what server you have
authenticated against by running 'set l' or
'echo %logonserver%' at the command line.

You can check the following to start with:
Have you added all your subnets in the AD Sites & Services console and are
the local DC's for each subnet correctly associated with it?
Do you have DNS running on each site and are all the clients configured to
use the local DNS as the primary?
Are all your DC's Global Catalogue servers?
On your DNS servers, are all the AD records correctly configured, eg the
_msdcs folder etc.
Any errors running dcdiag /v or netdiag /v on the DC's?

 

[Tony Murray [MVP]]

The steps are described in the following KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-
US;247811

From what you describe it sounds like the problem could
be to do with your site definitions. If you want certain
clients to use a specific DC for logon you should put the
DC in a separate site and associate the relevant subnets
to that site.

Tony
www.activedir.org