ICMP from my WinXP

[Tumurbaatar S.]

Hi all!

My WinXP SP2's Windows Firewall blocks UDP packets
going from some remote host. And it works well. As I see in
firewall log file (it logs dropped packets).
Now my application is catching these packets because
Windows Firewall automatically detects this and unblocks (after
asking me) a needed port. But my system starts to send ICMP
packets to the remote machine and firewall blocks them:

....DROP ICMP my_ip remote_ip - - 176 - - - - 3 3 - SEND

It continues several minutes. What does my Windows send out?

 

[Chuck]

Hi all!

My WinXP SP2's Windows Firewall blocks UDP packets
going from some remote host. And it works well. As I see in
firewall log file (it logs dropped packets).
Now my application is catching these packets because
Windows Firewall automatically detects this and unblocks (after
asking me) a needed port. But my system starts to send ICMP
packets to the remote machine and firewall blocks them:

...DROP ICMP my_ip remote_ip - - 176 - - - - 3 3 - SEND

It continues several minutes. What does my Windows send out?

Please clarify "packets going from" - did you mean "packets coming from" or
"packets going to"? Here precise grammar is essential.

For a better idea of what these mysterious packets are, get Port Explorer (free)
from <http://www.diamondcs.com.au/portexplorer/index.php?page=home> to show you
what network connections your computer is actually opening, and what processes
are opening them. The paid version includes a mini packet sniffer, which you
may, in this case, need.
And Process Explorer (free) from
<http://www.sysinternals.com/ntw2k/freeware/procexp.shtml>. Provides way more
information than Task Manager. Also, Autoruns (also free, and also from
SysInternals) <http://www.sysinternals.com/ntw2k/freeware/autoruns.shtml> will
show you specifically what process are started automatically.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.