Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Solved
Windows doesn't recognize domain name until 60 seconds after startup
Posted on 2013-01-15
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!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
2
7 Comments
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?
I opened a case with Microsoft. Their take is that it's a problem with the computer recognizing the NetBios name for the domain. No solution yet.
Featured Post
Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
Active Directory can easily get cluttered with unused service, user and computer accounts. In this article, I will show you the way I like to implement ADCleanup..
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…
- Windows 10
- Windows Vista
- Windows 8
- Windows OS
- Windows 7
- Microsoft Legacy OS, Windows XP, *Scripts, *task scheduler
Attackers love to prey on accounts that have privileges.
Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Suggested Courses
Course of the Month6 days, 2 hours left to enroll
688 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.