Event ID 13508 in microsoft windwos 2000 server

pts.
Tags:
Availability
Bandwidth
Benchmarking
Budgeting
Business/IT alignment
Career Development
Compliance
DataCenter
Fault isolation
Firewalls
Forensics
Incident response
Intrusion management
Laws
Management
Microsoft Windows
Network applications management
Network management software
Network monitoring
Network security
Network testing
Networking
OS
Outsourcing
Patch management
Performance management
Ping
Project management
Protocol analysis
Regulations
Remote management
ROI
Security
Servers
SQL Server
standards
Storage
Vendors
VPN
Wireless
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

Answer Wiki

Thanks. We'll let you know when a new response is added.

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

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Jcan123
    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 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following