Managing Active Directory can get complicated. Often, the native tools for managing AD are just not up to the task. The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.
Course Of The Month
2 days, 1 hour left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
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 about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
| Title | # Comments | Views | Activity |
|---|---|---|---|
| VMWare 101 | 9 | 101 | |
| Server 2008 R2 has no more space on C: (OS) drive | 21 | 96 | |
| Windows Server 2003 STD SP2 as a member server of 2016 domain | 11 | 97 | |
| Writing reports to a script | 7 | 34 |
A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This Micro Tutorial will give you a introduction in two parts how to utilize Windows Live Movie Maker to its maximum editing capability.
This will be demonstrated using Windows Live Movie Maker on Windows 7 operating system.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7.
Start the SARDU utility:
Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
Suggested Courses
Course of the Month2 days, 1 hour left to enroll
710 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.