DFS/FRS error with removing an old server

[FatBoy]

Hi People,

 

I have a issue with the File Replication Service part of my event viewer in that I keep getting the same 2 errors everyday. I know why they are happening but not how to get rid of the error

 

The problem is we used to run DFS across from Server A to Server B, Server B is now dead and replaced by Server C (Server A and C both work nicely together). Now everyday I get the below error:

 

Event Type: Warning

Event Source: NtFrs

Event Category: None

Event ID: 13508

Date: 22/10/2008

Time: 00:11:15

User: N/A

Computer: Server A

Description:

The File Replication Service is having trouble enabling replication from Server B to Server A for e:\users\homdirs using the DNS name Server B.domain.CSCo.Org.UK. FRS will keep retrying.

Following are some of the reasons you would see this warning.

 

[1] FRS can not correctly resolve the DNS name Server B.ashford.CSCo.Org.UK from this computer.

[2] FRS is not running on Server B.ashford.CSCo.Org.UK.

[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

 

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

 

Now Server B isn't with us any more BUT its account is still on the domain!!! Shall I just delete the computer account and that should do it or check in certain area's first before I delete it?

 

I have looked in DFS and AD Sites and Services and can find no mention of any servers setup to Replicate with it, I just didn't want to delete the computer account and then find out I have made it worst for myself

 

All servers are W2003 Std SP2

[User3204]

There's a setting in AD that lists all the DFS stuff.

 

It's not in the usual AD controls (DSA.msc etc), you have to go into the ADSIEDIT.msc - which is a separate download from Micro-Soft.

 

Just be careful what you delete from there, as it could cause serious problems, and I don't just mean slight problems that occur from deleting stuff from the registry.

[FatBoy]

thanks for that 3204 the simple solution worked in the end, deleting the old computer account from the domain has stopped the errors thankfully