ssh forwarding problem on WinNT for java client

David W. Lewis dwlewis "at" dnai.com
Thu, 13 Jul 2000 18:29:40 +0000


Hey, all.

Playing with VNC on Solaris/NT/2000 platforms - VERY cool tool, btw - and 
I'm running up against a problem using ssh forwarding from a Solaris box to 
an WinNT 4.0, SP 6A machine using SecureCRT as my NT ssh client.   VNC 
Viewer works fine with port forwarding but the java client doesn't

Below I'll describe symptoms:

 From my log on the Solaris box that I'm attempting to view:

13/07/00 09:18:49 Listening for VNC connections on TCP port 5902
13/07/00 09:18:49 Listening for HTTP connections on TCP port 5802
13/07/00 09:18:49   URL http://192.168.200.2:5802  (machine name changed to 
IP address by me)

Direct connects both via http and vnc viewer to the machine in question 
work fine.

In my ssh port forwarding I have the following:

local port	remote hostname	remote port
5810		192.168.200.2		5802
5910		192.168.200.2		5902

Vnc Viewer to localhost:10 brings up the forwarded port 5902 and i 
authenticate just fine.   However, when I attempt to access

	http://localhost:5810

the VNC Authentication screen pops up just fine but when I put in my 
password for authentication I get the error message

	java.net.ConnectException:  Connection refused

As mentioned, I don't get this error when connecting directly to

	http://192.168.200.2:5802

I authenticate fine and everything is hunky-dory.

Below is from my vnc log for this session:

13/07/00 10:04:58 Got connection from client 192.168.200.3
13/07/00 10:04:58 Protocol version 3.3
13/07/00 10:04:58 Using hextile encoding for client 192.168.200.3
13/07/00 10:04:58 Pixel format for client 192.168.200.3:
13/07/00 10:04:58   8 bpp, depth 8
13/07/00 10:04:58   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
13/07/00 10:04:58 no translation needed
13/07/00 10:05:05 Client 192.168.200.3 gone
13/07/00 10:05:05 Statistics:
13/07/00 10:05:05   key events received 0, pointer events 35
13/07/00 10:05:05   framebuffer updates 34, rectangles 83, bytes 15841
13/07/00 10:05:05     hextile rectangles 83, bytes 15841
13/07/00 10:05:05   raw bytes equivalent 795519, compression ratio 50.218989

The above is the correctly authenticated session to the local machine with 
the http://192.168.200.2:5802 connection call.

13/07/00 10:05:08 httpd: get '' for 192.168.200.2
13/07/00 10:05:08 httpd: defaulting to 'index.vnc'

Note that in the above the call is from  http://localhost:5810 which 
translates to http://192.168.200.2:5802 via my ssh rewrite.  Vncserver 
doesn't appear to be able to get the call properly.   Note again, that the 
port translation for the Vncviewer from localhost:5910 --> 
192.168.200.2:5902 works fine.

Anyone seen the above problem before?  Is there a workaround?

Thanks in advance.

-David Lewis
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------