We help IT Professionals succeed at work.

SBS 2003 to SBS 2011 Migration - Getting "There are currently no logon servers to process this request"

jdancel asked
We completed a SBS 2003 to SBS 2011 migration.  After we demoted the original SBS 2003 server and removed it from the enterprise, some of the workstations started having problems logging in.  When they tried to logon an error was returned saying "There are currently no logon servers to process the request."  It seems like a DNS error but I can't figure out what the problem is.

We've checked the Primary DNS server settings using ipconfig /all on all the troubled workstations.  The settings are correct.  The DNS is set by the DHCP.  The clients are all Win7 32-bit, except one which 64-bit.

We've tried ipconfig /flushdns, ipconfig /regusterdns, net stop netlogon, net start netlogon.

 Your suggestions are greatly appreciated.
Watch Question

Have you tried removing the workstaions from the domain, rebooting, login locally with admin and adding them to the domain again?  Are the workstation names showing up in the OU on your SBS server?
Technical Lead
Top Expert 2011
Ensure the following on DC:
1. Each DC / DNS server points to its private IP address as primary DNS server and other remote/local DNS servers as secondary in TCP/IP properties.
2. Each DC has just one IP address and single network adapter is enabled.
3. Contact your ISP and get valid DNS IPs from them and add it in to the forwarders, Do not set public DNS server in TCP/IP setting of DC.
4. Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.
Do not put private DNS IP addresses in forwarder list.
5.Assign static IP address to DC if IP address is assigned by DHCP server to DC.It is strongly not recommended.

-->> IP configuration on clients and member servers:
1. Each workstation/member server should point to local DNS server as primary DNS and other remote DNS servers as secondary.
2. Do not set public DNS server in TCP/IP setting of WS.

Post the dcdiag /q and repadmin /replsum for any erros.Also check the event log for any errors on DC and post the same.