Forum Replies Created
They will need to be using some kind of ftp client, possibly only the command prompt ftp client in Windows. Can you show us what the commands are, and how they are issued? There is no way to tell the password, because the password itself it not stored, only a hash of it. You need to reset it – or perhaps you could ask some of the other users using that account, what it is? I really can’t tell, as I have no idea how these services are implemented… It just looks like port 21 on no-ip is forwarded somewhere else. That is all I can see. This server log is very different from the first one you posted. This second log shows that the client is indeed writing out the welcome message from the server:
Response: 220-Cerberus FTP Server – Personal Edition
Response: 220 Welcome to FTP Server
The first log shows:
Response: 220 FTPU ready.
– so if there is no change in the server log, it must be because there are no loggings at all in the server log when connecting through no-ip, because it is not connecting to the right FTP server.
Yes, it could look like the client is not doing what it is supposed to. I can’t see anything specific in the client log, try to compare a client log from the inside with the client log from the outside. There must be some more in the server log, it doesn’t show the connection attempt at all. Wether it is possible do tweak intelligence in the router must depend on the router – but I doubt it very much. Somehow, low-end routers never have all the knobs and tweaks an advanced user needs…
Windows server probably does not do anything intelligent (ever!
). So it is the linksys router at the client’s site, that is messing things up – actually , it is intelligent, yes, but not intelligent enough. You don’t want to disable intelligence, rather activate it for a different port as well. That is why passive FTP was invented, to overcome all the non-intelligent routers.
I am pretty sure cuteFTP can do passive an also IE (Tools / Internet Options / Advanced / half way through the list of options), don’t know about the backup programs, and command line ftp in Windows can’t for sure.
You need to post logs showing a failed login – no ideas so far. Now I am pretty sure, that this is due to the router at the client’s end. If connecting to FTP on port 21, the router is intelligent and knows that it must replace the internal ip 10.0.0.18 with the external ip of the router within the PORT command. If port 22 is used, it doesn’t recognize it as FTP traffic, and then it doesn’t do the replacement.
Instead, you should use passive ftp from the client – if it is capable of doing so, but most clients are. What client are you using? This will of course require the passive port range to be forwarded on the server’s router – and it will require the server to be configured accordingly. The FAQ has info on this:
. http://www.cerberusftp.com/faq/initialsetup.htm#Q2http://www.cerberusftp.com/faq/initialsetup.htm#Q2 ” class=”bbcode_url”> The reason for this “half-connect” is quite simple. Several connections are used in FTP, and not just port 21 needs to be open/forwarded. (See .) The LIST requires a seperate data connection. http://www.mdjnet.dk/ftp.htmlhttp://www.mdjnet.dk/ftp.html ” class=”bbcode_url”>
If this is the setup, then I don’t understand that it works at all for port 21! According to the log, the FTP server is asked to connect to 10.0.0.18, but that ip does NOT make sense in your client’s 192.168-environment. Could you post a log that shows that it is working?
It could perhaps be an “intelligent” router somewhere? Some routers/firewalls know FTP, and when they see it, they automatically allow the ports selected for active ftp (at the client’s end) or passive ftp (at the server’s end) to be forwarded, but when it is carried by port 22, the router doesn’t recognize it.
I still don’t quite understand the ip addresses of your setup, and the routers involved. Have you manually configured port forwarding for the router/firewall at the client’s end?
[2010-01-04 08:38:37]:COMMAND [ 9] – PORT 10,0,0,18,206,23
This means that the client wants the server to connect to it on 10.0.0.18:52759 (active FTP), but that ip is perhaps a LAN ip on the client side that doesn’t make any sense for the server? I guess the client and the server are not located at the same place.December 2, 2009 at 3:54 pm in reply to: File xfers sucessfully, disconnects, then starts xfer again #35428
No suggestions, really… In my own router there is no changing that timeout, so – learn to live with it. Another option is to cut the file in smaller pieces, and reassemble it again on the other side…December 1, 2009 at 8:51 am in reply to: File xfers sucessfully, disconnects, then starts xfer again #35426 What catches my eye is that the first upload shown takes almost exactly 10 minutes, and that rings a bell. I have a “smart” router myself, that will cut tcp lines that have been idle for 10 minutes, and during upload of large files, the ftp control line is indeed idle. Not all ftp software can handle that the control line is cut (I believe Cerberus can though), so you could possibly try with another client, or simply try to verify the theory by timing an idle connection through the router(s) involved. In the latest release (188.8.131.52) the leaks on exiting (yes, exiting actually) the user manager and ip manager are still there. Also, there are quite a few GDI handles leaked in all three managers, and also in the about box.