RE: [cobalt-users] FTP problems on a RaQ4

["Rich LaBo" <rlabo@xxxxxxxxx>]

> >Subject: [cobalt-users] FTP problems on a RaQ4
> >
> >
> >Hi All, Hope your summers are going well.
> >
> >My problem is this. Some FTP users are having problems. They
> >can connect,
> >authenticate and then immediately the connection gets reset
> >by peer. I had
> >this same person use a different login id and password and
> >she connected
> >successfully, no reset. I've combed the archives with no
> >luck and I see
> >absolutely nothing changed in proftpd. Any ideas.
> >
> >Thanks,
> >
> >Rich
>
#################
> 	First bet would be to check if 'Passive/PASV' FTP
> mode is available, either by a check box or some sort of
> switch related to signing on to the FTP server.
>
> 	In many cases with DSL using the Efficient or PPPoE
> (PPP over Ethernet) hardware, we've found it a requirement
> to set it to passive mode and use the 'keep connection
> alive' settings in WSFTP to prevent problems.
>
> 	Even with that, there have been times when working
> for a short bit and then a smaller amount of inactivity
> than timers were set for goes by - it would still reset
> the connection on the Server side.
>
> 	Cable, at least with Adelphia/PowerLink and Time
> Warner/RoadRunner, having this mode ON would foul things
> up.  So if it's set as a default, it may need to be
> turned off.
>
> 	In rare cases with StarBand/DirectPC satellite
> based setups, we've found that the passive mode has to
> be on but using 'keep connection alive' settings would
> cause their 'predictive' style of connections (pre-
> guessing and cache-ing up pages so your connection
> appears faster than it really is) to freak out and
> drop you because your keep-alive requests were
> colliding with the cached requests (shouldn't be
> this way, but it's our experience) and causing mass
> confusion - then resets.
>
> 	Last note, we've found that using WSFTP in the
> mode where it cache's directory listings for a 'faster'
> working environment also caused problems with a RaQ.
> Once you pull down the first directory and it updates,
> if you had older versions cached and WSFTP didn't see
> any reason to update them, you think you're pulling
> directory listings and moving around when reality is
> that no commands are being sent to the Server so it
> believes you're inactive and resets the connection.
>
> 	Hope all this helps!
>
>       David J. Duffner
>       VP Operations
>       http://www.nwcxpress.com


David,

Thanks for the input. It's greatly appreciated.

The people trying to ftp are on a dedicated T1 (static IP's) that resolves
with no problems. I've had them try both active and passive with no luck as
well as the cached directory listing ticked. It strikes me as wierd that one
username is successful, but the other errors out. I can successfully connect
with the troubled account, but they cannot. I've been beating my head on the
desk for almost 2 weeks now with no avail. Ifconfig show everything as it
should and honestly, NOTHING has changed within the past 2 months on this
machine.