Further to my last reply and I really am out of my depth here!
The syslog message referring to 192.168.11.212 is interesting as I don’t have a device on my network with that IP address. I have an app called Fing which maps all my devices and I’m happy it has found everything.
There were error messages earlier on the syslog, when I wasn’t trying to connect, as follows:
Probably totally unrelated certainly no mention of SMB or Samba.
I haven’t configured firewall settings on the router, don’t know where to do it.
I’m confuse (no surprise there) you say neither FTP nor SMB work. I know I have typed in FTP:// etc which I guess is FTP access. How do I attempt SMB access.
SMB is the Windows file sharing protocol. It is what is used when you visit a network drive in the Windows File Explorer. This is what would have been used when you entered \\192.168.11.1 in the Run… dialog. The error message you got (“The network path was not found”) suggests that your PC was unable to contact an SMB service running at that IP address.
FTP is a different way of moving files between systems. It’s not really integrated into Windows like SMB is. FileZilla is an example of a program that can use FTP to transfer files.
Web browsers have traditionally been able to perform a limited version of FTP; when you enter an ftp:// URL, they will try to connect to the FTP service at that URL. However, I think they might be starting to remove that support. It’s difficult to tell if the error message you received when trying the ftp://192.168.11.1 URL was due to the service not running, or due to your browser not really knowing how to do FTP. That’s why a dedicated FTP client would be a better test.
A small thought, that almost certainly won’t make any difference: you could try making the Workgroup in the SMB settings match your computer’s workgroup. I doubt it’ll make any difference because I don’t think the workgroup is used when accessing an SMB host via IP address, but it wouldn’t hurt to try.
No, port 21 is just the default for FTP. The error is categorical: “Connection Refused” means that packets from your PC are making it to the device at 192.168.11.1, and the device is actively refusing them (it’s sending a response back saying that it won’t allow the connection).
Looking again at your first screenshot, I see you’ve entered a path with spaces in. I wonder if that could be a problem. Could you try removing spaces from the paths, both in the UI and on your disk?
Also, can you confirm that your drive is formatted as FAT32, as mentioned in this note:
Reluctantly today I updated the firmware on the router (probably I have been stupidly wary but I didn’t want to screw up my network).
FTP then worked fine with Filezilla and IE but not Chrome.
I shall shortly try and set up DDNS access which I have failed with in the past.
Thanks for your help.