Re: [masq] Ftp server behind firewall?

[Mark]

Well I can't give you the answer to your problem, but I do have a
work-around.  I am in a similar situation but my NT box also boots to
Linux.  Ftp works fine in NT using War FTPD, but when I boot to Linux I get
that bind error.  You can get War software at
http://www.jgaa.com/downloadpage.htm .  I think it may have to do with the
'Fool my brain dead ISP! (dont bind to port 20)' option, but I know little
about this.  That's your best bet.  It's a great program too.  

As for me, I'd rather be in Linux more but I cant find a way around that
bind problem.  If you hear anything, let me know please.  I have asked the
same question here and got no respose.  Lets hope you do.


At 12:26 AM 3/18/98 -0500, you wrote:

   I have a need for there to be a ftp server behind the firewall, 
I am assuming that it can be done.  I have used redir for port 21 and can 
connect to the server but when I try to get a listing or file it spits
this at 
me:  

ftp ls
500 Invalid PORT Command.
ftp: bind: Address already in use
ftp ls
500 Invalid PORT Command.
ftp dir
500 Invalid PORT Command.

I have tried using redir on port 20 and using udpred on 21 and 20 but keep
getting the same error messages, I have not yet tried ipautofw.
The machine is a NT box with the microsoft ftp server; I don't think that it 
makes a difference.

-- 
Andrew L. DavisNetwork Operations
[EMAIL PROTECTED]  ViperLink International
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]

[masq] Timeouts and very slow response through masq server

[Jeff Adams]

I think this was discussed recently, but, with the new mail server the
thread in the archives is gone.

Several machines which are masqueraded work fine one day and then randomly
experience one of two problems -

Applications will take minutes to respond rather than seconds.
or
Applications that were working simply go into a wait forever state trying
to get to a registered IP host.

Rebooting the client in question dosen't clear the problem.

Everything is connected via 10BaseT Ethernet.

When I boot the Linux box the problem usually clears for some amount of time.
Then either the same or a different node misbehaves.

The MTU on the interfaces are currently set for 1500
The masq rule is to allow masq to/from everywhere
ipfwadm -F -a masq -S 192.168.15.0/24 -D 0.0.0.0/0

Thanks in advance.

Jeff
Jeff Adams

[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]