FTP just hiked

[sue lange]

We've been running BM for years..3.0 through 3.7 where we now are with
the last round of patches applied. On top of NW6 sp3.

It's been running fine for a long time. Suddenly yesterday we started
having problems with FTP. We have a system inside the firewall where
folks do web design. Twice a day the updated results are published to a
web server outside the firewall. Been this way for years. Yesterday
morning it was fine, late in the day it won't publish because FTP times
out. This morning it is still timing out and this afternoon same thing.

Small files can get through randomly, larger files pretty much not.
Terminal services will crash whenever this happens, but can be resumed
once we cancel the attempted FTP session. HTTP seems to pretty much
work okay no matter what.

It's not just this one site either, else I would suspect the sending or
receiving station. Various complaints are coming in from all over the
building that folks can't FTP to a number of sites outside Border.

We've not made changes in a long while. I did monkey with some filters
Friday but they weren't FTP filters and even if they were, if it was a
filter problem shouldn't it just not work at all (as opposed to getting
started then time out and quit)? Does FTP use one port for
establishing the connection and doing list dirs and such then pick
another port for actual data transfer?

Nic card? How could other things like proxy to HTTP sites outside the
firewall work then?

This is just really a weird one.

Thanks for any ideas.

[Craig Johnson]

Check for duplex mismatches, and check for evidence of viruses causing
problems on the server itself.

If you think it is a filtering issue, you could try dropping the
filters for a brief test to confirm that.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

[D. SKye Hodges]

did you add, or change some filters to STATEFUL?  (Too many stateful filters can sometimes cause this problem)

>>> Craig Johnson<cra...@ix.netcom.com> 2003-11-18 21:37:42 >>>