Fport.exe & TCPvcon.exe help

[hjbyram]

I downloaded Fport.exe & also TCPView.exe/TCPVcon.exe.

However, the only one I can get to work is TCPView, which gave me a nice report. I am trying to identify some ports showing up in my firewall log, & thought these tools would help.

I apparently have to do something I am not doing - I thought I could just execute the .exe software from the downloaded, unzipped folder? I see something flash by, but it's gone & I don't get a report.

Any help in how to execute these would be appreciated - new user to all of this & also not very experienced obviously.

THANKS

[Bubba]

In regards to fport....there are a number of ways to accomplish this but I'll list my preferred method.

1) Copy fport.exe to your System32 folder

2) Create a batch file with the below contents and name it whatever you wish(launch.bat for example)....and place that file in a folder of your choice.

fport > fport.txt
notepad.exe fport.txt 3) You can either go to where launch.bat is located and select it or place a short-cut on your desktop to that file.

When you execute the above batch file it should open fport in a cmd box with notepad overlayed and the fport info.

Bubba

[Tommy]

I think 'netstat -an' in the cmd box does the same , or am i wrong?

[Bubba]

-{ Quote: "I think 'netstat -an' in the cmd box does the same , or am i wrong?" }-netstat will give port\protocol.

fport will give port\protocol\pid\process

[Tommy]

There is a other nice freeware utility for that purpose out there called CurrPorts.
http://www.nirsoft.net/utils/cports.html
-{ 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 (Applications without version information and icons)" }-
There are by the way alot of nice Freeware tools available on this page.

[hjbyram]

Thank you, Bubba, I got the fport to work following your instructions - at last I know what some of these ports are being used for.

And thank you, Tommy - I copied down & used the CurrPorts also. VERY interesting & should help resolve some things.

Thanks everyone - this is exactly what I have been looking for, though I may be back asking additional questions on some of these items.

THANKS!