Internal client is expecting FTP traffic to come back with source 1.2.3.4 and discards response from 10.0.0.1.FTP server sends response back directly to 10.0.0.100 with source address 10.0.0.1 and never goes back out the firewall since it sees the local source address.Firewall has a rule that sends port 21 traffic to 10.0.0.1 and sends the traffic to 10.0.0.1 sending it with a true source address of the client IP (10.0.0.100).
Internal client sends traffic to default gateway/firewall. The traffic flow for your current setup would basically goes as follows (using example IP's): I'm stuck on this one laptop connecting easily at home.What you are trying to do generally won't work without reconfiguration on the firewall/NAT device. The FTP clients generate a generic error message that basically says a connection could not be established and/or time out. I've tried using CuteFTP, Filezilla, WinSCP and Windows explorer over wired and wireless devices. I've turned off the firewalls and deactivated anti-virus protection on all 5 of my machines (all Win 10) for testing purposes. Make sure you have permsission to access that folder.Ģ27 Entering Passive Mode (10,0,0,xx,xxx,xxx) If I take it across town to my office, I get error message:Īn error occurred opening that folder on the FTP server. I've set up a Windows 10 file server on a desktop wired to my local network and it's accessible over my local network, but I can only connect to it over internet with one computer, a laptop over wireless, and only when connected to my LAN at home.
0 kommentar(er)
