Re: Win2000-Server tries to connect various machines on port 53

From: Ken Schaefer (kenREMOVE_at_THISadOpenStatic.com)
Date: 08/22/03 

Date: Fri, 22 Aug 2003 19:05:21 +1000

Are you running a DNS server on this machine (I assume you are, since you
say it is a Domain Controller, and Windows 2000 domains require Active
Directory)?

Port 53 (UDP) is for DNS. If you are running a DNS server on this machine,
it may be connecting out to do a DNS lookup.

Cheers
Ken 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Kay Lehmann" <kay_lehmann@web.de> wrote in message
news:3f45d632$0$2342$9b4e6d93@newsread2.arcor-online.net...
: Hello everybody,
:
: I have following porblem with a win2000 server:
:
: It tries to connect varous machines on port 53. Some of the adresses are:
:
: 158.38.0.181
: 193.0.0.193
: 194.176.32.129
: 192.36.125.2
: 137.39.1.3
: 128.214.4.29
: ...
:
: So as I am not administrator of this machine and I am not that familiar
with
: windows, but has to configure the firewall, I wanted to know if somebody
: can tell me how to find the program, which tries to connect to the
outside.
: Maybe a trojan, worm or something else? I tried to find something about a
: this in the internet but I do not know where to find a searching machine
: where I can insert some symptoms of the behavior of my machine which gives
: a list of worms or viruses which could be the reason, is there any? The
: other question is:
:
: Which ports should be normally opened on the win2000 server (It works as
: domain controller). nmap gives me:

Relevant Pages

  • Replication Problem
    ... In our company we have a Windows 2000 AD with 2 DCs each in a different site. ... The DNS server was unable to open the Active Directory. ... Could not bind to a Domain Controller. ... infer a route by which this Partition can reach this site. ...
    (microsoft.public.win2000.active_directory)
  • Re: Epmap Connectionn Problem
    ... The problem is still here after I change the machine's DNS server; ... The machine is with SP2 and fire wall is on; ... The port number connect to server's epmap port is protean. ... > windows firewall to log successful connections and dropped packets. ...
    (microsoft.public.windowsxp.general)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... that can replicate the directory partition over this ... either fixup the alpha site dns or point it to use the SBS dns server and allow replication to complete before pointing it back to using itself for DNS. ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Demoting a DC in W2003
    ... >> roles) and DC3 is a plain DC. ... >> was configured to use itself as it's primary DNS server, ... >> object from the following source domain controller. ... > DC3 due to replication problems that have been happening longer than 60 ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication issues
    ... "If this is a Windows 2000 AD domain controller, ... you will want to ensure that the first DNS server in the ... What if it is Windows Server 2003, ... >> The File Replication Service is in an error state. ...
    (microsoft.public.windows.server.active_directory)
Quantcast