Fsmocheck Error 1355 Gc_server_required
Contents |
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a warning dcgetdcname(pdc_required) call failed error 1355 Freelance Project Hire for a Full Time Job Ways to Get Help the server holding the pdc role is down error 1355 Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing dcdiag failed test locatorcheck Store Headlines Experts Exchange > Questions > how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" Want to Advertise Here? Solved how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" Posted on 2012-02-02 warning dcgetdcname(time_server) call failed error 1355 Active Directory Windows Server 2003 2 Verified Solutions 6 Comments 9,922 Views Last Modified: 2012-02-06 hello in attached document you can see result of "DCDIAG /v" (log-dcdiag.txt) in attached document you can see result of "dnslint /ad 127.0.0.1 /s 192.168.0.14 /v" (dnslint.txt) I have make this too : netdom query fsmo and the result of this is : Schema owner
Error 1355 Server 2012
dc-wnc1hnl0oyu.lci.local Domain role owner dc-wnc1hnl0oyu.lci.local PDC role dc-wnc1hnl0oyu.lci.local RID pool manager dc-wnc1hnl0oyu.lci.local Infrastructure owner dc-wnc1hnl0oyu.lci.local The command completed successfully. I have this problem after crash of my PDC I have forcer promot for give All role at my seconde DC but now I have this error "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" how can solved this ? thx dnslint.txt log-dcdiag.txt 0 Question by:thierry91 Facebook Twitter LinkedIn Google LVL 26 Best Solution byLeon Fester Verify that this server is a global catalog, run repadmin /options You should see at least "Current Options: IS_GC" If not, then following instructions from here http://support.microsoft.com/kb/313994 Go to Solution 6 Comments LVL 17 Overall: Level 17 Active Directory 12 Windows Server 2003 9 Message Expert Comment by:Premkumar Yogeswaran2012-02-03 I member checked a blog for this issue, which helped my friend.... http://blog.shiraj.com/index.php/2009/09/dcgetdcnametime_server-call-failed-error-1355/ Check this HTH... regards, Prem 0 LVL 10 Overall: Level 10 Active D
360 games PC games
All Gc Are Down Error 1355
Windows games Windows phone games Entertainment All Entertainment dsgetdcname call failed, error 1355 Movies & TV Music Business & Education Business Students & educators fatal error:dsgetdcname call failed, error 1355 server 2012 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://www.experts-exchange.com/questions/27568710/how-solve-DcGetDcName-GC-SERVER-REQUIRED-call-failed-error-1355.html 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 https://support.microsoft.com/en-us/kb/958804 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
Off on What to do when the Domain Controller Can't find its domain! PROBLEM: Users unable to login to the domain - DCs not replicating RESOLUTION: => Set the http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ RPC Locator service to Automatic 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 http://www.pcreview.co.uk/threads/warning-dcgetdcname-pdc_required-call-failed-error-1355.2167383/ => Checked and found that both servers did not have sysvol and netlogon shared => Found that the SYSVOL was shared as SYSVOLa - unshared it as it looked like manually shared. => Checked error 1355 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 to the SYSVOL\sysvol folder => Started the FRS Service only on PDC => The sysvol and netlogon shares did not get call failed error 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: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. http://technet2.microsoft.com/windowsserver/en/library/ce8890cf-ef46-4931-8e4a-2fc5b4ddb0471033.mspx?mfr=true http://technet2.microsoft.com/windowsserver/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx?mfr=tr
3, 2005. zealousworks Guest I have an native Windows 2000 Active Directory domain with a number of remote sites, and I am trying to diagnose some Netlogon error messages appearing in the event log of the remote domain controllers: Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5719 Date: 03/10/2005 Time: 11:08:33 User: N/A Computer: SITE02AD01 Description: No Windows NT or Windows 2000 Domain Controller is available for domain WALKERS. The following error occurred: There are currently no logon servers available to service the logon request. Data: 0000: 5e 00 00 c0 ^..À Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 3096 Date: 03/10/2005 Time: 15:55:20 User: N/A Computer: SITE02AD01 Description: The Windows NT domain controller for this domain could not be located. If I run 'dcdiag /v' on the domain controller, the following is listed for the FsmoCheck Starting test: FsmoCheck GC Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. Time Server Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc Preferred Time Server Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc KDC Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc ......................... domain.co.uk failed test FsmoCheck But if I run 'netdom query fsmo', the following is reported: Schema owner site01ad01.walkers.co.uk Domain role owner site01ad01.walkers.co.uk PDC role site01ad02.walkers.co.uk RID pool manager site01ad02.walkers.co.uk Infrastructure owner site01ad02.walkers.co.uk The command completed successfully. Any suggestions appreciated! Regards, Andrew zealousworks, Oct 3, 2005 #1 Advertisements Paul Bergson Guest Has the sysvol share come online and/or is