netstat in Windows showing multiple established TCP connections... 1

[Jimtron26]

Hi all,

I was wondering if anyone can help... When I run the netstat -a command on one of our servers it is showing multiple TCP ESTABLISHED connections to the loopback address 127.0.0.1 on differant ports. Sample output below..

TCP 127.0.0.1:1080 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1091 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1092 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1098 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1104 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1105 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1106 127.0.0.1:9092 ESTABLISHED
TCP 127.0.0.1:1109 127.0.0.1:1110 ESTABLISHED
TCP 127.0.0.1:1110 127.0.0.1:1109 ESTABLISHED

When ran on a client PC I can see the loopback address under UDP but no established TCP connections. Our server is currently having a problem whereby its memory is being used up rapidly and it keeps crashing. I am anxious to eliminate this as being the cause of the problem. The server is running Windows 2000 Pro.

Thank you in advance

Jim CCNA

 

[Serbtastic]

Download TCPView from Sysinternals.com to see what process is establishing the connections.

Windows XP has this functionality built in (using the netstat -o command) but Windows 2000 does not.

 

[cyberspace]

worth pointing out that it's netstat -b in Windows XP to see the process eg msnmsgr.exe

using the -o operator just shows the process ID, eg '247' which isn't too helpful

'When all else fails.......read the manual'