Differences
This shows you the differences between the selected revisions of the page.
| 2007-10-12 | 2008-02-13 | ||
| created (martin) | filewalls checking executable file fingerprint (martin) | ||
| Line 1: | Line 1: | ||
| ====== Why is WinSCP not able to connect to a server, when other clients are? ====== | ====== Why is WinSCP not able to connect to a server, when other clients are? ====== | ||
| If you are getting an error message like "Connection refused" or "Connection timed out", it is likely that there is a local firewall set up with per-application rules. The rules may allow the other clients, but not WinSCP. | If you are getting an error message like "Connection refused" or "Connection timed out", it is likely that there is a local firewall set up with per-application rules. The rules may allow the other clients, but not WinSCP. | ||
| + | |||
| + | You may also start getting the error after upgrading WinSCP. Some firewalls check executable file fingerprint. As the executable file changes with upgrade, the firewall starts blocking the executable, although you may have added exception rule for WinSCP already. | ||
| On Windows XP SP2 and newer, there is a built-in firewall. To configure its rules go to //Start > Settings > Control Panel > Windows Firewall > Exceptions//. There you can add an exception for ''winscp.exe''. | On Windows XP SP2 and newer, there is a built-in firewall. To configure its rules go to //Start > Settings > Control Panel > Windows Firewall > Exceptions//. There you can add an exception for ''winscp.exe''. | ||