Re: McAfee Firewall Blocking FTP

From: S. Miller (n7apeNOSPAM_at_amsat.org)
Date: 12/15/03 

Date: Sun, 14 Dec 2003 15:57:55 -0800

"J Jay" <jayjay@nevertell.net> wrote in message
news:MPG.1a469ef711d04c5c9896b6@news.east.earthlink.net...
> Hi S Miller. I don't remember the details, but sometime in the past
> I investigated how FTP works. FTP remote ports are 20 and 21. In
> addition to these, FTP also needs to connect on random, unpredictable
> high-end numbered remote ports. The firewall rule for my FileZilla FTP
> client looks like this:
> FileZilla, allow, both directions, remote ports 20,21,1024-65535, local
> ports 1024-2500
> Try this on your McAfee.
> For use of my browser on FTP, I have a similar rule in the firewall
> just for it. I go in and enable this rule and use the browser on FTP.
> When I finish using the browser on FTP, I turn this rule off.
> JJ

Thanks for your info. I added a rule to pass local port destinations
1024-65535 and that didn't help. Of course the problem occurs even when
McAfee firewall is told to "Allow All" for the ftp program. So a filter
somewhere else in McAfee firewall must be blocking the port 20 packet. It's
logging it in the McAfee logs, and ftp works if I shut off McAfee firewall.
I just can't figure out where *else* in the configuration of McAfee firewall
to allow the port 20 packet to get through. I'm wondering if it could be
hard-coded to block packets with high destination ports and it's changeable
by the user?

After posting my original message I found the McAfeeHelp forums but as of
yet have not found any solution there -- only a posting by another user with
the exact same problem as me, with several replies that unfortunately were
dead-ends. He posted that his "solution" was to switch ftp programs. To
me, that's a workaround, not a solution. ;-) I have a workaround as well,
but it'd sure be nice to be able to understand the actual problem and either
a solution or an explanation as to why it can't be solved (i.e. McAfee has a
hard-coded rule or something).

I'll keep investigating and report back if I get it solved.

Relevant Pages

  • Re: NTL WepSpace (FTP Uploading) Help required, please - Re: Back from Mountie Land
    ... So the prob *isn't* wit hthe Server then. ... definitely her McAfee Firewall Blocking it. ... Firewall was running OK & Disabled the McAfee Firewall ... It the Internet Explorer FTP thingy) Connected to the NTL FTP Server, ...
    (uk.people.silversurfers)
  • Re: Newbie question about ports.
    ... Can you do a CVSup to update your ports via http? ... Cvsup does not support http, but neither does it use ftp (see man cvsup, ... openable through your firewall. ...
    (freebsd-questions)
  • RE: FTP Server on SBS 2003
    ... When I access the ftp site ... In the properties the ftp is set to "all assigned ports" should this ... > You connect the SBS to a third party Router and forward port 21 to the SBS ... The network administrator of the server network can consult the ...
    (microsoft.public.windows.server.sbs)
  • RE: Passive FTP
    ... Some FTP servers are able to set the passive ports he can use, ... Onderwerp: Passive FTP ... Dit E-mail bericht is slechts bestemd voor de persoon aan wie het is ...
    (Security-Basics)
  • Re: FTP server behind a PF firewall (including NAT)
    ... Philip> have exactly the same problem. ... Philip> huge range of high ports, and I can't find any information ... IPFW is a real pain compared to most modern firewall software. ... address-translate) the FTP data transfers. ...
    (comp.unix.bsd.freebsd.misc)
Quantcast