Please send all replies to the list so that they will be in the archives for the next person having trouble.
Joseph Kexel said: > Thanks for the polite RTFM response, but this is not an issue of the > server being enabled for loopback. It's the client, vncviewer, having > problems. When the server refuses loopback connections it is reported by the client. > I am doing nothing like what is explained in the documentation. > In fact every registry entry is in place and I have quite a bit of > experience using ssh with VNC while implementing the standard 'client > connects to server' paradigm. This is nothing really different, just a different port. > This is the reverse of that; the server initializes the connection to a > listening vncviewer, through a ssh tunnel. The tunnel works since the > viewer responds with the loopback disabled dialog. I have seen references > in the lists that vncviewer does not look at the AllowLoopback key. Also, > the closest list message does not seem to have an answer. Again, the viewer doesn't look at the AllowLoopback key because the server is the only one that cares. Since you have experience with using SSH tunnels with VNC, you are aware that typing something like "localhost:1" into the vncviewer doesn't cause this error. > Even the Unix version of vncviewer does not seem to have an 'enable > loopback' command line switch. If, you need a better description, let me > know. Again, the viewer doesn't care. More information must be needed if adding "AllowLoopback" in the registry doesn't work. I've just made a test, without "AllowLoopback" in the server registry, the client reports "VNC connection failed: Local loop-back connections are disabled.". With the key it works. Server on a Win2k machine, client on a RH 7.3 machine, both RealVNC 3.3.7. WORKSFORME. -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
