Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

polarbearca

Re: I got the same problem!

Hi,
My problem is solved:

Probability the problem is the DNS Suffix option in the ipconfig.

When there is no DNS Suffix the winscp and puTTY do not work. But today after I started my computer I got the DNS Suffix then everything is fine.

Hope this helps.
polarbearca

I got the same problem!

Hi randy04,
I got the exactly same problems as yours. Including the putty failed thing.

The remote server is a linux system desktop belonging to my boss. He has the right login as root. So if you have any information about why this happens could you please reply here??

Thank you very much for your help!!

Cheers,
Guest

Re: Connection has been unexpectedly closed. Server sent command exit status 0.

martin wrote:

The only thing I can recommend you now is to ask your server administrator to check a SSH server log file for reason of the disconnection.
Thank you Martin, I will see what I can do today at work. I'll submit the logfile to someone in our Computing and Network Services area.
martin

Re: Connection has been unexpectedly closed. Server sent command exit status 0.

The only thing I can recommend you now is to ask your server administrator to check a SSH server log file for reason of the disconnection.
randy04

Connection has been unexpectedly closed. Server sent command exit status 0.

Hello Martin. I installed 3.7.0 today, and am getting the above error. I am trying to connect to a machine at the University of Alberta, where I work. When I am on campus, I can use WinSCP without a problem. I have searched the FAQ, and throughout the forum. All I can do is post my logfile here, and ask if you have any ideas why this is happening.

Oddly enough, I can also not connect using PuTTY 0.55. My logfile is below. Any help or suggestion would be appreciated. Many thanks - Randy

. --------------------------------------------------------------------------
. WinSCP Version 3.7.0 (Build 254) (OS 5.1.2600 Service Pack 1)
. Login time: October 13, 2004 11:18:22 PM
. --------------------------------------------------------------------------
. Session name: rreichar@gpu.srv.ualberta.ca
. Host name: gpu.srv.ualberta.ca (Port: 22)
. User name: rreichar (Password: Yes, Key file: No)
. Transfer Protocol: SFTP (SCP)
. SSH protocol version: 2; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. SSH Bugs: -,-,-,-,-,-,-,-,
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: /bin/bash, EOL: 0
. Local directory: default, Remote directory: home, Update: No, Cache: No
. Cache directory changes: Yes, Permanent: Yes
. Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. --------------------------------------------------------------------------
. Looking up host "gpu.srv.ualberta.ca"
. Connecting to 129.128.5.145 port 22
* (ESshFatal) Connection has been unexpectedly closed. Server sent command exit status 0.