On Wed, 2002-11-27 at 20:40, Damon McMahon wrote: > My configuration: Windows 2000 Professional SP3 with RealVNC 3.3.5 and > NetworkSimplity OpenSSH 3.4p1, both installed as services. > > VNC server runs successfully when viewed over a direct ethernet connection > [switch, same subnet, ports opened on firewall] using the VNCThing client on > MacOSX 10.1.5. > > SSH server runs successfully when a simply login connection is established > using: > > ssh <Win2Khost> > > from the MacOSX host. > > However, I cannot get port forwarding to work with sshd<->vncserver. I run: > > ssh -L 5901:<Win2Khost>:5900 <Win2Khost> > > on the MacOSX client, but when I then attempt to connect to localhost:1 > using VNC viewer (VNCThing) I get a message saying the connection was > refused because the password was incorrect [it's not]. >
Well, I'm not sure what problem you're having, but you can try: ssh -L 5901:localhost:5900 <win2k host>. It will probably give you the same results, but it will rule out any host naming issues. > By using tcpdump I have established that there is TCP traffic between > exchanged between <MacOSXhost>:random-port and <Win2Khost>:22 after I > attempt to connect to localhost:1 via VNC, so the port forwarding on the > client-side would seem to working? > Try turning debugging on for the encrypted tunnel, as follows: ssh -v -v -L 5901:localhost:5900 <win2k host> You'll see a whole lot of debugging info when you first sign in with SSH, and that can all be ignored. When you attempt to create a connection over the tunnel, however, you will be given quite a bit of additional debugging information pertinent to the tunnel. It can help in cases such as this. Hope this helps! _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
