1. Forum
  2. Usenet
  3. COMP.SECURITY.SSH

  • PSCP error: 'ssh_init: Network error: Cannot assign requested addre

    From erikebrownva@gmail.com@21:1/5 to All on Sun Jul 5 10:01:47 2020
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jcharlesepic@gmail.com@21:1/5 to All on Thu Jul 9 13:00:30 2020
    Thanks guys... Even though my PuTTY default session still shows port 22, I was having this problem and used the -P flag to get pscp to work.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From david.bowser@gmail.com@21:1/5 to Matt Miller on Sat Jul 11 15:23:12 2020
    On Sunday, November 8, 2015 at 8:13:26 PM UTC-5, Matt Miller wrote:
    Hello All,

    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.

    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. Could
    this be a configuration issue? How about something with my NIC card?

    Any thoughts are much appreciated!

    Thanks,

    M. Miller

    Just happened to me, so thanks for the explanation.

    Putty recently got a version bump to 0.74 on my system. Wondering if this is a bug/revision or an issue with the upgrade process.

    Just in case someone is chasing this down: Win10 1909. pscp/putty 0.74 installed/upgraded via Chocolatey

    Option "-P 22" got the script running again.

    And because it was likely a default setting issue, my subsequent run WITHOUT "-P 22" also worked as before.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From asifelahi999@gmail.com@21:1/5 to erikeb...@gmail.com on Sat Jul 11 19:51:48 2020
    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.

    EB

    Thanks. pscp -P 22 user@IP:file C:/User/location works perfectly.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ziwen Yuan@21:1/5 to asifel...@gmail.com on Thu Jul 16 18:45:45 2020
    On Saturday, July 11, 2020 at 10:51:49 PM UTC-4, asifel...@gmail.com wrote:
    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.

    EB
    Thanks. pscp -P 22 user@IP:file C:/User/location works perfectly.

    Thanks! Finally found answer here!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From vegas4@gmail.com@21:1/5 to Jacob Nevins on Fri Jul 24 16:06:14 2020
    On Wednesday, November 11, 2015 at 3:16:56 AM UTC-7, Jacob Nevins wrote:
    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.

    Thank you Matt for asking the question and Jacob for providing the solution.
    I just added "-P 22" in the command line and we are back in business. :)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From cloud4jam@gmail.com@21:1/5 to All on Fri Jul 31 03:23:12 2020
    Hey, thanks Jacob you saved my whole day.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mittu Chowdary@21:1/5 to All on Sun Aug 16 02:25:20 2020
    Thanks a lot to you both. It saved me!! "pcsp -P 22 ...." worked!!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From urooj mughal@21:1/5 to Mittu Chowdary on Fri Aug 21 07:06:08 2020
    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 .

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Hassan Mkhlalati@21:1/5 to matthew.al...@gmail.com on Wed Aug 26 11:14:02 2020
    On Monday, November 9, 2015 at 2:13:26 AM UTC+1, matthew.al...@gmail.com wrote:
    Hello All,

    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.

    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. Could
    this be a configuration issue? How about something with my NIC card?

    Any thoughts are much appreciated!

    Thanks,

    M. Miller
    Thank you, Very good but how to make it permanent

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nathan Lannine@21:1/5 to All on Thu Aug 27 11:53:15 2020
    Thank you, Very good but how to make it permanent

    I 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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Manfred Andres@21:1/5 to Nathan Lannine on Mon Sep 14 23:34:51 2020
    Nathan Lannine schrieb am Donnerstag, 27. August 2020 um 20:53:17 UTC+2:
    Thank you, Very good but how to make it permanent
    I 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.
    Thank you very much. This made it permanent for me.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From evindrenji007@gmail.com@21:1/5 to urooj mughal on Tue Sep 22 16:02:48 2020
    On Friday, August 21, 2020 at 7:36:10 PM UTC+5:30, urooj mughal wrote:
    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 .

    I'm still stuck on this.Could you share the solution to this problem?'

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Giovanni Uzzardi@21:1/5 to All on Thu Sep 24 09:24:51 2020
    Il giorno mercoledì 11 novembre 2015 alle 11:16:56 UTC+1 Jacob Nevins ha scritto:
    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'.
    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.
    Thank you!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lapi Pase@21:1/5 to All on Tue Feb 9 13:36:47 2021
    El jueves, 24 de septiembre de 2020 a las 11:24:53 UTC-5, Giovanni Uzzardi escribió:
    Il giorno mercoledì 11 novembre 2015 alle 11:16:56 UTC+1 Jacob Nevins ha scritto:
    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'.
    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.
    Thank you!
    Perfect for AWS with pscp -P 22 -I ec2-user . Thanks a LOT !!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anders Eliasson@21:1/5 to All on Wed Jun 9 01:27:33 2021
    torsdag 27 augusti 2020 kl. 20:53:17 UTC+2 skrev Nathan Lannine:
    Thank you, Very good but how to make it permanent
    I 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.
    Works for me too, "highlighting the "default settings" entry, and clicking "save" fixed it" No need to add -p after this. Thx :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)