Being disconected from Filezilla server after successful log

[spryguy]

000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 230 Logged on
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> PWD
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 257 "/" is current directory.
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> PWD
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 257 "/" is current directory.
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> CWD /hmi
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 250 CWD successful. "/hmi" is current directory.
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> PWD
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 257 "/hmi" is current directory.
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> CWD /hmi
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 250 CWD successful. "/hmi" is current directory.
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> PORT 192,168,1,2,12,35
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 200 Port command successful
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> TYPE A
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 200 Type set to A
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> LIST
(000040) 5/14/2012 18:45:33 PM - inetadmin (166.248.35.181)> 150 Opening data channel for directory list.
(000040) 5/14/2012 18:45:43 PM - inetadmin (166.248.35.181)> ABOR
(000040) 5/14/2012 18:45:43 PM - inetadmin (166.248.35.181)> 226 ABOR command successful
(000040) 5/14/2012 18:45:43 PM - inetadmin (166.248.35.181)> QUIT
(000040) 5/14/2012 18:45:43 PM - inetadmin (166.248.35.181)> 221 Goodbye
(000040) 5/14/2012 18:45:43 PM - inetadmin (166.248.35.181)> disconnected.



Passive mode does not work either. We have used FileZilla before successfully on another PC.

local ip of the pc is 192.168.1.240.

Can anyone assist with ideas to stay connected? The end directory is wwwroot/hmi

Thanks

[boco]

The client sends an ABOR command, thus it's the client aborting the connection, not FileZilla Server. Besides, the client isn't configured correctly for Active (PORT) mode, it sends an invalid IPv4 along with port (192.168.1.2 is a private IPv4).

Would like to see a log for Passive mode, maybe the server is also configured wrong.