Wesley Vogel wrote:
Wayne H. Wilhelm wrote:
I've tried running netstat -b (WinXP Pro w/SP2 + Admin priv).
The program runs.
Problem: The window disappears in aprox. 1 second.
netstat -b is not a proper command.
Actually, the -b switch was introduced with SP2 for WinXP.
Help output for netstat.exe on a WinXP SP2 computer:
Displays protocol statistics and current TCP/IP network connections.
NETSTAT [-a] [-b] [-e] [-n] [-o] [-p proto] [-r] [-s] [-v] [interval]
-a Displays all connections and listening ports.
-b Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in  at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
(snip rest of help listing)
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
- Re: Sniffer for Windows That Shows Process ID?
... Displays protocol statistics and current TCP/IP network connections. ... sequence of components involved in creating the connection ... or listening port is displayed. ... of components involved in creating the connection listening port for all executables. ...
- RE: How to find a process
... Displays protocol statistics and current TCP/IP network connections. ... In some cases well-known executables ... or listening port is displayed. ...
- Re: Semaphores and .NET
... The two applications are two separate executables that run ... it cannot hangup the connection. ... I have to make the access sharable between executables modules. ... >> Lead Project Software Engineer ...
- Re: Semaphores and .NET
... The two applications are two separate executables that run ... it cannot hangup the connection. ... >>> Lead Project Software Engineer ...
- Re: Script running infinitely when calling wscript.exe from code
... detecting the scripting engine could be made somewhat more bullet proof. ... Having renamed system executables would seem to be so likely to break a system that it would be reasonable, and even responsible, to ignore that possibility. ... And of course, if someone is renaming the executables, they might also rename the keys pointing to them... ... Why not use the File System Object's GetFileName and GetFileExtensionName methods? ...