• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 417
  • Last Modified:

problem with retired DC

At client`s site we have problem with a retired DC running NT4. Apparently there is a ghost on the network!!! When we shut down this host, the network is slightly slowing down. There is no DNS or DC relation with this host anymore, no share, no listening services.   We even used a sniffer and no trafic has been catched destinated to the host during 60min.

If you ever got similar issue, as network administrator, when removing old server please let me know what was the cause?  Will higher points to its mak if good answer is received
0
Danny_Larouche
Asked:
Danny_Larouche
1 Solution
 
JMMICommented:
Have you checked WINS?  Is this retired host listed as a WINS server for other hosts, or is it in the WINS database marked as workgorup or domain server?
0
 
Naser GabajCommented:
Greetings Danny_Larouche,

>> When we shut down this host, the network is slightly slowing down
Start with checking the event viewer of that host if there is anything suspicious, and let me know.

Good Luck!

Naser
0
 
mikefalconeCommented:
Sound to me like the existing DCs think the DC still exists.

you can remove it using NTDSUTIL

Do a search on google for NTDSUTIL metadata cleanup and you will find step by step instructions
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
Naser GabajCommented:
Hi Danny_Larouche,

It's long time since you asked the Q. Are you still working on this? Was the information provided helpful? Do you need more information?

If any of the above answers gave you the solution, please accept his/her answer with the appropriate grade you see.

Please let us know, we appreciate your reply.

Naser
0
 
Danny_LaroucheAuthor Commented:
Yes i work on it, the DC was effectively listed as DC then we tried to remove it from the list using srvmgr script. Curiously, the DC still there!! For any new attempt to remove it i got a message "DC is already removed... and will disapear from the list in 15min..."

I will see tomorow if it affect the network or not and will try to block trafic destinated to this host
0
 
mikefalconeCommented:
Do what I said. That is what microsoft built in to fix the problem you are having. Here is a link to Microsoft's step by step instructions.



http://technet2.microsoft.com/WindowsServer/en/Library/012793ee-5e8c-4a5c-9f66-4a486a7114fd1033.mspx?mfr=true
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now