Visitor
•
2 Messages
Inability to FTP/upload to server
I have been VERY DISAPPOINTED in Comcast/Xfinity's obvious inability to comprehend and/or understand the inability to understand the FTP issue's being reported by many users and instead quickly mark as "resolved" ... or blamed on the outside server at the other end. The inability to listen to the full message and pertinent details being delivered by the client is also quite disturbing and insulting!
I have been using the same FTP settings across numerous computer systems and networks FOR YEARS. All have and continue to work flawlessly until recently connected on the xfinity home/residential network. IMPORTANT NOTE: they worked fine even on this network until the "newer" xfinity modem was installed. As mentioned in OTHER REPORTS, the FTP connection DOES find and connect to the remote computer, does negotiate password and login properly, does other mode changes, but fails (times out) due to no responses from the xfinity side! (I own the servers on the other end so we CAN monitor for debugging.) Obviously there is some incompatibility with these new modems or default settings.
I try to connect via a VPN and problems remain the same.
I can connect to my T-Mobile hotspot and things work flawlessly with the identical settings.
The [Edited: "Language"] responses from these forums should be embarrassing. The "help" from the "store" personnel is even worse and usually a TOTAL waste of time. Come on Comcast ...get your act together and get this FIXED!
flatlander3
Problem Solver
•
1.5K Messages
3 years ago
The use case, server OS, and ftp server software package information would be useful. Generally from what I remember, that ftp deadlock happens with both sides are firewalled and you can't get to the higher random port. In that case, it's probably better to change the server configuration. This stack overflow reply covers it nicely with iptables (if this link shows up and they don't scrub it):
https://stackoverflow.com/questions/26659223/appropriate-iptables-rules-for-an-ftp-server-in-active-passive-mode
I haven't messed with FTP in quite sometime, mostly due to plain text username/password, firewall maintenance config file hassle, and no need for anonymous connections. It's much easier to defend an open ssh port anyway on the server side, so sFTP/SCP is kind of the way to go here. You can do anonymous uploads with an http server too if you really want to (maybe not so much recommended though), it's faster, and you can encrypt the transfer, so I dunno.....there would have to be a compelling reason.....
If you are using Xfinity stuff, and you turn off their "advanced security", does it do what you want? I just use 3rd party gear.
0
user_6ec46d
Visitor
•
2 Messages
3 years ago
I did (also) disable their "Advanced Security" ..... same problem. The problem occurs across 4 different machines ... all of which were working fine BEFORE the swapout (upgrade?????) to this "newer" router. the systems are a mix of windows10 and linux (ubuntu) OSs. I will look into the sFTP/SCP but I think my real plan is just to move on from xfinity to something more reliable. This one incident has cost me many hours. Thanks for the heads-up on the sFTP client ... it looks to be good!
2
0
Jlavaseur
Problem Solver
•
948 Messages
3 years ago
I use FileZilla with both Linux and win 10, works beautifully, drag and drop interface, very easy to use, I use sftp with all my uploads and downloads, works great with the Xb7
0