• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 654
  • Last Modified:

Domain Controller not servicing clients in its Site

Hi guys, we have an issue concerning domain controllers that dont seem to authenticate clients that are in its site.

For example,

Site: HO
Domain Controller: AUTESTDC (This is listed as a server in the Site HO in AD Sites and Services)
Client: CLIENTPC
CLIENTPC has an IP address that is part of a subnet that this Site should service, and as listed in AD Sites and Services.

So, the following is what is happening on a regular basis.

CLIENTPC boots up, user logs on.
Instead of AUTESTDC being the %logonserver%, when you issue this command, a domain controller OUTSIDE its own SITE is the logonserver.

What we need to establish is the following:

1.Why is the client continually getting authenticated OUTSIDE its own site?
2.How can we determine the problem with the local DC (if there is a problem) to see WHY it wont be the logonserver.
3.How do we get the local DC AUTESTDC to be the local logonserver.
4.In our AD Sites and Services, the setup looks correct, so we are at a loss to understand why clients are not being authenticated locally.
5.Any test tools that we can use to fix this problem?

Any help on this greatly appreciated.


Simon

netlogon.jpg
0
Simon336697
Asked:
Simon336697
  • 3
  • 2
1 Solution
 
Renato Montenegro RusticiIT SpecialistCommented:
First, the message you uploaded is telling you that you have clients whose IP addresses does not match to any subnet created in Active Directory Sites and Services. To find out what IP addresses are involved, take a look in the netlogon.log file. It's located in the following path:

%windir%\debug\netlogon.log

For additional information about net logon logging, take a look at this document:

Enabling debug logging for the Net Logon service
http://support.microsoft.com/kb/109626

By default, you will see enough information concerning the site awareness.

That takes us to the second point. Workstations will choose the domain controllers based on the subnets you associated with sites in Active Directory Sites and Services. Make sure you setup them up correctly, including the appropriate subnet mask. If you need information about how to translate a subnet mask to a /xx format, use a subnet calculator: http://www.subnet-calculator.com

For example, the subnet mask for the ip address 192.168.128.10 with the subnet mask 255.255.255.192 would be 192.168.128.0/26 (the 26 would be in the field Mask Bits of the calculator when you select the mask 255.255.255.192).

Besides, to use site awareness you need at least a fully updated Windows XP or later.

Make sure everything is in place and tell us what you've found.
0
 
Renato Montenegro RusticiIT SpecialistCommented:
Also, make sure your clients are able to reach the domain controller. You can make a connection from the client to make sure:

\\your_desired_dc\netlogon

You can also run a dcdiag /v in the domain controller and send it back to us. If there is something unusual we will be able to tell you how to fix.
0
 
Simon336697Author Commented:
Thanks so much rmrustice, that is brilliant info.
Ill run the dcdiag and send it back.
0
 
Renato Montenegro RusticiIT SpecialistCommented:
Any news on that?
0
 
Simon336697Author Commented:
Thanks rm
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now