[cbakey]

Dose anyone know of a command in CMD in win2k that allows you to see what ports are open on you computer?, I looked in help and its not in there....
Thanks

[rUfUnKy]

open command promt and then type "netstat" (without the quotes) I believe this is what you want. This will show you what ports are being used now. Otherwise you could just run a port scan on your ip and get a list of open ports.

[nemisys]

"netstat -a" shows a little more info (TCP and UDP ports).

[Gordon Airport]

I like TCPView from sysinternals.com. It's basically a real-time netstat.
Pick up some of their other stuff while you're there, very handy.

[SinsFeelNatural]

Originally posted by nemisys
"netstat -a" shows a little more info (TCP and UDP ports).

does *.* denote an open port?

[EmTSea19]

In Netstat, what does "foreign address" mean?

[Ravsitar]

dslreports.com has the port scanner tool. there's also this port scanner www.BlueBitter.de it works too.

[josi]

Run netstat -an and look for TCP entries with state "LISTENING" and UDP entries with foreign address "*.*".

[Gordon Airport]

Hmm, what are we suposed to do with the *.* UDP ports? The services that own them are svchost.exe or System so I've always figured they were...uh, important system stuff. Looks like NETBIOS and time service.

[Chris]

Netstat just shows what ports are being used, it doesnt show easily all ports that are open. The best thing to do is runa port scan on your self, or just check your firewall and see what you have open.

[josi]

Sorry, Chris, but what netstat shows is depending from the command line parameters, and with parameter "-a" it shows also all open ports.

[pik4chu]

I will dd that if you have teh ability to stealth open ports and such, they WILL show up in netstat, bu5 a port scan and such will show as no open ports, even if there are. best way is to use netstat -an. if you happen to have kazaa or other P@P filesharing running you will see a lot of wierd ports and addresses, so dont freak out too much

kinda like this

PHP Code:

.......
TCP    192.168.1.33:1032      192.168.1.34:139       ESTABLISHED
TCP    192.168.1.33:1174      213.112.10.147:411     ESTABLISHED
TCP    192.168.1.33:1176      68.113.58.59:1214      ESTABLISHED
TCP    192.168.1.33:1188      24.25.188.106:30446    ESTABLISHED
TCP    192.168.1.33:1211      217.164.83.16:1411     ESTABLISHED
TCP    192.168.1.33:1381      217.215.14.131:418     ESTABLISHED
TCP    192.168.1.33:1552      24.94.250.20:1412      ESTABLISHED
TCP    192.168.1.33:1648      213.199.92.93:1933     ESTABLISHED
TCP    192.168.1.33:1848      24.166.163.245:3798    ESTABLISHED
TCP    192.168.1.33:1853      213.64.197.83:1813     ESTABLISHED
TCP    192.168.1.33:1940      142.165.29.16:411      ESTABLISHED
....... 


[Chris]

Originally posted by josi
Sorry, Chris, but what netstat shows is depending from the command line parameters, and with parameter "-a" it shows also all open ports.

I thought that was just open ports that are in use though? and not all open ports full stop. I dont mind being corrected if im wrong.

[pik4chu]

Originally posted by Chris


I thought that was just open ports that are in use though? and not all open ports full stop. I dont mind being corrected if im wrong.

if the State TCP is "LISTENING" then its open but not in use. or for UDP the forieng address is *.* then its open but not in use. all the other States means its in use one way or another. (like, Established, Time_wait, Closing, Close_wait, Fin_wait_XX and so on)

[Chris]

Originally posted by pik4chu


if the State TCP is "LISTENING" then its open but not in use. or for UDP the forieng address is *.* then its open but not in use. all the other States means its in use one way or another. (like, Established, Time_wait, Closing, Close_wait, Fin_wait_XX and so on)

ah ok thanks