Annoyances.org
Home » Windows Server 2003 Discussion Forum » Message 1230073726 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: stop tcp msg to old server - to port 139
Tuesday, December 23, 2008 at 3:08 pm
Windows Server 2003 Annoyances Discussion Forum
Posted by appleoddity (2343 messages posted)


Well, as you've discovered you can't just unplug a domain controller. It has to be demoted. I just dealt with this the other day. There are two specific articles I came across that had all the information I needed to remove the dead domain controller from the working domain controller and active directory. Unfortunately, I don't remember the process and I don't remember the articles. However, I can say that I found all the information by looking in the event viewer and googling the errors, then reading the documentation you will find about improperly removed domain controllers. Your event logs will be full of errors.




Written in response to:
re: stop tcp msg to old server - to port 139 (bgd: Tuesday, December 23, 2008 at 12:20 pm)

There are presently no replies to this message.

All messages in this thread [show all]
-stop tcp msg to old server - to port 139 (bgd: Thu, Dec 18, 2008, 2:43 pm)
-re: stop tcp msg to old server - to port 139 (appleoddity: Mon, Dec 22, 2008, 3:40 pm)
-re: stop tcp msg to old server - to port 139 (bgd: Tue, Dec 23, 2008, 6:12 am)
-re: stop tcp msg to old server - to port 139 (appleoddity: Tue, Dec 23, 2008, 8:51 am)
-re: stop tcp msg to old server - to port 139 (bgd: Tue, Dec 23, 2008, 12:20 pm)
*re: stop tcp msg to old server - to port 139 (appleoddity: Tue, Dec 23, 2008, 3:08 pm)
Return to the Windows Server 2003 Discussion Forum


All content at Annoyances.org is Copyright © 1995-2009 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.