Event ID 13508 in microsoft windwos 2000 server
Home > IT Answers > Networking > Event ID 13508 in microsoft windwos 2000 serv...
management
0 pts.
0
Q:
Event ID 13508 in microsoft windwos 2000 server
Networking, Network management software, Network security, Firewalls, Intrusion management, Incident response, Forensics, Wireless, Storage, Security, Network monitoring, Network testing, Performance management, Remote management, Servers, Microsoft Windows, Protocol analysis, Career development, Network applications management, Management, Compliance, Project management, Laws, Regulations, standards, Bandwidth, Business/IT alignment, Vendors, ROI & cost justification, VPN, Budgeting, Outsourcing, OS, Desktops, SQL Server, Availability, Ping, Benchmarking, Fault isolation, DataCenter, Patch management
Hi all

I have a three servers with windows 2000 (service pack4 ) and its running active directory and DNS also. My global catalog server (PDC) am calling as server ?A? , others are server ?B? and server ?C?. These are two servers are acting as BDCs. One of the BDC?s Hard disk was crashed last week and I removed this computer from my network physically also. I have no problems in my network its working fine. Nowadays am getting an error message in event viewer ID#13508 (source is NTFRS). Now I want to tell u that I want to remove my server name which is crashed server ?C? from the Active directory sites and services menu ? sites? servers.
Following are the event desctiption which I got in the event viewer

The file replication service having trouble enabling replocation from server C to server A fro c:winntsysvol domain using the DNS name C.<domain name>.local FRS will keep retrying. Following are some reasons you would see this warring.

Now please help how remove this crashed server entries from my Acitve directory and DNS database.

Highly appreciate your kind help on this regards,
Thanking you in advance.
Bye from Niyas.
Niyas@gsh-sa.com
ASKED: Apr 3 2006  9:44 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
ehcraig
0 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
Hello Niyas,

This error in your event log is coming from the FSMO server (server A) trying to replicate to DNS on server B, then B trying to replicate to DNS on server C.

Go into the dns mgr snap-in for the other two machines and remove the server C (crashed server) from the 'allow replication to' list. Also, you may have server B forwarding to server c, remove that reference also.

This will stop that particular error, but does not remove it from your AD. There, you will have to remove it in your 'User & computer' mgr. snap-in

Evans Craig
Skillstorm IT
Last Answered: Apr 3 2006  7:01 PM GMT by ehcraig   0 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

jcan123   0 pts.  |   Apr 4 2006  8:13AM GMT

Actually there is a KB article describing how to remove an orphaned or crashed DC from AD. This is neccessary to follow as there are lots of references in AD to this DC, so just deleting it does help. There are 2 ways to do this - follow the article or demote DC properly.

 
0