🚀 go-pugleaf

I think his problem is, that he doesn't know what a port scan is, and so he
thinks he is being attacked. The fact that his computer crashes around the same
time makes him think the worst is happening.

Perhaps someone who actually knows what a port scan is (because I don't know),
should enlighten him and let him know what a port scan really is. It might put
him at ease.

I would suspect that he has some kind of conflict with McAfee, not enough RAM,
or something like that which causes the computer to crash when McAfee is
activated.


Edward wrote:
> haha u switched back to dial up b/c u experienced a port scan? i find that
> highly amusing b/c port scans are completely harmless especially when u have
> a firewall running.
>
> "HissyFit'n PaminiFarm" <nospam@newsranger.com> wrote
> > >> In news:soc.senior.issues, i clicked on a "Rita" post and got
> > >> disconnected and went through the
> > >> fatal error thingy with the scan disc and all; then i tried to close
> > >> down, and got another fatal error
> > >> with the blue screen where 'puter tried to come on; then i got an
> > >> illegal-act pop-up; desk top
> > >> turned all white and wanted to be restored; another fatal exception;
> > >> another whited-out desk top;
> > >> i pulled the plug; powered up 'puter went into another blue-screen
> > >> "Because you didnot close
> > >> down properly" another scan; 'puter came back on; i "restored"
> > >> desktop; McAfee virus scan was
> > >> found to be disabled. I changed ISP and am now not getting any port
> > >> attackes. I was on BellSouth DSL and am now on my old mom-n-pop
> > >> dial-up.
> > >>
> > >> What does all this mean?
> > >> From 09/09/02 12:47:53pm until i changed isp just now:
> > >> McAfee Firewall blocked an attempt to attack your machine using a
> > >> "Port Scan" attack.  The
> > >> remote address associated with the traffic was 12.129.72.135 (port
> > >> 20480).  The local port on
> > >> your PC was 14340.

[MAJOR SNIPPING DONE]