Putty 0.53b: Packet Type 95 Error?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
Able to sucessfully SSH into web server for administratioon. But when
attempting to transfer files via pscp:

pscp -p -r -v -2 e:/foo.bar server:e:/foo.bar

Host key fingerprint is:
ssh-dss 2048 3c:70:1d:88:21:b8:13:02:ed:63:de:f1:71:08:64:86
Using username "root".
Reading private key file "F:\PuTTY-0.53b\Keyring\server.ppk"
Offered public key
Offer of public key accepted
Authenticating with public key "@server"
Passphrase for key "@server":
Further authentication required
Further authentication required
root@xxx.xxx.xxx.xxx's password:
Sent password
Access granted
Opened channel for session
Primary command failed; attempting fallback
Unexpected response to shell/command request: packet type 95
Fatal: Unexpected response to shell/command request: packet type 95

What does Fatal: Unexpected response to shell/command request: packet
type 95 refer to? Question also posted in comp.security.ssh as
recommended per Putty Feedback page.

Version: Putty 0.53b
Client OS: Windows XP Pro
Server OS: Windows Server 2003
Protocol: SSH2

Adam Lau

Re: Putty 0.53b: Packet Type 95 Error?

SSH-2 message 95 is an "extended data" channel message, usually used to
send stderr.  My guess is that your login process (shell startup, .login,
etc.) is sending something to stderr and putty doesn't like it, though I
can't duplicate the problem.

  Richard Silverman

Re: Putty 0.53b: Packet Type 95 Error?

Quoted text here. Click to load it

PuTTY doesn't expect the server to start sending channel data until
after it's started up whatever process PuTTY asked for (shell,
command, subsystem). It looks to me as if the EXTENDED_DATA message
came in before the response to the channel request that was supposed
to start a process in the session.

Reading the draft spec carefully, it looks as if sending
EXTENDED_DATA at this stage is not actually prohibited, so I suppose
I ought to be able to deal with it. It hadn't previously occurred to
me that anyone would want to - how can the process be sending data
before it's started?

(I'd be interested to see what was _in_ that EXTENDED_DATA message.
My guess would be an error message explaining why the requested
command couldn't be run, or similar.)
Simon Tatham         "loop, infinite _see_ infinite loop"

Site Timeline