Differences
This shows you the differences between the selected revisions of the page.
| 2020-12-23 | 2020-12-25 | ||
| normalizing link (martin) | automatically using target article title for link anchor (martin) | ||
| Line 16: | Line 16: | ||
| * Read guide for [[guide_connect|connecting to FTP/SFTP server]]. | * Read guide for [[guide_connect|connecting to FTP/SFTP server]]. | ||
| * Try if you can connect with other clients using the same protocol. | * Try if you can connect with other clients using the same protocol. | ||
| - | * If you can connect with another client, check [[faq_connection_refused|why WinSCP may not be able to connect to a server when other clients are]]. | + | * If you can connect with another client, see [[faq_connection_refused|*]]. |
| * When using SFTP/SCP, it may be useful to try to connect with an SSH terminal client (such as [[&url(putty)|PuTTY]]). You may get some useful messages back on the terminal screen. | * When using SFTP/SCP, it may be useful to try to connect with an SSH terminal client (such as [[&url(putty)|PuTTY]]). You may get some useful messages back on the terminal screen. | ||
| * Check other [[faq#connecting|F.A.Q. on connection]]. | * Check other [[faq#connecting|F.A.Q. on connection]]. | ||
| Line 29: | Line 29: | ||
| * Turn on [[logging|session logging]] using [[commandline#logging|''/log'' command-line switch]] and check the generated log file to see, if WinSCP actually does what you want it to do. IF you are having problems with password authentication, enable password logging using [[commandline#logging|''/loglevel=*'' command-line switch]] and check the log, if a correct password is being used. | * Turn on [[logging|session logging]] using [[commandline#logging|''/log'' command-line switch]] and check the generated log file to see, if WinSCP actually does what you want it to do. IF you are having problems with password authentication, enable password logging using [[commandline#logging|''/loglevel=*'' command-line switch]] and check the log, if a correct password is being used. | ||
| * If no session log is created, chances are that some error prevented WinSCP from starting, creating a log, or starting a session. Check WinSCP console output for any error. It is recommended to execute ''[[executables|winscp.com]]'' from existing console window (such as from Windows ''cmd.exe''). The ''winscp.com'' inherits the console((A ''winscp.exe'' always creates a new console that closes when WinSCP finishes.)) and when it exits with an error, the error is preserved on the console, allowing you to inspect it. | * If no session log is created, chances are that some error prevented WinSCP from starting, creating a log, or starting a session. Check WinSCP console output for any error. It is recommended to execute ''[[executables|winscp.com]]'' from existing console window (such as from Windows ''cmd.exe''). The ''winscp.com'' inherits the console((A ''winscp.exe'' always creates a new console that closes when WinSCP finishes.)) and when it exits with an error, the error is preserved on the console, allowing you to inspect it. | ||
| - | * See also [[guide_debugging_scheduler|Debugging transfer task running in Windows Scheduler, SSIS, or another automation service]]. | + | * See also [[guide_debugging_scheduler|]]. |
| - | * If you cannot log in or transfer the file using a script, yet you can log in or transfer the file in GUI, see [[faq_script_vs_gui|Why I cannot connect/transfer using script, when I can using GUI?]] | + | * If you cannot log in or transfer the file using a script, yet you can log in or transfer the file in GUI, see [[faq_script_vs_gui|*]] |
| ===== [[timestamps]] Troubleshooting Timestamp Issues ===== | ===== [[timestamps]] Troubleshooting Timestamp Issues ===== | ||