finding out which port an app is trying to connect to?

[yawnmoth]

I seem to recall there being some way one could view which ports were
being used by the currently open applications, via the command line.

eg. app a tries to connect to www.google.com:80 and this command line
tool would tell you.

Any ideas as to how one invokes this command?

[Detlev Dreyer]

"yawnmoth" > wrote:

> I seem to recall there being some way one could view which ports were
> being used by the currently open applications, via the command line.

netstat -abn

> eg. app a tries to connect to www.google.com:80 and this command line
> tool would tell you.

Not that way. Run "netstat /?" for help.

--
d-d

[Badger]

yawnmoth wrote:
> I seem to recall there being some way one could view which ports were
> being used by the currently open applications, via the command line.
>
> eg. app a tries to connect to www.google.com:80 and this command line
> tool would tell you.
>
> Any ideas as to how one invokes this command?
>
Hi yawnmoth
You could try Aports which is a windows app for monitoring your open
ports (like the dos netstat command}
www.download.com/3000-2085-10062969.html
Some antivirus programs think it is malware (guess your not supposed the
see these kind of things :-)

--
Badger,

The one who says it cannot be done
should never interrupt the one who is doing it.

[Haggis]

"Badger" > wrote in message
...
> yawnmoth wrote:
>> I seem to recall there being some way one could view which ports were
>> being used by the currently open applications, via the command line.
>>
>> eg. app a tries to connect to www.google.com:80 and this command line
>> tool would tell you.
>>
>> Any ideas as to how one invokes this command?
>>
> Hi yawnmoth
> You could try Aports which is a windows app for monitoring your open
> ports (like the dos netstat command}
> www.download.com/3000-2085-10062969.html
> Some antivirus programs think it is malware (guess your not supposed the
> see these kind of things :-)
>
> --
> Badger,
>
> The one who says it cannot be done
> should never interrupt the one who is doing it.

I use

http://www.ethereal.com/

[Tim Slattery]

"yawnmoth" > wrote:

>I seem to recall there being some way one could view which ports were
>being used by the currently open applications, via the command line.
>
>eg. app a tries to connect to www.google.com:80 and this command line
>tool would tell you.

Your browser may be trying to connect to port 80 at Google, but it's
not using port 80 on your computer. It's using a port number assigned
at random, though it will probably be above 1000. That's where
Google's response will be sent.

--
Tim Slattery
MS MVP(DTS)

[yawnmoth]

Haggis wrote:
> "Badger" > wrote in message
> ...
> <snip>
>
> I use
>
> http://www.ethereal.com/
That's been superceeded by Wireshark.

For what I was trying to do, though, Ethereal / Wireshark seems a
little overkill.