Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.
Windows doesn't recognize domain name until 60 seconds after startup
I have an odd problem that I've been unable to find an exact match to in any other topic. We have some new Windows 7 desktops with SSDs that boot fast (<10 seconds). The fast boot time may or may not be the cause. The problem seems to be that it tries to apply group policy software installs before it knows what the domain name is.
***Event ID: 1129
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition....***
***Event ID: 5719
This computer was not able to set up a secure session with a domain controller in domain ...***
When the user tries to log on right away, the logon scripts also fail to go off and mapped drives depending on the domain name/DFS fail to map. Other mapped drives just using server names (including the user's home directory) work fine. If we wait 30-60 seconds before logging in or trying to map the drive, it works fine. It doesn't seem to have a problem being authenticated, just recognizing the official domain name.
I've tried dis-joining and rejoining the domain (2008 DC at 2003 functional level, multiple DCs available), sysprep, updating network card drivers, trying the second network card, clearing the DNS cache, static IP, disabling IPv6, MS Hotfix 372638, and setting the policy to wait for network connectivity before logon. About the only thing I haven't tried is cloning the disk to a standard hard drive. Any other ideas would be appreciated!
***Event ID: 1129
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition....***
***Event ID: 5719
This computer was not able to set up a secure session with a domain controller in domain ...***
When the user tries to log on right away, the logon scripts also fail to go off and mapped drives depending on the domain name/DFS fail to map. Other mapped drives just using server names (including the user's home directory) work fine. If we wait 30-60 seconds before logging in or trying to map the drive, it works fine. It doesn't seem to have a problem being authenticated, just recognizing the official domain name.
I've tried dis-joining and rejoining the domain (2008 DC at 2003 functional level, multiple DCs available), sysprep, updating network card drivers, trying the second network card, clearing the DNS cache, static IP, disabling IPv6, MS Hotfix 372638, and setting the policy to wait for network connectivity before logon. About the only thing I haven't tried is cloning the disk to a standard hard drive. Any other ideas would be appreciated!
Who is Participating?
The solution ended up being creating a host entry in DNS for the NetBios domain name with the IP of one of our domain controllers. Since then, everything has worked fine.
The description certainly fits close our issue, but I tried it all the way up to 180 and no change. It doesn't wait for more than a few seconds before showing the logon prompt, so I'm not sure if it's even paying attention to it.
Okay, have you verified if the GPO to wait for the network is being applied successfully to the workstations?
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.
-
Course of the Month8 days, 23 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
