Windows 2008 R2 Server Not Using Domain Controller as Logon Server

I have a Windows 2008 R2 server that joined the domain without issue. However, it is no longer using this domain controller as the logon server. It instead is using itself as the logon server. It can ping the domain controller and browse its file shares without issue.

This new server is actually going to be a Lync 2013 server and I noticed this problem when I went to prepare the Active Directory Schema. I received a message saying:

      "Not Available: Failure occurred while attempting to check the schema state. Please ensure Active Directory is reachable"

There is actually only one domain controller on the domain right now that is on the local subnet with the new Lync Server.

Another potential symptom of the problem is that while I can ping the domain controller from the Lync server, I cannot ping the Lync Server from the domain controller. Using a Wireshark capture it shows the ping requests getting to the Lync server but the Lync server doesn't send any pings back.

 Does anyone have any suggestions on what I can do to resolve?
Rob SandersAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Will SzymkowskiSenior Solution ArchitectCommented:
How do you know that it is using itself as the logon server? Are you login into the Lync server with the Administrator password? If this is true, by default when you do this it will logon locally. Have you tried a different account?

Also when you are logged into the DC run the following command...
set logonserver <press enter>

This will tell you what server you are using as your logon server.

Also try logging into the machine with another account as well and perfomr the same command above.

To upgrade the Schema, you need to be part of the Schema Admins group as well for this to work.


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
Rob SandersAuthor Commented:
I was making a silly mistake. I wasn't logged on to the server as a domain administrator, only a local administrator. Once I logged on as a domain administrator, the problem was resolved.
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.