Networking Forums

Networking Forums > Computer Networking > Windows Networking > question about port 389 in windows 2000 server

Reply
Thread Tools Display Modes

question about port 389 in windows 2000 server

 
 
yatlam
Guest
Posts: n/a

 
      08-10-2004, 05:07 PM
Hi all, I found that there is an unknown problem in the port 389 of my
windows 2000 server and it is really disturbing.
I have checked the TCP Connections on my server, there are over a hundred of
established connections on the port 389 with the other local ports. For
example, my server's local IP is 10.8.0.191, the connections are as below:
10.8.0.191 389 -> 10.8.0.191 10000 ESTABLISHED
10.8.0.191 389 -> 10.8.0.191 10201 ESTABLISHED
10.8.0.191 389 -> 10.8.0.191 10332 ESTABLISHED
10.8.0.191 389 -> 10.8.0.191 10403 ESTABLISHED
10.8.0.191 389 -> 10.8.0.191 10522 ESTABLISHED
10.8.0.191 389 -> 10.8.0.191 10615 ESTABLISHED
..
..
..
..
..
10.8.0.191 389 -> 10.8.0.191 11315 TIME_WAIT
..
..

It seems that it is caused by some virus, but I have tried a full scan on my
server and checked all process on run. No virus has been discovered. Some of
my local network applications, such as files accessing and active directory
accessing, have been slow down and even unaccessable. I have no idea on
that. Could any one help me to figure out the problems and give me some
suggestion to tackle this? Thank you very much.

Lam


 
Reply With Quote
 
 
 
 
Miha Pihler
Guest
Posts: n/a

 
      08-10-2004, 05:27 PM
Hi,

389 is TCP port used by LDAP (Lightweight Directory Access Protocol). LDAP
is a base for Active Directory -- all the queries in Active Directory are
done through LDAP (e.g. looking for user information etc...).

Mike

"yatlam" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi all, I found that there is an unknown problem in the port 389 of my
> windows 2000 server and it is really disturbing.
> I have checked the TCP Connections on my server, there are over a hundred

of
> established connections on the port 389 with the other local ports. For
> example, my server's local IP is 10.8.0.191, the connections are as below:
> 10.8.0.191 389 -> 10.8.0.191 10000 ESTABLISHED
> 10.8.0.191 389 -> 10.8.0.191 10201 ESTABLISHED
> 10.8.0.191 389 -> 10.8.0.191 10332 ESTABLISHED
> 10.8.0.191 389 -> 10.8.0.191 10403 ESTABLISHED
> 10.8.0.191 389 -> 10.8.0.191 10522 ESTABLISHED
> 10.8.0.191 389 -> 10.8.0.191 10615 ESTABLISHED
> .
> .
> .
> .
> .
> 10.8.0.191 389 -> 10.8.0.191 11315 TIME_WAIT
> .
> .
>
> It seems that it is caused by some virus, but I have tried a full scan on

my
> server and checked all process on run. No virus has been discovered. Some

of
> my local network applications, such as files accessing and active

directory
> accessing, have been slow down and even unaccessable. I have no idea on
> that. Could any one help me to figure out the problems and give me some
> suggestion to tackle this? Thank you very much.
>
> Lam
>
>



 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Question on Trusts with Windows 2003 and Windows 2000 Corey Arndt Windows Networking 0 06-15-2007 02:45 PM
DHCP Migration from windows server 2000 to windows server 2003 Amr Salah Windows Networking 3 02-04-2007 12:01 PM
Migrating to Windows Server 2003 from Windows Server 2000 and using Remote Desktop Client Navodit Windows Networking 1 09-13-2006 07:38 PM
Windows 2000 server problem on a Windows 2003 server domain =?Utf-8?B?U2Fsb25nZQ==?= Windows Networking 1 02-09-2005 03:16 PM
Windows 2000 question spanner@quik.com Wireless Internet 2 05-05-2004 10:37 PM



1 2 3 4 5 6 7 8 9 10 11