![]() |
#1
|
|||
|
|||
![]()
Is there any way I can find out which ports an application is using or has used? Or rather, is there any way that I as a computer layman can find that out?
|
#2
|
|||
|
|||
![]()
Open a cmd box (start menu / run) and type in
cmd when the cmd box opens type netstat -ao This will give you the port type, local port, foreign IP address, the stats its in + a PID Number. Hit CTRL + ALT + DEL to bring up the task manager, you should see a list of all the processes running on your computer.. click on the view menu and select colums click the box for PID and click ok. Now you can match up the PID's to see what is connecting to what [img]/images/graemlins/laugh.gif[/img] |
#3
|
|||
|
|||
![]()
Checkout www.sysinternals.com. There is a whole host of useful utilities here. They where so good and the author of the site know more about the inner workings of window that Microsoft made him an offer he could not refuse.
|
#4
|
|||
|
|||
![]()
sonneti:
I tried the netstat/task manager thing just for the hell of it but it doesn't seem to work. I mean, some of the PID's match up but some aren't even listed in netstat. For example, according to TM "explorer.exe" has a PID of 3956, however that PID # isn't even listed in the netstat output. There are also a few others like that. Whats up? -DG |
#5
|
|||
|
|||
![]()
Because explorer doesn't listen to TCP/IP traffic and if it did I'd freak out.
Download TCPView from Microsoft Sysinternals as the other poster mentioned. http://www.microsoft.com/technet/sys...g/TcpView.mspx |
#6
|
|||
|
|||
![]()
It was inevitable it would happen - a crapload of MS KB articles specifically mentioned using sysinternals tools to diagnose problems.
The marriage was bound to happen - plus the sysinternals tools should only become better simply because he now has official access to kernel API's. |
![]() |
|
|