Still getting the same error
Sentinel Stopped Working
- Thread starter todd818
- Start date
- Status
Same error on both
Re-downloaded, re-installed / repaired, still getting error
Even tried shutting off all virus protection / firewalls
Did that too
Usually problems with PASV mode FTP are server configuration, but since only a very small number of people are having them, it seems more likely there's something between you and Uniden's FTP server that's blocking the connection.
In active-mode FTP, the client makes a command-and-control connection to the server's port 21. Then for file transfer, the client starts listening on a random port, then sends that port # to the server over the C&C connection, then the server connects back to the client on that random port, then file transfer happens on that new data connection. But firewalls, NAT, etc., break that [because some of them won't allow the incoming connection from the firewall, although some can deep-inspect what's going on and handle it].
Passive mode supposedly fixes that. When the client sends PASV to the server (which Sentinel does for you to Uniden's server), the server starts listening on another port, and then sends that port # back to the client, which then initiates an outbound to the server [which doesn't cause a problem with firewalls, NAT, etc.], and the data transfer takes place on that connection. I.e., the opposite of active mode.
Your clients are hanging after the PASV command, so I'm guessing that when they try to establish that connection with Uniden's FTP server on the port that the server sent them [in scanster305's case, port 8*256+153 = 2201, but it will be different every time], something is blocking that. Maybe your ISP [I've heard Hughesnet users have PASV mode issues]. Maybe a firewall [are you sure you turned Windows firewall off?]. You might have to get someone to snoop the network session to see exactly what's happening before you can figure out why.
In active-mode FTP, the client makes a command-and-control connection to the server's port 21. Then for file transfer, the client starts listening on a random port, then sends that port # to the server over the C&C connection, then the server connects back to the client on that random port, then file transfer happens on that new data connection. But firewalls, NAT, etc., break that [because some of them won't allow the incoming connection from the firewall, although some can deep-inspect what's going on and handle it].
Passive mode supposedly fixes that. When the client sends PASV to the server (which Sentinel does for you to Uniden's server), the server starts listening on another port, and then sends that port # back to the client, which then initiates an outbound to the server [which doesn't cause a problem with firewalls, NAT, etc.], and the data transfer takes place on that connection. I.e., the opposite of active mode.
Your clients are hanging after the PASV command, so I'm guessing that when they try to establish that connection with Uniden's FTP server on the port that the server sent them [in scanster305's case, port 8*256+153 = 2201, but it will be different every time], something is blocking that. Maybe your ISP [I've heard Hughesnet users have PASV mode issues]. Maybe a firewall [are you sure you turned Windows firewall off?]. You might have to get someone to snoop the network session to see exactly what's happening before you can figure out why.
Thanks for the info. I’ve always suspected that this is some kind of permissions / port issue but have not been able to find a fix. All AV and FW are off but error persists. ISP is AB. I can try using a diff isp and will advise further. TY again.
Just tried with an alternate ISP, no joy...
- Status
