Dcgetdcnamegc_server_required Call Failed Error 1355
Contents |
360 games PC games dsgetdcname call failed error 1355 Windows games Windows phone games Entertainment All Entertainment dcgetdcname gc server required call failed Movies & TV Music Business & Education Business Students & educators dcdiag failed test locatorcheck Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet all gc are down error 1355 Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Error 1355 Server 2012
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered
The Server Holding The Pdc Role Is Down Error 1355
by: A Global Catalog Server could not be located - fatal error:dsgetdcname call failed, error 1355 server 2012 All GC's are down. Windows Server > Directory Services Question 0 Sign in to vote Im dcgetdcname(time_server) call failed error 1355 all out of ideas. I have two DC's that both fail DCDIAG with the following adn my exchange services wont come online due to this. please https://support.microsoft.com/en-us/kb/958804 help!Starting test: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. PDC Name: \\xx.xxxxx.xxxx ( servername and domain are correct) Locator Flags: 0xe00001fd Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role https://social.technet.microsoft.com/Forums/windows/en-US/a28c7d65-6591-4d61-81ba-b9cfe08ec734/a-global-catalog-server-could-not-be-located-all-gcs-are-down?forum=winserverDS is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355 A KDC could not be located - All the KDCs are down.Both Dc's are GC's and users can log on to either DC. Sunday, November 16, 2008 9:52 PM Reply | Quote Answers 2 Sign in to vote Some troubleshooting ideas:0. Check if the DCs can resolve each other using their DNSHostName. If not, this indicates some DNS misconfiguration -- you need to fix that first.1. Check if the both the DCs are pointing to the same DNS server (or DNS servers that are replica of each other). Run: "ipconfig /all" and check its output. If not, correct the DNS client settings and run dcdiag after sometime.2. Check if dynamic updates are "turned on" on the DNS server.3. Try re-registering the DCs SRV records by either restarting netlogon service or by running the following comm
Off on What to do when the Domain Controller Can't find its domain! PROBLEM: Users unable to login to the domain - http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ DCs not replicating RESOLUTION: => Set the RPC Locator service to Automatic http://blog.shiraj.com/2009/09/dcgetdcnametime_server-call-failed-error-1355/ and started on the PDC. => Still DCdiag gave errors of 1355. => Ran dcdiag on both PDC and BDC - both showed problems with sysvol and netlogon shares => Checked and found that both servers did not have sysvol and netlogon shared => Found that the SYSVOL was error 1355 shared as SYSVOLa - unshared it as it looked like manually shared. => Checked the PDC server and found that the Policies and Scripts were under the NTFRS-PRE-Existing folder => Stopped FRS Service on the BDC and PDC servers => Backed the policies and scripts from ntfrs-pre-existing folders to a folder on the desktop on PDC => Copied it on call failed error to the SYSVOL\sysvol folder => Started the FRS Service only on PDC => The sysvol and netlogon shares did not get created. => Stopped FRS Service again on PDC => On registry modified the following : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d4 => Started the FRS service on PDC => Got Event id : 13516 NTFRS on the PDC File replication service event log => On the BDC modified the registry : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d2 => Started FRS Service on BDC => Got Event id : 13516 NTFRS on the BDC File Replication service event log => Checked replication using repadmin /syncall - looks fine on both servers => Ran dcdiag /q on BDC and got no errors => Ran dcdiag /q on PDC and got one warning of 13508 and 13509 being reported on the eventlogs => Restarted FRS service on the PDC and reran dcdiag /q - got no errors now => All looks fine I researched the Event ID received from the following portion of a dcdiag on PDC: Starting test: Fsmo
failed, error 1355 A Good Time Server could not be located. ----- Quick resolution worked for me changing time server: The procedure for doing this on a PDC Emulator running Windows Server 2003 in the forest root domain is as follows. Open Registry Editor (regedit.exe) and configure the following registry entries: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type This registry entry determines which peers W32Time will accept synchronization from. Change this REG_SZ value from NT5DS to NTP so the PDC Emulator synchronizes from the list of reliable time servers specified in the NtpServer registry entry described below. HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags This registry entry controls whether the local computer is marked as a reliable time server (which is only possible if the previous registry entry is set to NTP as described above). Change this REG_DWORD value from 10 to 5 here. HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer This registry entry specifies a space-delimited list of stratum 1 time servers from which the local computer can obtain reliable time stamps. The list may consist of one or more DNS names or IP addresses (if DNS names are used then you must append ,0x1 to the end of each DNS name). For example, to synchronize the PDC Emulator in your forest root domain with tock.usno.navy.mil, an open-access SNTP time server run by the United States Naval Observatory, change the value of the NtpServer registry entry from time.windows.com,0x1 to tock.usno.navy.mil,0x1 here. Alternatively, you can specify the IP address of this time server, which is 192.5.41.209 instead. Now stop and restart the Windows Time service using the following commands: net stop w32time net start w32time Tagged with: Categorised as: Microsoft, Networking, Windows Upgrade Leave a Reply Cancel replyYou must be logged in to post a comment. Search for: September 2009 M T W T F S S « Aug Oct » 123456 78910111213 14151617181920 21222324252627 282930 Categories App V blogmail Cisco Exchange Hardware/Software Juniper Linux/OSX LYNC Microsoft Networking OS X Outlook Password Recovery Server OS Virtual Infra