Worse still, in a remote-to-local copy you have to specify the local file name explicitly, otherwise PSCP will complain that they don't match (unless you specified the -unsafe option). The following command will give an error message:
c:\>pscp user@host:"\"oo er\"" .
warning: remote host tried to write to a file called 'oo er'
when we requested a file called '"oo er"'.
Instead, you need to specify the local file name in full:
c:\>pscp user@host:"\"oo er\"" "oo er"
If PSCP is using the newer SFTP protocol, none of this is a problem, and all filenames with spaces in are specified using a single pair of quotes in the obvious way:
pscp "local file" user@host:
pscp user@host:"remote file" .
A.7 Troubleshooting
•
A.7.1 Why do I see ‘Incorrect MAC received on packet’?
•
A.7.2 Why do I see ‘Fatal: Protocol error: Expected control record’ in PSCP?
•
A.7.3 I clicked on a colour in the Colours panel, and the colour didn't change in my terminal.
•
A.7.4 Plink on Windows 95 says it can't find WS2_32.DLL.
•
A.7.5 After trying to establish an SSH-2 connection, PuTTY says ‘Out of memory’ and dies.
•
A.7.6 When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.
•
A.7.7 PSFTP transfers files much slower than PSCP.
•
A.7.8 When I run full-colour applications, I see areas of black space where colour ought to be, or vice versa.
•
A.7.9 When I change some terminal settings, nothing happens.
•
A.7.10 My PuTTY sessions unexpectedly close after they are idle for a while.
•
A.7.11 PuTTY's network connections time out too quickly when network connectivity is temporarily lost.
•
A.7.12 When I cat a binary file, I get ‘PuTTYPuTTYPuTTY’ on my command line.
•
A.7.13 When I cat a binary file, my window title changes to a nonsense string.
•
A.7.14 My keyboard stops working once PuTTY displays the password prompt.
•
A.7.15 One or more function keys don't do what I expected in a server-side application.
•
A.7.16 Since my SSH server was upgraded to OpenSSH 3.1p1/3.4p1, I can no longer connect with PuTTY.
•
A.7.17 Why do I see ‘Couldn't load private key from ...’? Why can PuTTYgen load my key but not PuTTY?
•
A.7.18 When I'm connected to a Red Hat Linux 8.0 system, some characters don't display properly.
•
A.7.19 Since I upgraded to PuTTY 0.54, the scrollback has stopped working when I run screen.
•
A.7.20 Since I upgraded Windows XP to Service Pack 2, I can't use addresses like 127.0.0.2.
•
A.7.21 PSFTP commands seem to be missing a directory separator (slash).
•
A.7.22 Do you want to hear about ‘Software caused connection abort’?
•
A.7.23 My SSH-2 session locks up for a few seconds every so often.
•
A.7.24 PuTTY fails to start up. Windows claims that ‘the application configuration is incorrect’.
•
A.7.25 When I put PuTTY in C:\WINDOWS\SYSTEM32 on my 64-bit Windows system, ‘Duplicate Session’ doesn't work.
A.7.1 Why do I see ‘Incorrect MAC received on packet’?
One possible cause of this that used to be common is a bug in old SSH-2 servers distributed by ssh.com. (This is not the only possible cause; see
section 10.11
 in the documentation.) Version 2.3.0 and below of their SSH-2 server constructs Message
Authentication Codes in the wrong way, and expects the client to construct them in the same wrong way. PuTTY constructs the MACs correctly by default, and hence these old servers will fail to work with it.
If you are using PuTTY version 0.52 or better, this should work automatically: PuTTY should detect the buggy servers from their version number announcement, and automatically start to construct its MACs in the same incorrect manner as they do, so it will be able to work with them.
If you are using PuTTY version 0.51 or below, you can enable the workaround by going to the SSH panel and ticking the box labelled ‘Imitate SSH2 MAC bug’. It's possible that you might have to do this with 0.52 as well, if a buggy server exists that PuTTY doesn't know about.