CurrPorts

Paul · 22-01-2006, 22:30

Dunno if anyone has posted this but a useful tool to check on what ports are active on your PC at any one time
CurrPorts
CurrPorts Download

Quote:

CurrPorts displays the list of all currently opened TCP/IP and UDP ports on your local computer. For each port in the list, information about the process that opened the port is also displayed, including the process name, full path of the process, version information of the process (product name, file description, and so on), the time that the process was created, and the user that created it.
In addition, CurrPorts allows you to close unwanted TCP connections, kill the process that opened the ports, and save the TCP/UDP ports information to HTML file , XML file, or to tab-delimited text file.
CurrPorts also automatically mark with pink color suspicious TCP/UDP ports owned by unidentified applications.
System Requirements
This utility works perfectly under Windows NT, Windows 2000, and Windows XP. If you want to use this utility on Windows NT, you should install psapi.dll in your system32 directory.
You can also use this utility on previous versions of Windows (Windows 98/ME), but in these versions of Windows, the process information for each port won't be displayed.

Down the Pub · 22-01-2006, 22:56

on the subject of ports, and to thother side of the thread

did a firewall test the other day to test comodo, one with shields-up and the other was grc i think, shield-up came back all hidden and the other said that port 80 was open, isn't 80 the port for http and needed? both basically say that 80 should be closed?

conflicting and confusing info? whats the train of general thought? as i don't know which one is more accurate than the other.

Paul · 22-01-2006, 22:57

Port 80 should be open when needed but shouldn't be seen to be open (stealthed) or it can be abused.

Down the Pub · 22-01-2006, 23:02

thought so, just when one says you are stealthed and you think you're ok and another kicks u in the knackers and says no you're not......................you get the idea?

Hom3r · 22-01-2006, 23:03

How do you close / stealth port 80?

Paul · 22-01-2006, 23:06

Always a strange one that but some firewalls can cause the port to be mis-represented when tested. I used to worry about my ports till I got a router lol

Anyway.... back on topic

---------- Post added at 23:06 ---------- Previous post was at 23:03 ----------

Quote:

Originally Posted by david.ewles

How do you close / stealth port 80?

A decent firewall or router will make sure that all ports are properly protected and/ or stealthed so that they are not seen by anyone looking for ports to attack.

Down the Pub · 22-01-2006, 23:12

so what would u recommend as a good port tester?

bopdude · 23-01-2006, 00:15

Quote:

Originally Posted by Down the Pub

so what would u recommend as a good port tester?

... the clue might be in the title

thats as much as I know, I'll get me coat.

Thanks for another heads up Paul.

Gareth · 23-01-2006, 12:28

Ahh, looks a lot like Fport from Foundstone... although it seems to automate some of the things you'd have to do manually after examining Fport's output. Nice one

---------- Post added at 12:28 ---------- Previous post was at 12:21 ----------

Quote:

Originally Posted by Down the Pub

so what would u recommend as a good port tester?

For Windows users, try here whereas Linux users can also do this by running netstat -pan --inet