| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 139385 | 2015-04-24 08:35:00 | Filezilla client problem | BBCmicro (15761) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1399257 | 2015-04-24 08:35:00 | I have reinstalled WinPro64 but Filezilla client no longer connects. It used to connect before the reinstall but with a different version (I don't know what it was) The new version is 3.10.3 which is the latest The device I am trying to connect to is a media player/analogue video capture thingy (PBR-500). I've had it for about 6 years I think. (It accepts RGB input and captures in high quality from Sky or DVD player) As the picture shows, the media player seems to get recognised but rejects connection??? It has a wired connection to a wireless bridge (NP121). A blue light comes up on the bridge when I boot it (the problem device). The wireless bridge works OK for internet connection to a WD TV HD media player on an adjacent port to the problem device. The device does not show up in Windows Network Map but I don't think it did in the past either Any suggestions? I've done the normal re-booting of computer/device/bridge/router. Also used arp -a to get addresses to try. The connection worked in the past with 192.168.0.189 admin admin 21. That particular address currently shows up under arp -a (and I don't think it is identified with any other device) |
BBCmicro (15761) | ||
| 1399258 | 2015-04-24 17:06:00 | Well its connecting but auth is failing, why does it try TLS and SSL? Maybe it wants plain, its not SFTP that its connecting to. Cheers, KK |
Kame (312) | ||
| 1399259 | 2015-04-24 23:52:00 | OK, I decided to try a different client - Core FTP LE (chosen more-or-less at random. It's had 3m downloads since May 2014) It connected straight away and is giving over 1 MB/sec. That is a reasonable speed given the minimal resources in the device and a wireless bridge in the path So I guess there is an incompatibility between the server and client, probably a fault on the server side because the device is not a common one whereas Filezilla is (Just notice your post time Kame. Obviously you got up early to attend the dawn service.... ) |
BBCmicro (15761) | ||
| 1399260 | 2015-04-25 02:39:00 | SFTP should be on port 22 (to the SSH server) not 21. | fred_fish (15241) | ||
| 1399261 | 2015-04-26 00:03:00 | Without really seeing the commands that the other client sends I believe its because you are AUTH-ing using TLS or SSL. Which would means your client is forced into trying a secure connection that isn't supported at the other end. As I'm saying, SFTP isn't on port 21 and FileZilla wouldn't do this normally on that port without being told to. This means you've set up FileZilla to do this when default settings would be best to use unless you understand what changes you make affect your client. Reset FileZilla to default settings and leave it like that, really no need to change it. Cheers, KK |
Kame (312) | ||
| 1 | |||||