Re: McAfee BellSouth DSL Conflict?

Article View: alt.comp.virus

Article #349

#349

From: toolman
Date: Tue, 30 Jul 2002 15:25

40 lines
2793 bytes

"Pamini" <nospam@newsranger.com> wrote in message
news:Y6g19.31988$15.10497@www.newsranger.com...
> Hello,
>
> My BellSouth DSL willnot run with the McAfee Fire Wall on.
>
> Does anyone have this problem or know anything about it?
>
> Is there a configuration on McAfee for this Problem:
> If i start up The BellSouth DSL first; then second, the
> McAfee Fire Wall, i can usually get the BellSouth DSL
> to run for about 5 minutes. If i try to start the
> BellSouth DSL while the McAfee Fire Wall is on,
> The BellSouth DSL willnot sart up at all.
>
> The McAfee Fire Wall log is often saying, "Blocked
> A Port Scan Attack", also it Blocks incoming and
> outgoing TCP a lot, then finally after about 5
> minutes of this, the DSL just quits all together.
>
> Why is it "a bad thing" for TCP's to be coming in
> an out - what do they do that is "bad" (Violation)?
>
> Does anyone know how to configure McAfee of BellSouth
> DSL around to stop his problem?
>
> Yesterday at Best Buy, they told me McAfee isnot
> configured for DSL, but is configured only for
> dial-up. Is this a popular opinion or a fact?
>
> I donot have this problem with my mom-n-pop
> dial-up ISP as you can see.
>
> Pamini
>
>

hey all right I see F WAS is back posting SOS !!!!!

that would be format c: @!#$%^&@

Technical Details

Message-ID: <j1y19.79591$Og3.20348388@e3500-atl1.usenetserver.com>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!news.gtei.net!news-out.visi.com!hermes.visi.com!newsfeeds-atl2!news.webusenet.com!pc01.webusenet.com!e3500-atl1.usenetserver.com.POSTED!not-for-mail

References: <Y6g19.31988$15.10497@www.newsranger.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fcd68,598046ebfe4d0f7e
X-Google-Attributes: gidfcd68,public
X-Google-Thread: 1122a6,598046ebfe4d0f7e
X-Google-Attributes: gid1122a6,public
X-Google-Thread: faa3c,598046ebfe4d0f7e
X-Google-Attributes: gidfaa3c,public
X-Google-Thread: 1070cf,598046ebfe4d0f7e
X-Google-Attributes: gid1070cf,public
X-Google-ArrivalTime: 2002-07-30 08:25:26 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!news.gtei.net!news-out.visi.com!hermes.visi.com!newsfeeds-atl2!news.webusenet.com!pc01.webusenet.com!e3500-atl1.usenetserver.com.POSTED!not-for-mail
Reply-To: "toolman" <tooltep@be.org>
From: "toolman" <tooltep@be.org>
Newsgroups: alt.comp.virus,bellsouth.net.support.adsl,alt.windows98,24hoursupport.helpdesk
References: <Y6g19.31988$15.10497@www.newsranger.com>
Subject: Re: McAfee BellSouth DSL Conflict?
Lines: 43
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <j1y19.79591$Og3.20348388@e3500-atl1.usenetserver.com>
X-Complaints-To: abuse@usenetserver.com
X-Abuse-Info: Please be sure to forward a copy of ALL headers
X-Abuse-Info: Otherwise we will be unable to process your complaint properly.
NNTP-Posting-Date: Tue, 30 Jul 2002 11:12:15 EDT
Organization: WEBUSENET.com
Date: Tue, 30 Jul 2002 11:25:18 -0400

Reply to Parent Message