User logging on against wrong DC

Hi all,

2003 domain running 2003/2008/2012 servers.

I have recently demoted a 2008 DC and replaced with a 2012 on a number of sites. All looks good apart from a particular user seems to authenticate against a DC on another site across the WAN and not the new local DC that is available?

This causes issues with group policy applying properly. But im not sure why the machine is doing this? has anyone seen this before?
MattAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dan McFaddenSystems EngineerCommented:
I would first run the following commands from the computer the user is working on:

1. nltest /DSGETDC:<YouDomainNameHere.Extension>

2. nslookup
2a. set type=SRV
2b. _ldap._tcp.<SiteName>._sites.dc._msdcs.<YourDomain.Ext>

#1 will tell you what DC & Site this computer/user is connecting thru.
#2 will tell you what LDAP servers are in DNS for the site

I would also verify the TCP/IP configuration on the computer. I would read thru this article and double check your Sites & Services config.

http://blogs.dirteam.com/blogs/paulbergson/archive/2010/04/19/ad-clients-not-authenticating-to-its-local-site.aspx

Dan
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Radhakrishnan RSenior Technical LeadCommented:
Hi,

As Dan said, this type of behaviour occurs due to missing SRV records. If the restart the netlogon service on the appropriate server, the SRV records creates automatically if it is missing.
0
Pramod UbheCommented:
set logonserver command will give you the name of DC that completed authentication request for that computer.
additionally check if that computer has a diff IP address which might belong to a diff. subnet. which then you can verify in AD sites and services about the DC where that subnet is mapped.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.