This could be caused by a name resolution failure. The following errors were encountered: The processing of Group Policy failed. Why did my cron job run? When ever I try to connect, it keeps prompting me for a user... Source
Thanks, 0 Featured Post Top 6 Sources for Identifying Threat Actor TTPs Promoted by Recorded Future Understanding your enemy is essential. Looking at them in general it looks like there is some sort of problem that don't let the DCHP, DNS, GroupPolicy and other services contact the DC. I then started getting all kinds of errors. Windows could not obtain the name of a domain controller. you could check here
If this situation is happening intermittently in Windows Server 2008, the likely resolution is to apply a software patch (hotfix 961775).Questions related to hotfixes should be referred toMicrosoft Support(http://support.microsoft.com/contactus). Thank you for the suggestions anyway. After using tools to check and fix the registry the server stopped crashing.
Does the error detail "The Specified server cannot perform the requestion operation." suggest that the issue isn't actually finding a DC, but something else failing? New 25 Jan 2010 #6 Ace Fekay [MVP-DS, MCT] Guest Re: Server 2008 Standard R2 - Server unable to communicate on network "Cameron Shaw"
It looks like this machine is using a DHCP reservation rather than a static IP. Random reboot? DO this many times and analyse the result . Forum New Posts FAQ Calendar Community Member List Forum Actions Mark Forums Read Quick Links Today's Posts Tutorials Advanced Search Forum Vista Newsgroup Archive Server Newsgroups Server General Server 2008 Standard
Network & Sharing Re: Migrating from Small Business Server 2008 Standard environment to Windows Server 2008 Standard x64It is possible and I just finished testing this on a lab network environment click Determine the location of the FSMO roles by lo… Windows Server 2008 Windows Server 2012 Active Directory Advertise Here 767 members asked questions and received personalized solutions in the past 7 up vote -3 down vote This is a known bug in MS Windows when using static IP, gigabit NIC http://support.microsoft.com/kb/938449 Most people use following option to create new registry value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpIp\Parameters\ArpRetryCount Browse other questions tagged networking windows-server-2008 active-directory server-crashes or ask your own question.
Windows could not obtain the name of a domain controller. this contact form Suggested Solutions Title # Comments Views Activity How to move RedirectedFolders from Drive C to Drive D? 6 23 25d Staff want to build his own server- Suggestions and IT policy Windows could not > obtain the name of a domain controller. All rights reserved.
Computer policy could not be updated successfully. Page 1 of 3 123 Last Jump to page: Server 2008 Standard R2 - Server unable to communicate on network « Previous Thread | Next Thread » Similar Threads Thread Forum How can I figure out why GPUpdate can't find a DC? have a peek here Achieve same random number sequence on different OS with same seed Should the sole user of a *nix system have two accounts?
TechCenter Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery According to Windows Network Centre the the connection is fine is and other then the error I specified below there is nothing to indicate something is wrong. You can leave the IPv4 Loopback in place, and run an ipconfig /flushdns from the command prompt.
DCDiag is fine. Using Elemental Attunement to destroy a castle Different use of tenses in Iberian vs South American (and/or Andean) Spanish How do I unexpand a file name? This could be caused by a name resolution failure. It's included in SP2.
share|improve this answer answered Jan 13 '14 at 8:37 Santi 8612 add a comment| Did you find this question interesting? New 25 Jan 2010 #8 David Shen [MSFT] Guest RE: Server 2008 Standard R2 - Server unable to communicate on network Hello customer, The managed support service of the microsoft.public.windows.server.general is