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/

Chuck <skilover_nospam@bluebottle.com> writes:

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

Heh... must've missed my mention of cygwin. :-)

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

Afraid that doesn't work either - same problem.

Do I need to have putty running with a connection for this to work?

I have tried it with / without and it makes no difference. I am able
to connect using Putty directly

I tried your cygwin suggestion and that worked a treat - is there any
way to use that command from a dos prompt?

Thanks very much for pointing me in the direction of cygwin.

As this worked fine - I am perplexed as to why pscp doesn't want to
play the game......

sorry - just realised that it works fine 'as-is' from the command
prompt - thanks again

vladimir.mcbadger@gmail.com writes:

> I tried your cygwin suggestion and that worked a treat - is there any
> way to use that command from a dos prompt?

> Thanks very much for pointing me in the direction of cygwin.

Cool.

I'm not sure about the dos prompt. The cygwin command prompt is SO
much nicer though, I've never bothered to try figuring it out.

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

vladimir.mcbadger@gmail.com wrote:
> Afraid that doesn't work either - same problem.
>
> Do I need to have putty running with a connection for this to work?
>
> I have tried it with / without and it makes no difference. I am able
> to connect using Putty directly
>

Nope. What is the error you're getting?

Chuck wrote:
> vladimir.mcbadger@gmail.com wrote:
> > Afraid that doesn't work either - same problem.
> >
> > Do I need to have putty running with a connection for this to work?
> >
> > I have tried it with / without and it makes no difference. I am able
> > to connect using Putty directly
> >
>
> Nope. What is the error you're getting?

'Fatal: Network error: Connection timed out' - It may be ful to
know that scp from cygwin works absolutely fine so that probably rules
out any network issues.

vladimir.mcbadger@gmail.com writes:

> sorry - just realised that it works fine 'as-is' from the command
> prompt - thanks again

Vladimir, what did you mean by this?

[openssh cygwin scp | pscp ] works fine as-is from the [cygwin | windows ]
command prompt?

Circle two. :-)

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

vladimir.mcbadger@gmail.com writes:

> Chuck wrote:
> > vladimir.mcbadger@gmail.com wrote:
> > > Afraid that doesn't work either - same problem.
> > >
> > > Do I need to have putty running with a connection for this to work?
> > >
> > > I have tried it with / without and it makes no difference. I am able
> > > to connect using Putty directly
> > >
> >
> > Nope. What is the error you're getting?
>
> 'Fatal: Network error: Connection timed out' - It may be ful to
> know that scp from cygwin works absolutely fine so that probably rules
> out any network issues.

What's the output of pscp -V ?

And what's the command tat elicits the connection timed out error? I
imagine that pscp is trying to open a connection to port 22 vs the
port it needs to.


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

Sorry - pscp works fine from the windows command prompt


Todd H. wrote:
> vladimir.mcbadger@gmail.com writes:
>
> > sorry - just realised that it works fine 'as-is' from the command
> > prompt - thanks again
>
> Vladimir, what did you mean by this?
>
> [openssh cygwin scp | pscp ] works fine as-is from the [cygwin | windows ]
> command prompt?
>
> Circle two. :-)
>
> --
> Todd H.
> http://www.toddh.net/

In comp.security.ssh Todd H. <comp@toddh.net>:
> Chuck <skilover_nospam@bluebottle.com> writes:
>> Todd H. wrote:
>> > Simon Tatham <anakin@pobox.com> writes:
>> >> Todd H. <comp@toddh.net> wrote:

[ problems with pscp ]

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

Just install a real OS, you'll not only get openssh out of the
box but a bunch of great nntp reader in addition. ;-)

> Heh... must've missed my mention of cygwin. :-)


--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 445: Browser's is corrupted -- someone's
been nibbling on it.

Michael Heiming <michael+USENET@www.heiming.de> writes:

> Just install a real OS, you'll not only get openssh out of the
> box but a bunch of great nntp reader in addition. ;-)

I'll note I'm not posting from a windows box, but aren't we above this
sort of kneejerk "real OS" stuff here in comp.security.ssh?

I see the winky and all but still... I guess what's irritating about
the usual chorus of "use a real OS" comments is that they ignore
corporate users who don't necessarily have a choice of what OS is on
their company computer and have to get their work done anyway.

'Course that's where vmware player or vmware server can come in quite
handy (if the company in question trusts employees to install
things).

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

In comp.security.ssh Todd H. <comp@toddh.net>:
> Michael Heiming <michael+USENET@www.heiming.de> writes:

>> Just install a real OS, you'll not only get openssh out of the
>> box but a bunch of great nntp reader in addition. ;-)

> I'll note I'm not posting from a windows box, but aren't we above this
> sort of kneejerk "real OS" stuff here in comp.security.ssh?

> I see the winky and all but still... I guess what's irritating about
> the usual chorus of "use a real OS" comments is that they ignore
> corporate users who don't necessarily have a choice of what OS is on
> their company computer and have to get their work done anyway.

Really? Personally run *nix on all my desktop/laptop/etc, they
even pay me for doing it. ;-)

Good idea to ask during a job interview if there'd be a problem?

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 411: Traffic jam on the Information Superhighway.