This sounds like a default vs current user registry issue. So the fix is to set the default settings and get rid of the current user settings for vnc.
With the service running. Open regedit and delete hkey_current_user/software/orl/winvnc3 Then run winvnc -defaultsettings from the command line or run with full path(notice the title in the title bar). After applying the default settings restart either vnc service or the machine, and all should now be fine. V4 fixes this issue of confusing configuration nicely. Steve Palocz -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott D. Davis Sent: Thursday, September 04, 2003 9:04 AM To: [EMAIL PROTECTED]; VNC list Subject: Re: VNC / SSH / PUTTY Okay news first, then answer to your last email: *** NEWS: Before I left for work this AM, I setup a vncserver on my HOME workstation (win2k) listening on (auto) port:0. When I got to work I tried the exact same (setupsare same) as from home. o ssh with tunneling to 5900:192.168.0.2:5900 o open VNCViewer localhost:0 BAM! Worked. I could not believe it. Same setup, yes SAME. The ONLY difference is that I have not recently downlaoded VNC and installed on the home PC. However, it IS the same version. I will fix that when I get home. However, that is not the end of this strange story. I was crusing along, ssh vnc'ing, and testing well. I finally decided to go get something else done at work, and I was looking for a way to "lock" (win2k client) the workstation manually. I tried: o "send ctrl-alt-del" but it did not respond o "request refresh" then c-a-d, same, no response o hrm... o Then I set, VNCServer (on home host) to "When last client disconnets: lock workstation" o I closed VNC session (viewer) o kept ssh sessin alive o re-opened the VNCViewer to go back home, to see if host (server) locked workstation. o BAM! Same error as from home. *** Coincidenece? I think not. What do the setups have in commen now with the error setup? Good question: Both were "workstation locked" or "workstation login" Wow!? HAve aI found a bug or what? To prove my theory I will go home tonight, and FORCE my WORK HOST to stay un-locked and logged-in, mirroring the successful setup I had from work this AM. *** If it works as it did this AM from work, then WE will have found the problem. ssh-vnc, for my setup, does not like, and will error out, if the host (server) is (win2k) locked, or waiting for login. === Yikes! Jepers. Now for your reply. o tunneling is working obviously from my success. o forwarding is reported in putty event log on successful login (ssh) *** So what do you think? Thanks for all, Scott ----- Original Message ----- From: "Jerry Westrick" <[EMAIL PROTECTED]> To: "Scott D. Davis" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, September 04, 2003 8:21 AM Subject: Re: VNC / SSH / PUTTY > okay the tunnel looks good, > and I assume you are doing ssh to w.x.y.z... > > Okay, next step, check that the tunnel setup is > working: > > after starting putty and connecting; > do "telnet 127.0.0.1 5903" in a dos box on win2k. > > if you get the "RFB ..." line then the tunnel is > working. > > If you don't then you still got a problem. > either with the tunnel setup, or on the remote box. > > > to check the tunnel right mouse click the putty title-bar, > select "event log", and scroll down window a look > for "opening forwarded connection" to see if the tunnel > is working as expected.... > > > To check the remote system, in the ssh terminal > try telnet 192.168.0.3 5903 and see if you get the > "RFB..." line... > > This will tell you where to look for the problem... > > Jerry > > P.S. Are you sure the win2k (at work) has a server > running on PORT 3? > > > > > On Thu, 2003-09-04 at 14:01, Scott D. Davis wrote: > > Thanks for the reply. > > > > The INTERNAL address 192.168.0.3 is the win2k CLIENT BEHIND my FIREWALL that > > is running the VNC SERVER. > > > > It goes like this: > > > > [HOME:] > > VNC_viewer ==> > > (win2k)192.168.0.2 --> (linux RH9)a.b.c.d > > ====internet====> > > [WORK:] > > (linux RH9)w.x.y.z --> (win2k)192.168.0.3 > > ==> VNC_Server > > > > SO: I ssh to my WORK linux and request a FOWARD (-L 5903:192.168.0.3:5903) > > to the win2k client running the VNC server. > > > > Make better sense? So then I "VNCViewer localhost:3" on the home client to > > use the ssh tunnel. Am I doing it right? > > > > Need more information? > > > > Thanks, > > Scott > > > > > > > > > > > > ----- Original Message ----- > > From: "Jerry Westrick" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, September 04, 2003 3:08 AM > > Subject: Re: VNC / SSH / PUTTY > > > > > > > Hello Mr. Davis... > > > > > > the address 192.168.0.3 is an internal address, not allowed accross the > > > internet. This address where you placed it is very suspect... > > > She if the router/firewall does not have an external address... > > > > > > > > > Then go through the "telnet xxx.yyy.zzz.aaa 5903" to see if you can > > > connect to your server... (You should get something like RFB X.Y) > > > > > > Jerry > > > > > > > > > On Thu, 2003-09-04 at 06:04, Scott D. Davis wrote: > > > > Hello: > > > > > > > > New user here on this list, glad to have it. > > > > > > > > I have read all the posts, searched both google, and arcive. > > > > > > > > I am using win2k client to goto VNC to work. I have recently upgradeed > > to > > > > RH9 from RH6. I USED to use telnet and portforwarding in a VERY > > unsecure > > > > way. Since the upgrade I ahve leared al I wanted and more about SSH. > > > > > > > > *** So here is the problem: > > > > I get an error EVERY time I run VNC after tunneling with ssh. I either > > get > > > > a C++ error notification, or a total session drop on VNC. > > > > > > > > I am using the latest VNC, and PUTTY. > > > > o Client is win2k SP4 > > > > o Remote is RH9 > > > > o Remote target is another win2k running VNC server > > > > > > > > I have tried: > > > > o using PUTTY tunneling via GUI (L5903 192.168.0.3:5903) > > > > o using PUTTY CL (PLink -SSH -C -L 5903:192.168.0.3:5903 linux.remote) > > > > o using VNC: localhost:3 > > > > o using VNC: 127.0.0.1:3 > > > > > > > > ERROR is either: > > > > o C++ error notification (when using PUTTY GUI) > > > > (or) > > > > o VNC viewer drops, ie, disappears, with no visable result (when using > > > > PLink) > > > > > > > > HELP!!! I am SO CLOSE. I can smell it, but something is wrong. I am > > using > > > > secure firewall rules with NAT rules for LAN internet access. > > > > > > > > Can anyone help?!!! I have done al the searching and testing I care > > for. > > > > Well, at least until I get back to work tomarrow. > > > > > > > > Thanks, > > > > Scott > > > > mailto:[EMAIL PROTECTED] > > > > _______________________________________________ > > > > VNC-List mailing list > > > > [EMAIL PROTECTED] > > > > To remove yourself from the list visit: > > > > http://www.realvnc.com/mailman/listinfo/vnc-list > > > _______________________________________________ > > > VNC-List mailing list > > > [EMAIL PROTECTED] > > > To remove yourself from the list visit: > > > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
