If I open a Terminal, then I see the "Connecting" messages. Therefore, it seems terminal is running under a separate session. No? The article you linked seems to confirm that all terminal sessions run on a separate connection, no?
The article links to a different article, which might be more relevant.
https://winscp.net/eng/docs/ui_login_scp
The linked article is about other shell options (not about running in a separate session). One of these may be the cause of this error:
However, I am moving to a new host, due to several issues with 1and1 (including this issue). I'm not seeing this issue on my new host (namecheap). So I no longer need to resolve this issue. I'll leave it to others to experiment.
To support execution of remote command and a direct duplication of remote file, WinSCP can open a separate shell session to perform the commands. The shell session is opened automatically.
The article links to a different article, which might be more relevant.
https://winscp.net/eng/docs/ui_login_scp
The linked article is about other shell options (not about running in a separate session). One of these may be the cause of this error:
- Shell option: what shell WinSCP will use.
- Return code variable: what environment variable contains exit code of the last command.
- Listing command: what shell command WinSCP uses to list directory contents.
- Ignore LS warnings: ignore any error messages printed by the ls command.
- Clear aliases: clear all aliases on start-up.
- Clear national variables: clear environment variables known to influence directory listing.
- Use scp2 with scp1 compat: force the scp command to use really the SCP protocol.
However, I am moving to a new host, due to several issues with 1and1 (including this issue). I'm not seeing this issue on my new host (namecheap). So I no longer need to resolve this issue. I'll leave it to others to experiment.