Windows 2003 AD

I have a small network in the office and we recently moved DHCP services to the router and shutdown a secondary AD server. We had 3 domain controllers and now we have 2.

However, I am finding a lot of systems are getting this issue now:

This computer was not able to setup a secure session with a domain controller in domain MYDOMAIN due to the following:
There are currently no login servers available to service the login request.

I have limited knowledge of AD so looking for some steps to try. I can follow directions.
LVL 7
Robert SaylorSenior DeveloperAsked:
Who is Participating?
 
James HIT DirectorCommented:
Well then those errors are due to the time difference between the second DC and primary. That should resolve those issues but I would figure out why your second DC was that far behind. It should be using the NTP of the primary as its source
0
 
James HIT DirectorCommented:
verify which server holds the FSMO roles.

Just type this in a command prompt:

NetDOM /query FSMO

This will display the current primary DC.
We will continue after you verify this.
0
 
Robert SaylorSenior DeveloperAuthor Commented:
Schema owner               server01.mydomain.corp
Domain role owner       server01.mydomain.corp
PDC role                          server01.mydomain.corp
RID pool manager         server01.mydomain.corp
Infrastructure owner    server01.mydomain.corp
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
James HIT DirectorCommented:
Can you verify the time in in sync? Is there a reason why you moved DHCP to the router and not keep it on server? I have seen errors like this due to issues with time sync and DHCP residing on Cisco devices running DHCP.
0
 
Robert SaylorSenior DeveloperAuthor Commented:
Time is correct on the 1st DC. The 2nd it was behind an hour.

The server that use to run DHCP was running out of storage. It is a old Dell server so we moved DHCP to a hardware solution instead of a software.
0
 
Robert SaylorSenior DeveloperAuthor Commented:
DHCP is being handled by our PepLink 305 load balancer.
0
 
Robert SaylorSenior DeveloperAuthor Commented:
Thanks, I will see what the secondary DC is using for NTP. I will know within 24 hours if this resolves the issue.
0
 
Robert SaylorSenior DeveloperAuthor Commented:
I think it's fixed!!! I also added server01.mydomain.corp on my router in the DNS section and another Windows 2003 server that I was reloading connected to the AD!

I think it was a combination of time and DNS.
0
 
Robert SaylorSenior DeveloperAuthor Commented:
DNS was also part of the issue.
0
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.

All Courses

From novice to tech pro — start learning today.