Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Event ID 13508 on DC
I am not that good with AD and dont want to mess anything and hope can get some resolution today as tomorrow users will be back and dont want any issues than
Asked:
Who is Participating?
Procedures for Troubleshooting FRS Event 13508
http://technet.microsoft.com/en-us/library/bb727056.aspx#EMAA
Run the below commands and check for any errors
Dcdiag /q, Netdiag /q
Check if the Time sync is in place
Firstly check if below Registry is in place on the server that shows errors
net time \\ComputerName_Of_Authorit
net stop ntfrs
net start ntfrs
- Rancy
"Merry Christmas and Happy New Year"
http://technet.microsoft.com/en-us/library/bb727056.aspx#EMAA
Run the below commands and check for any errors
Dcdiag /q, Netdiag /q
Check if the Time sync is in place
Firstly check if below Registry is in place on the server that shows errors
In my case these changes didn't resolve the problem:
1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon trolSet\Se rvices\NtF rs\Paramet ers
4. On the Edit menu, click Add Value, and then add the following registry value:
Value name: Enable Journal Wrap Automatic Restore
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 1 (Default 0)
5. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon trolSet\Se rvices\NtF rs\Paramet ers\Backup /Restore/P rocess at Startup
6. On the Edit menu, click Add Value, and then add the following registry value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2
7. Quit Registry Editor.
8. Start FRS service
net time \\ComputerName_Of_Authorit
net stop ntfrs
net start ntfrs
- Rancy
"Merry Christmas and Happy New Year"
This link should help
http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=ntfrs&phase=1
http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=ntfrs&phase=1
TG-TIS can you tell me what specific steps your refering to as few are listed in the post from Rancy and not sure if there you are wanting to check something rather than working on entire post
Regards
Regards
The steps I'm referring too appear to be idetical to the steps Rancy quoted. It appears someone copied them to the Microsoft sire (or vise versa) a while back.
No worries is there something you can suggest that i can check ? Would like to take all options and work on them in one time
Regards
Regards
There are multiple reasons for event id 13508 to occur it could be due network latency issue.Ad sites and services are not set corectly,replication issue,dns misconfig,required port not open for AD replication,secure channel broken,etc.
I would recommend to first check the health of dc by running dcdiag /q and repadmin /replsum and post the log if error is reported along with ipconfig /all details of DC's.
I would suggest contact network/security team to verify whether all the related AD ports being configured and allowed on the firewall for communication. Portquery is free tool from the MS which can be downloaded and installed to verify the necessary ports are opened or not.
Also, disable local windows firewall service, by default it is enabled in vista/windows 2008 and above. Check the network connectivity and latency.
Disable Windows Firewall:http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx
Active Directory and Active Directory Domain Services Port Requirements
http://technet.microsoft.com/en-us/library/dd772723%28WS.10%29.aspx
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
If manual connection are created in AD sites and service then remove the same and run repadmin /kcc to regerate the topology:
http://blogs.technet.com/b/markmoro/archive/2011/08/05/you-are-not-smarter-than-the-kcc.aspx
See this similar thread too:
http://qa.social.technet.microsoft.com/Forums/en-US/winserverDS/thread/7652f4ac-6974-4bdc-9b31-7632c85b0811
Hope this helps
I would recommend to first check the health of dc by running dcdiag /q and repadmin /replsum and post the log if error is reported along with ipconfig /all details of DC's.
I would suggest contact network/security team to verify whether all the related AD ports being configured and allowed on the firewall for communication. Portquery is free tool from the MS which can be downloaded and installed to verify the necessary ports are opened or not.
Also, disable local windows firewall service, by default it is enabled in vista/windows 2008 and above. Check the network connectivity and latency.
Disable Windows Firewall:http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx
Active Directory and Active Directory Domain Services Port Requirements
http://technet.microsoft.com/en-us/library/dd772723%28WS.10%29.aspx
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
If manual connection are created in AD sites and service then remove the same and run repadmin /kcc to regerate the topology:
http://blogs.technet.com/b/markmoro/archive/2011/08/05/you-are-not-smarter-than-the-kcc.aspx
See this similar thread too:
http://qa.social.technet.microsoft.com/Forums/en-US/winserverDS/thread/7652f4ac-6974-4bdc-9b31-7632c85b0811
Hope this helps
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Browse \\WorkingDC.domain.local copy sysvol & netlogon and keep backup on ProblemDC & WorkingDC (If can not browse check network connectivity/Port and don't proceed further)
Go to WorkingDC stop NTFRS service open regedit and go to "HKEY_LOCAL_MACHINE\System
Check Now your sysvol and netlogon shares are available
Above is called Authoritive(D4) and non-Authoritive Restore (D2)
Refer http://support.microsoft.com/kb/257338 for more info