Hello All,requested address'. Putty works fine, WinSCP also works fine.
I am using PSCP to transfer a file from a Linux server to a local directory on my Windows 7 machine. When I attempt to transfer the file using PSCP from the Windows command line, I immediately receive the error: 'ssh_init: Network error: Cannot assign
PSCP was working fine up to a few days ago, then suddenly stopped working. I have verified that I can perform a file transfer with a different Windows box using PSCP, so it definitely seems to be something about the PC itself that has changed. Couldthis be a configuration issue? How about something with my NIC card?
Any thoughts are much appreciated!
Thanks,
M. Miller
Saved my butt too, thanks guys. I got around this by adding the -P flag to specify port 22 directly. Then it worked fine.
EB
On Sunday, July 5, 2020 at 10:31:48 PM UTC+5:30, erikeb...@gmail.com wrote:
Saved my butt too, thanks guys. I got around this by adding the -P flag to specify port 22 directly. Then it worked fine.
EBThanks. pscp -P 22 user@IP:file C:/User/location works perfectly.
Matt Miller <matthew.almar.miller@gmail.com> writes:
I am using PSCP to transfer a file from a Linux server to a local
directory on my Windows 7 machine. When I attempt to transfer the file >using PSCP from the Windows command line, I immediately receive the
error: 'ssh_init: Network error: Cannot assign requested address'.
Putty works fine, WinSCP also works fine.
A favourite way to provoke this message is to try to connect to port 0.
Guess: is it possible that you've accidentally saved port 0 to PuTTY's Default Settings? The different PuTTY tools have different implicit
session loading behaviour, which might explain why PuTTY works but PSCP doesn't.
Thanks a lot to you both. It saved me!! "pcsp -P 22 ...." worked!!Hey, i am using pscp command for copy file from window to server. i have also issue but when i am using -P 22 port than also faced error: FATAL ERROR: Network error: connection refused .
Hello All,requested address'. Putty works fine, WinSCP also works fine.
I am using PSCP to transfer a file from a Linux server to a local directory on my Windows 7 machine. When I attempt to transfer the file using PSCP from the Windows command line, I immediately receive the error: 'ssh_init: Network error: Cannot assign
PSCP was working fine up to a few days ago, then suddenly stopped working. I have verified that I can perform a file transfer with a different Windows box using PSCP, so it definitely seems to be something about the PC itself that has changed. Couldthis be a configuration issue? How about something with my NIC card?
Any thoughts are much appreciated!Thank you, Very good but how to make it permanent
Thanks,
M. Miller
Thank you, Very good but how to make it permanent
Thank you very much. This made it permanent for me.Thank you, Very good but how to make it permanentI found just opening the putty settings window, highlighting the "default settings" entry, and clicking "save" fixed it for me. 22 was already in the port field for SSH.
On Sunday, August 16, 2020 at 2:25:21 AM UTC-7, Mittu Chowdary wrote:
Thanks a lot to you both. It saved me!! "pcsp -P 22 ...." worked!!Hey, i am using pscp command for copy file from window to server. i have also issue but when i am using -P 22 port than also faced error: FATAL ERROR: Network error: connection refused .
Matt Miller <matthew.al...@gmail.com> writes:Thank you!
I am using PSCP to transfer a file from a Linux server to a local >directory on my Windows 7 machine. When I attempt to transfer the file >using PSCP from the Windows command line, I immediately receive theA favourite way to provoke this message is to try to connect to port 0.
error: 'ssh_init: Network error: Cannot assign requested address'.
Putty works fine, WinSCP also works fine.
Guess: is it possible that you've accidentally saved port 0 to PuTTY's Default Settings? The different PuTTY tools have different implicit
session loading behaviour, which might explain why PuTTY works but PSCP doesn't.
Il giorno mercoledì 11 novembre 2015 alle 11:16:56 UTC+1 Jacob Nevins ha scritto:Perfect for AWS with pscp -P 22 -I ec2-user . Thanks a LOT !!
Matt Miller <matthew.al...@gmail.com> writes:
I am using PSCP to transfer a file from a Linux server to a local >directory on my Windows 7 machine. When I attempt to transfer the file >using PSCP from the Windows command line, I immediately receive the >error: 'ssh_init: Network error: Cannot assign requested address'.A favourite way to provoke this message is to try to connect to port 0.
Putty works fine, WinSCP also works fine.
Guess: is it possible that you've accidentally saved port 0 to PuTTY's Default Settings? The different PuTTY tools have different implicit session loading behaviour, which might explain why PuTTY works but PSCP doesn't.Thank you!
Works for me too, "highlighting the "default settings" entry, and clicking "save" fixed it" No need to add -p after this. Thx :-)Thank you, Very good but how to make it permanentI found just opening the putty settings window, highlighting the "default settings" entry, and clicking "save" fixed it for me. 22 was already in the port field for SSH.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 11:48:10 |
| Calls: | 6,645 |
| Calls today: | 5 |
| Files: | 12,190 |
| Messages: | 5,326,712 |