|
|
|
stop tcp msg to old server - to port 139
Showing all messages in thread #1229640199
Windows Server 2003 Annoyances Discussion Forum
The following are all of the messages in this thread (6 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
|
stop tcp msg to old server - to port 139
Thursday, December 18, 2008 at 2:43 pm
Posted by bgd
(3 messages posted)
I have removed a server from our system, and tried to remove all links to it, but
my firewall shows continuing traffic to this address from another server. I am getting
messages from my server with varying port numbers (port number increments by about
20 to 30) to old server port 139. I know this 139 port is old NetBios related...
Have checked WINS configuration, DHCP, DNS, but cannot find where this reference
is coming from. Using Netstat it says PID 4 {system} is doing this...
both Servers are Windows 2003 - messages come about every 3 minutes - - any ideas
on how to clean this up and stop it??
[Reply or follow-up to this message]
| |
re: stop tcp msg to old server - to port 139
Monday, December 22, 2008 at 3:40 pm
Posted by appleoddity
(2369 messages posted)
Was the server you removed a domain controller?
[Reply or follow-up to this message]
|
re: stop tcp msg to old server - to port 139
Tuesday, December 23, 2008 at 6:12 am
Posted by bgd
(3 messages posted)
yes, it was a domain controller - it co-existed in new domain for a while, and functions
were migrated over to new server
[Reply or follow-up to this message]
|
re: stop tcp msg to old server - to port 139
Tuesday, December 23, 2008 at 8:51 am
Posted by appleoddity
(2369 messages posted)
Was the domain controller demoted properly?
[Reply or follow-up to this message]
|
re: stop tcp msg to old server - to port 139
Tuesday, December 23, 2008 at 12:20 pm
Posted by bgd
(3 messages posted)
no, it was not demoted - - that would have probably been a good thing to do
- but no (and it is not available to 'demote' now)
so is there any method to determine which services are trying to do this, and fix
them??
[Reply or follow-up to this message]
|
re: stop tcp msg to old server - to port 139
Tuesday, December 23, 2008 at 3:08 pm
Posted by appleoddity
(2369 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.
[Reply or follow-up to this message]
| |
| |
Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
| |
Return to the Windows Server 2003 Discussion Forum
|
|
|
|
