Re: false portscan alarm
- From: "GEO" Me@xxxxxxxxx
- Date: Thu, 19 Oct 2006 03:56:15 GMT
On Wed, 18 Oct 2006 15:58:51 +0100, "Spack" <news@xxxxxxxxxxxxxxxx>
wrote:
Or those packets are simply responses to connections initiated from the
user end and closed prematurely. For instance, the user opened a browser
to www.microsoft.com,.........[snip]
This is just the usual sort of completely harmless and normal activity
that these so called "personal firewalls"..............[snip]
I would disagree with your explanation since I have no firewall, and
don't connect to MS, and yesterday I was receiving UDP packets from
the same range of addresses ( 207.46.18.xx). Today I have received UDP
packets from 204.16.208.74.
You have nothing connecting to MS at all? No windows machine with automatic
updates enabled? No MSN messenger? Windows Messenger? Looks like some recent
UDP packets from that IP have been MSN/Windows messenger spam (which is
possible as normal chat messages are sent via the MS Messenger proxy
servers, which this IP could also be a member of), but without more
information (like packet traces for instance) everything is just
speculation.
Right. See Ibuprofin's explanation.
I use Windows 3.1, it does not even know what is this Messenger
thing. Updates? What's that?
Geo
.
- Follow-Ups:
- Re: false portscan alarm
- From: Moe Trin
- Re: false portscan alarm
- References:
- false portscan alarm
- From: mikahan
- Re: false portscan alarm
- From: Bit Twister
- Re: false portscan alarm
- From: Spack
- Re: false portscan alarm
- From: GEO
- Re: false portscan alarm
- From: Spack
- false portscan alarm
- Prev by Date: Re: Filter Internet NAT Redirection
- Next by Date: Re: false portscan alarm
- Previous by thread: Re: false portscan alarm
- Next by thread: Re: false portscan alarm
- Index(es):
Relevant Pages
|