(001360) 23:00:08 PM - (not logged in) ()> Connected, sending welcome message. You can the server sent out the passive mode response just before disconnecting. The first night I did not explicitly ask for a binary transfer. You can tell by the timestamps that in each case roughly one second (a little longer perhaps) transpires between the intitial connection and the final disconnect. Here are some log samples that show this with a little summary above each sample. Each time the command history in my server log is slightly different. I have tried various configurations on the client side. The disconnect does not consistently happen on any single command. I only have two ports open for passive mode and proof of successful transfers from other clients on both ports in my logs.ģ. My server has a 2 minute transfer timeout which it never hits.Ģ. the client tries to send through the passive mode port, the firewall blocks it then finally the server gives up waiting. in my experience client-side issues result in a time out. Let me try to explain my "one second server-side" theory as opposed to a firewall.ġ. When the client issues the STOR command it fails because it no longer has a connection.
The client authenticates fine and sends through a couple commands then after about one second it disconnects. My gut tells me it's on my side because there I'm not getting any timeouts or anything. I think it is a network issue but I haven't pinpointed exactly what or which side it's on. I have one client exhibiting some strange behavior.
We are behind a NAT and the external IP is set for passive mode. I think it's safe to say my configuration is good. Most are transferring over SSL though I recently opted to no longer force it. I have inhertied a FileZilla server instance that has been in production for years and a dozen or so clients that are successfully transferring files.
0 kommentar(er)
