I have created a SSH tunnel to an external (i.e. hosted outside my home
network) and have succesfully remotely logged onto the server.

When I try to use the pscp command to copy a file to the server I get
the error "Fatal: Network Error: Connection timed out"

Can anyone advise on what may be going wrong / how to resolve it?

TIA

Todd H. wrote:
> vladimir.mcbadger@gmail.com writes:
>
> > I have created a SSH tunnel to an external (i.e. hosted outside my home
> > network) and have succesfully remotely logged onto the server.
> >
> > When I try to use the pscp command to copy a file to the server I get
> > the error "Fatal: Network Error: Connection timed out"
> >
> > Can anyone advise on what may be going wrong / how to resolve it?
>
> Does the ssh server run on a non-standard port?
>
> Can you copy the syntax you are attempting here?
>

Yes the ssh server does run on a non-standard port '6024'

The syntax is

pscp C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:/tmp

I have also tried

pscp C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:

The path on my c: is correct and the file is present and a new file so
should not have any problematic attributes.

vladimir.mcbadger@gmail.com writes:

> I have created a SSH tunnel to an external (i.e. hosted outside my home
> network) and have succesfully remotely logged onto the server.
>
> When I try to use the pscp command to copy a file to the server I get
> the error "Fatal: Network Error: Connection timed out"
>
> Can anyone advise on what may be going wrong / how to resolve it?

Does the ssh server run on a non-standard port?

Can you copy the syntax you are attempting here?



--
Todd H.
http://www.toddh.net/

vladimir.mcbadger@gmail.com writes:

> Todd H. wrote:
> > vladimir.mcbadger@gmail.com writes:
> >
> > > I have created a SSH tunnel to an external (i.e. hosted outside my home
> > > network) and have succesfully remotely logged onto the server.
> > >
> > > When I try to use the pscp command to copy a file to the server I get
> > > the error "Fatal: Network Error: Connection timed out"
> > >
> > > Can anyone advise on what may be going wrong / how to resolve it?
> >
> > Does the ssh server run on a non-standard port?
> >
> > Can you copy the syntax you are attempting here?
> >
>
> Yes the ssh server does run on a non-standard port '6024'
>
> The syntax is
>
> pscp C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:/tmp
>
> I have also tried
>
> pscp C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:
>
> The path on my c: is correct and the file is present and a new file so
> should not have any problematic attributes.

Unlike command line scp, pscp lacks a -P port parameter (at least hte
version I have handy), and hence has never bee my choice when dealing
with an ssh server running on anything but tcp/22.

So you have two options. If you prefer command line, you can use real
openssh if you get cygwin.com. It's free. Cygwin is great to have
for other reasons to as it implements a veyr nice unix environment in
windows. The ssh client is part of the openssh package. Once you get
to the package selection screen of the cygwin installer, scroll down
to the "net" section and then scroll down to openssh, and in the New
column, left click to change "skip" to be the version number of the
latest. Once installed, first up the cygwin shell, then your command
line simply becomes

scp -P 6024 /cygdrive/c/Temp/TestFile1.txt vlad789@www.mcbadger.co.uk:/tmp

Option 2, is to grab a copy of the nice GUI scp client Winscp.
http://sourceforge.net/projects/winscp/

and be sure to include port 6024 in the session options.

Best Regards,
--
Todd H.
http://www.toddh.net/

Todd H. <comp@toddh.net> wrote:
> Unlike command line scp, pscp lacks a -P port parameter (at least hte
> version I have handy),

What version is that? The -P option has been in PSCP since version
0.48, which was the first released version of PSCP at all!
--
Simon Tatham These are my opinions. There are many
<anakin@pobox.com> like them but these ones are mine.

vladimir.mcbadger@gmail.com wrote:
> Todd H. wrote:
>> vladimir.mcbadger@gmail.com writes:
>>
>>> I have created a SSH tunnel to an external (i.e. hosted outside my home
>>> network) and have succesfully remotely logged onto the server.
>>>
>>> When I try to use the pscp command to copy a file to the server I get
>>> the error "Fatal: Network Error: Connection timed out"
>>>
>>> Can anyone advise on what may be going wrong / how to resolve it?
>> Does the ssh server run on a non-standard port?
>>
>> Can you copy the syntax you are attempting here?
>>
>
> Yes the ssh server does run on a non-standard port '6024'
>
> The syntax is
>
> pscp C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:/tmp
>
> I have also tried
>
> pscp C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:
>
> The path on my c: is correct and the file is present and a new file so
> should not have any problematic attributes.
>

Try pscp -P 6024 C:\Temp\TestFile1.txt vlad789@www.mcbadger.co.uk:/tmp

Todd H. wrote:
> Simon Tatham <anakin@pobox.com> writes:
>
>> Todd H. <comp@toddh.net> wrote:
>>> Unlike command line scp, pscp lacks a -P port parameter (at least hte
>>> version I have handy),
>> What version is that? The -P option has been in PSCP since version
>> 0.48, which was the first released version of PSCP at all!
>
> Heh... that's the one! Typing long pscp commands in cmd.exe ws
> something I only had patience for once before jupming to cygwin. :-)
>
> Thanks for the info though!
>

Install the cygwin version of openssh. Then openssh equivalent command
won't be much different though.

Simon Tatham <anakin@pobox.com> writes:

> Todd H. <comp@toddh.net> wrote:
> > Unlike command line scp, pscp lacks a -P port parameter (at least hte
> > version I have handy),
>
> What version is that? The -P option has been in PSCP since version
> 0.48, which was the first released version of PSCP at all!

Heh... that's the one! Typing long pscp commands in cmd.exe ws
something I only had patience for once before jupming to cygwin. :-)

Thanks for the info though!

--
Todd H.
http://www.toddh.net/