Re: SSH & VNC discovery

Mike, not only did I read your notes, I printed them out to have handy while
configuring.

The one with the suggestion to use Cygwin on the client side (WINME) coupled
with Marks note provided the route to success.

I followed the other instructions to the letter. But with ssh32 -L
5901:winxp:5900 winxp (or "user @winxp" the ssh client was not connecting
properly. Neither did it give me an error stating it had not connected!
So, I though SSH client had connected to SSHD on the host and hence all the
questions about VNC.

Once I used Cygwin/bin/ssh.exe it worked immediately. That also confirmed
that the SSH client piece was the obstacle. I knew VNC was OK because I
have used it for a long time. I knew the shhd server was OK because of your
web site describing the install and testing procedure. And I "thought"
(look out for the smoke) that SSH client was OK since I did not have error
messages.

I am very sorry that you think I did not read any of this. On the contrary,
I had read your website, the VNC web site, installed Cygwin, SSH32 and VNC
before making any post here. After testing and retesting ad nauseum, I
decided to post here. I was frustrated because I was sure I was following
your instructions and I was equally sure that your instructions were good.
That was my "catch 22".

I am not exaggerating when I say that I tried to close 100 times yesterday.
About half of those *before* posting here.

I agree with Bret that it is quite remarkable that I was able to resolve
this within 14 hours. Quite frankly, I was expecting it would happen by
today or Monday. This was due (in main part) thanks to your efforts and
yes, patience. To continue to help when you think the requestor is ignoring
you is a true sign of a noble heart and I thank you for that.

As I said, I am a total newbie to SSH

Once again I thank you.
Carl.

----- Original Message -----
From: "Michael Erdely" <mike@erdelynet.com>
To: <ssh-l@erdelynet.com>
Sent: Saturday, December 28, 2002 12:46 PM
Subject: RE: SSH & VNC discovery

> Oh, I understand. And I feel that the patient dialog yesterday was me
> giving Carl a break.
>
> Regardless of whether he is using a different ssh client than I
> throught, he still didn't read the responses to his messages.
>
> It was just a suggestion to read the messages before asking the same
> question again (and again).
>
> -ME
>
> -----Original Message-----
> From: ssh-l-admin@erdelynet.com [mailto:ssh-l-admin@erdelynet.com] On
> Behalf Of Ben Voigt
> Sent: Saturday, December 28, 2002 12:03 PM
> To: ssh-l@erdelynet.com
> Subject: RE: SSH & VNC discovery
>
>
> Give Carl a break. I'm guessing that his chosen ssh client utility IS
> command-line, but is not compatible with the OpenSSH command-line
> parameters. Then he would use "-L xxxx:localhost:xxxx" as everyone
> rightly
> instructed but ssh32 would not understand. Woila, no ports forwarded,
> no
> VNC connection!
>
> Carl, if this is the case, please share the configuration setup for
> ssh32
> with the group so that we'll know how to deal with that client in the
> future. Is there a different command-line parameter? Or a
> configuration
> file?
>
>
> Ben Voigt
> University of Pennsylvania
> Electrical Engineering PhD Student voigt@seas.upenn.edu
> <mailto:voigt@seas.upenn.edu>
> BVoigt@kas.com <mailto:BVoigt@kas.com>
> Support a Constitutional Amendment to protect the Pledge of Allegiance
> and
> National Motto. Click here for more information.
> <http://www.wepledge.com/>
>
> -----Original Message-----
> From: ssh-l-admin@erdelynet.com [mailto:ssh-l-admin@erdelynet.com]On
> Behalf Of Michael Erdely
> Sent: Saturday, December 28, 2002 10:44 AM
> To: ssh-l@erdelynet.com
> Subject: RE: SSH & VNC discovery
>
>
> Carl,
>
> Not to be rude, but you were told this very clearly in the following
> messages:
> - http://erdelynet.com/archive/ssh-l/2002-12/msg00137.php
> - http://erdelynet.com/archive/ssh-l/2002-12/msg00129.php
> - http://erdelynet.com/archive/ssh-l/2002-12/msg00136.php
>
> Please take the time to read people's responses to you.
>
> -ME
>
> -----Original Message-----
> From: ssh-l-admin@erdelynet.com [mailto:ssh-l-admin@erdelynet.com] On
> Behalf Of Carl - WC4H Bellsouth
> Sent: Friday, December 27, 2002 7:00 PM
> To: ssh-l
> Subject: SSH & VNC discovery
>
>
> I found out that once the SSH connection is established with
> portfowarding, I can use VNC Viewer to tunnel through regardless of
> whether or not VNC Server is running on the client.
>
> Thanks again to all.
> Carl
>
> --
> List Information: http://tech.erdelynet.com/mailman/listinfo/ssh-l/
> List Archives: http://erdelynet.com/archive/ssh-l/
> To Unsubscribe: Go to http://tech.erdelynet.com/mailman/listinfo/ssh-l/
> and
> enter your email address at the bottom to "Edit Options". If you don't
> know
> your password, have it emailed to you. Then unsubscribe.
> ---
> {AVG => Incoming mail is certified Virus Free.}
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002
>
> --
> List Information: http://tech.erdelynet.com/mailman/listinfo/ssh-l/
> List Archives: http://erdelynet.com/archive/ssh-l/
> To Unsubscribe: Go to http://tech.erdelynet.com/mailman/listinfo/ssh-l/
> and enter your email address at the bottom to "Edit Options". If you
> don't know your password, have it emailed to you. Then unsubscribe.
>
>
> --
> List Information: http://tech.erdelynet.com/mailman/listinfo/ssh-l/
> List Archives: http://erdelynet.com/archive/ssh-l/
> To Unsubscribe: Go to http://tech.erdelynet.com/mailman/listinfo/ssh-l/
and enter your email address at the bottom to "Edit Options". If you don't
know your password, have it emailed to you. Then unsubscribe.
>

--
List Information: http://tech.erdelynet.com/mailman/listinfo/ssh-l/
List Archives:    http://erdelynet.com/archive/ssh-l/
To Unsubscribe: Go to http://tech.erdelynet.com/mailman/listinfo/ssh-l/ and enter your email address at the bottom to "Edit Options". If you don't know your password, have it emailed to you. Then unsubscribe.