Fails to connect with SCP to Synology DSM 5.1-5004

Hi.

I have been using WinSCP succesfully to connect to my synology NAS using SCP for a long time. After the latest Synology upgrade to DSM 5.1-5004 WinSCP fails to complete the initialization.

Authentication works fine, but the next step of checks fails, not sure which...
Synology uses their own shell, ash.

I am able to login with Putty and use ls -la without any problems.


With Debug2:

. 2014-11-27 19:48:25.540 Using SCP protocol.
. 2014-11-27 19:48:25.540 Doing startup conversation with host.
. 2014-11-27 19:48:25.602 Skipping host startup message (if any).
! 2014-11-27 19:48:25.602 7
. 2014-11-27 19:48:25.602 Sent 36 bytes
. 2014-11-27 19:48:25.602 There are 0 bytes remaining in the send buffer
. 2014-11-27 19:48:25.602 Looking for network events
. 2014-11-27 19:48:25.602 Timeout waiting for network events
. 2014-11-27 19:48:25.602 Sent 1 bytes
. 2014-11-27 19:48:25.602 There are 0 bytes remaining in the send buffer
. 2014-11-27 19:48:25.602 Looking for network events
. 2014-11-27 19:48:25.602 Timeout waiting for network events
> 2014-11-27 19:48:25.602 echo "WinSCP: this is end-of-file:0"
. 2014-11-27 19:48:25.602 Waiting for another 1 bytes
. 2014-11-27 19:48:25.602 Looking for incoming data
. 2014-11-27 19:48:25.602 Looking for network events
. 2014-11-27 19:48:25.633 Detected network event
. 2014-11-27 19:48:25.633 Enumerating network events for socket 800
. 2014-11-27 19:48:25.633 Enumerated 1 network events making 1 cumulative events for socket 800
. 2014-11-27 19:48:25.633 Handling network read event on socket 800 with error 0
. 2014-11-27 19:48:25.633 Received 2 bytes (1)
. 2014-11-27 19:48:25.633 Waiting for another 1 bytes
. 2014-11-27 19:48:25.633 Looking for incoming data
. 2014-11-27 19:48:25.633 Looking for network events
. 2014-11-27 19:48:40.646 Timeout waiting for network events
. 2014-11-27 19:48:40.646 Waiting for data timed out, asking user what to do.
. 2014-11-27 19:48:40.646 Asking user:
. 2014-11-27 19:48:40.646 **Host is not communicating for 15 seconds.
. 2014-11-27 19:48:40.646
. 2014-11-27 19:48:40.646 Wait for another 15 seconds?** ()
. 2014-11-27 19:48:41.157 Pooling for data in case they finally arrives
. 2014-11-27 19:48:41.191 Looking for network events
. 2014-11-27 19:48:41.191 Timeout waiting for network events
. 2014-11-27 19:48:41.659 Pooling for data in case they finally arrives
. 2014-11-27 19:48:41.701 Looking for network events
. 2014-11-27 19:48:41.701 Timeout waiting for network events
. 2014-11-27 19:48:42.162 Pooling for data in case they finally arrives
. 2014-11-27 19:48:42.193 Looking for network events
. 2014-11-27 19:48:42.193 Timeout waiting for network events
. 2014-11-27 19:48:42.271 Attempt to close connection due to fatal exception:
* 2014-11-27 19:48:42.271 **Terminated by user.**
. 2014-11-27 19:48:42.271 Closing connection.
. 2014-11-27 19:48:42.271 Sending special code: 12
. 2014-11-27 19:48:42.271 Sent EOF message
. 2014-11-27 19:48:42.271 Selecting events 0 for socket 800
* 2014-11-27 19:48:42.349 (EFatal) **Terminated by user.**
* 2014-11-27 19:48:42.349 Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended).
! 2014-11-27 19:48:44.677 8

BR
Bolleboll

Do you know what the "7" means?

I think this is the escape charcaters that is given for the prompt.

If i make a guess i think it is like this:

7 = play bell (an ASCII bell character (07))
[ [ begin a sequence of non-printing characters,
which could be used to embed a terminal con­
trol sequence into the prompt
r = carriage return
999;999 = not sure
H = the hostname
6 = ack?
n = newline

https://tldp.org/HOWTO/Bash-Prompt-HOWTO/bash-prompt-escape-sequences.html
https://www.asciitable.com/

Well, I know it's an escape sequence. But do you know why it's there? In general, WinSCP won't work well over a session that uses this.
See https://winscp.net/eng/docs/requirements#remote_environment

Hi.

Thank you for the information. Synology released an update DSM 5.1-5021, and after that it was possible to use winSCP again. Perhaps they changed the bash settings?

/bolleboll