Article View: alt.comp.virus
Article #351Re: McAfee BellSouth DSL Conflict?
From: Shaken
Date: Mon, 29 Jul 2002 19:04
Date: Mon, 29 Jul 2002 19:04
43 lines
2940 bytes
2940 bytes
you are just an idiot. if you configure it correctly it will work. if you are you it will not work because you cannot get it through your head that DSL is not the problem it's the configuration of the firewall. go away "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 > >
Technical Details
Message-ID:
<K9g19.74318$Og3.16941214@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!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!cyclone.swbell.net!easynews!ps01-sjc1!news.webusenet.com!pc01.webusenet.com!e3500-atl1.usenetserver.com.POSTED!not-for-mailReferences:
<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: faa3c,598046ebfe4d0f7e X-Google-Attributes: gidfaa3c,public X-Google-Thread: 1122a6,598046ebfe4d0f7e X-Google-Attributes: gid1122a6,public X-Google-Thread: 1070cf,598046ebfe4d0f7e X-Google-Attributes: gid1070cf,public X-Google-ArrivalTime: 2002-07-29 12:05:39 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!nycmny1-snh1.gtei.net!cambridge1-snf1.gtei.net!news.gtei.net!bos-service1.ext.raytheon.com!cyclone.swbell.net!easynews!ps01-sjc1!news.webusenet.com!pc01.webusenet.com!e3500-atl1.usenetserver.com.POSTED!not-for-mail From: "Shaken" <shaken_1@yahoo.com> 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: 45 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Message-ID: <K9g19.74318$Og3.16941214@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: Mon, 29 Jul 2002 14:52:26 EDT Organization: WEBUSENET.com Date: Mon, 29 Jul 2002 14:04:01 -0500