Active Directory Error 13508
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related
Ntfrs Error 13508
threads Remove From My Forums Answered by: FRS 13508 Error the file replication service is having trouble enabling replication 13508 - HELP!? Windows Server > Directory Services Question 0 Sign in to vote Hi. I have event id 13508 ntfrs windows 2008 r2 2 DCs, PDC (2k8) and PDC1 (2k8R2). I recently promoted PDC1 to become a DC and replication occured without error. However now I get the
Event Id 13508 Ntfrs Windows 2012 R2
FRS 13508 error and replication will not happen. Can some have a look at my dcdiags below and tell me what is wrong. I can ping both servers from each other and they resolve correctly. I have removed our domain name and some AV errors. DCDIAG from PDC: Directory Server
Frs Event Id 13508 Without Frs Event Id 13509
Diagnosis Performing initial setup: Trying to find home server... Home Server = PDC * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\PDC Starting test: Connectivity ......................... PDC passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\PDC Starting test: Advertising Warning: PDC is not advertising as a time server. ......................... PDC failed test Advertising Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... PDC passed test FrsEvent Starting test: DFSREvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... PDC failed t
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 Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products event id 13508 ntfrs windows 2003 BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions >
Ntfrs 13508 Server 2012 R2
Active Directory FRS error 13508 in FRS Event Log Want to Advertise Here? Solved Active Directory FRS error 13508 in FRS Event Log Posted event id 13568 on 2010-08-24 Active Directory Windows Server 2003 Networking 1 Verified Solution 96 Comments 7,740 Views 1 Ratings Last Modified: 2012-05-10 Well I have been working on this problem for awhile now and I just can't seem to figure it https://social.technet.microsoft.com/Forums/windowsserver/en-US/88f45cb5-6057-4b35-815e-791cc0575263/frs-13508-error-help?forum=winserverDS out. Here is what is going on: A couple of weeks ago as I was doing some research into replacing some of my aging DCs I came across an error that I can't seem to remedy. I was running DCDIAG just to check and make sure there wasn't any errors and I found one. All tests would pass except the Netlogons test and the FRSEvent test when running DCDIAG. I get the following output for this test: Starting test: NetLogons https://www.experts-exchange.com/questions/26426708/Active-Directory-FRS-error-13508-in-FRS-Event-Log.html * Network Logons Privileges Check Unable to connect to the NETLOGON share! (\\SERVER\netlogon) [SERVER] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path.. ......................... SERVER failed test NetLogons I also fail the FRSEVENT test with the error: Starting test: frsevent * The File Replication Service Event log test There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. An Warning Event occured. EventID: 0x800034C4 Time Generated: 08/23/2010 22:49:31 (Event String could not be retrieved) ......................... SERVER failed test frsevent So I did some research and was directed towards the FRS Event Logs. Once I looked in there I saw the following error: The File Replication Service is having trouble enabling replication from
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://serverfault.com/questions/417159/new-domain-controller-is-having-trouble-replicating-from-an-existing-dc-13508-e Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags http://www.scottsavage.net/2009/01/frs-error-13508-without-13509/ Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top New Domain controller is having trouble replicating from an event id existing DC, 13508 Event ID for FRS up vote 4 down vote favorite This question is related to a previous one I asked regarding backing up Domain Controllers and RODC's. Basically I am making some changes in regards to the DC's in my network. I am looking to add a writable 2008R2 DC as well as a 2008R2 RODC to my domain. I have created a writable 2008R2 DC called "DC-04", it is set up event id 13508 and appears to be working fine with one exception. When I run dcdiag /v on this new domain controller, I get an error during the FRS event test. This error corresponds to Event 13508 that I am getting and it states: "The File Replication Service is having trouble enabling Replication from DC-02 to DC-04 for c:\windows\sysvol\domain using the DNS name dc-02.domain.com. FRS will keep retrying." Some information that may be helpful: DC-02 is running 2003R2 x86, it also holds all 5 FSMO roles There is another DC called DC-03 also running 2003R2 x86, no errors come up on DC-04 regarding replication from this DC All DC's are Global Catalogs and have DNS I can ping dc-02.domain.com from dc-04, so DNS seems ok FRS service is running on DC-02 Any ideas or things to check would be greatly appreciated. Thanks! active-directory replication domain-controller file-replication-services share|improve this question edited Aug 13 '12 at 21:45 asked Aug 13 '12 at 20:50 Mike 501315 Ugh, FRS sucks. I mean, really sucks. Is it possible to upgrade to DFS or DFS-R? (2k8 FL required, IIRC.) That's the first thing I'd try, because FRS just doesn't work and is such a massive pain to fix that it's best to not use it if at all possible. –HopelessN00b Aug 15 '12 at 2:26 add a comment| 3 Answ
that uses a VPN to connect back to the head office. Got some tips from Expert Exchange, but to summarise the various steps you should check are simple but effective (and as usual mostly DNS related): Check there are no external DNS servers listed Checked the localhost DNS server is not listed Check that NETBIOS is only enabled over the internal NIC Check that the other domain controllers FQDN's are pingable Check that the SRV records under the domain and _msdcs forward lookup zones include all your domain controllers (and only their internal IP addresses) Manually trigger the domain controller replication connections through "Active Directory Sites and Services", expand the server, right click "NTDS Settings" and do "All Tasks" and then "Check Replication Topology". Make sure you click the Refresh button to see if all the replication links are listed. Use netdiag -v and dcdiag -v to isolate any other problems Keep restarting the Netlogon service 🙂 I really wish the DNS lookup that Active Directory did was a little more resilient (i.e. if the first DNS server lookup fails then use the secondary). Tags: active directory, DNS, errors, file replication service, Microsoft Leave a comment | Trackback 2 Responses to "FRS Error 13508 without 13509" http://yahoo.com February 10th, 2013 at 21:45 1 I really blog likewise and I am crafting a little something related to this blog post, “FRS Error 13508 without 13509 | Scott Savage's Blog”. Do you really mind if I reallyapply a lot of of your personal suggestions? Regards -Anderson Reply Scott Savage March 6th, 2013 at 22:21 2 Please go ahead! Post the link back here if you can so we can tie the related content together. Reply Leave a Comment Click here to cancel reply. Name (required) E-Mail (will not be published) (required) Website « Thriving in a Crisis Can Spam Improve SEO? » RSS Twitter Recent Posts AsianGut Launched! Remove Adware infected YouTube App Graduating from my INSEAD EMBA Flickrtoplus.com now supports Google Photos NBN Fibre vs MTM comparison Starting an INSEAD MBA Upgrade DIR-615 wireless router to a DD-WRT Access Point How to Win Friends and Influence People : Book Review FlickrToPlus.com - Flickr to Goo