tcp 135 connnect local to local

[Guest]

Hi! I got some question about what happens just after my computer(windows 2000 server) boots
I found the result of 'netstat -an' just after my computer boot

Proto Local Address Foreign Address Stat
TCP 192.X.X.X:random port 192.X.X.X:135 time-wai

**192.X.X.X : my computer ip addres

and a few minutes later it is gone and find this ( below

Proto Local Address Foreign Address Stat
TCP 0.0.0.0:135 0.0.0.0:0 LISTENIN

why local system connects itself to tcp 135 port just after booting? It looks general things but I would like to know why it happen exactly. I looked all around by google searching but couldn't find out

 

[David H. Lipman]

Please go to McAfee (http://www.mcafee.com/myapps/mfs/default.asp) and/or Trend
(http://housecall.antivirus.com ) and perform an online scan of your platform then report
back your results.

Dave



| Hi! I got some question about what happens just after my computer(windows 2000 server)
boots.
| I found the result of 'netstat -an' just after my computer boots
|
| Proto Local Address Foreign Address State
| TCP 192.X.X.X:random port 192.X.X.X:135 time-wait
|
| **192.X.X.X : my computer ip address
|
| and a few minutes later it is gone and find this ( below )
|
| Proto Local Address Foreign Address State
| TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
|
| why local system connects itself to tcp 135 port just after booting? It looks general
things but I would like to know why it happen exactly. I looked all around by google
searching but couldn't find out.
|
|
|
|
|
|
|

 

[Guest]

I don't think my computer is infected by some worms that attack MS RPC vulnerability
and the result is OK! I suppose that it's nomal thing