I've seen this on both Windows XP Pro SP3 and Windows 7 Pro SP1 (32-bit).

This applies to Portmon v3.03.

When you double click on portmon.exe icon from within a Windows Explorer window (windows key + e) the connect timing seems to be sensitive to other windows open on the system.

The workaround is to ***close ALL windows and applications***, open a command prompt (i.e. Start->Run...->cmd->OK) and launch portmon.exe from the command line.

----

In addition, you can run into a pitfall if you try to run from a zip file. For this case on Windows XP, you should unzip the file into a directory, right mouse click on the unzipped portmon.exe file and in the Properties Dialog->General tab click on the Security "Unblock" button.

Also, if permissions/security settings come into play, you can right mouse click on the portmon.exe file and choose the "Run As..." menu item, and make sure that the "Protect my computer and data from unauthorized program activity" check box is unchecked or run as an Administrator.

Again, once you have encountered the "Not Connected" state for the application as indicated in the window title bar, any subsequent attempts to launch from a window, will still lead to the "Not Connected" state where the Capture->Capture Events and Capture->Ports menu items are disabled and greyed out.

A fix that worked for me on Windows 7 Pro and 8.1 is to:1) start portmon client - enter portmon /c in a command prompt or make a shortcut with the parameter /c after the path. Will show Portmon Remote Client window - "waiting for connection"2) on the same PC start portmon (with no parameters)3) type ctrl-R to show dialog box to enter a remote computer name or IP address - enter "localhost", this instance of Portmon should then be monitoring the PC's ports.

It seem that this setting is remembered when you close both instances and then just restart portmon without any parameters - as confirmed by poretmon's window title.

In
my case on WinXP SP 3, Computer menu item appeared in v3.02, and after I
connected to local machine and re-opened v3.03, it connected upon
openning (still no computer menu in v3.03, though). Probably v3.02
initialized some registry value to make the menu item appear (didn't
bother to look further into it). But.. don't see any captured data,
sadly.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum