On Thu, 12 Feb 2004 13:33:04 -0600, Glenn Lovitz wrote:
   > Interesting problem.  I have done this in similar situations
   > successfully via
   > PuTTY but my tunnel looks a little different than yours.  Are you
   > running
   > vncserver on both BOX_1 and BOX_2?  If so, both on port 5900?  If
   > so, I
   > suspect all the networks involved use 192.168.0 (or the same
   > private) address
   > space (certainly the case on LinkSys to LinkSys)which will cause a
   > fundamental
   > problem locally on BOX_2.  It will intercept the return packet on
   > it's own
   > port 5900 thinking it is incoming from your internal network to it
   > rather than
   > being sent back out through the tunnel.

   TCP can't be confused in this fashion; it does not make the connection
   from  5900 to 5900, but instead makes it from (temp port) to 5900. All
   packets  would  be  sent  back to (temp port) on the viewer machine or
   tunnel-machine.  Even  if  somehow  this  were  happening, I would get
   "failed  connection" messages, as NO packets would successfully return
   --  instead  I get a login prompt and successful-connection reports in
   my logfiles. You can look at NETSTAT /AN and see what I mean.

   However,  in  this instance (as mentioned in the other message) the IP
   address  ranges  aren't  even  identical; 192.168.1.* at home, 10.* at
   work, so the identical-IP stuff doesn't even apply here.

   Also, just for giggles, I installed a server on BOX_2 and attempted to
   vNC  to  it; same problem. (changing the forward from 5900: BOX_1:5900
   to 5900: localhost:5900 and 5900: BOX_2:5900, of course).

   > Even if that is not your situation exactly, try a tunnel that looks
   > like:
   >
   > L5910 <BOX_1 ip address>:5900 <external ip address>

   I  haven't  used the IP addresses yet. I suppose I should try that and
   see  what  happens,  although for DNS or reverse-DNS to be the problem
   here would be very weird.

   (I  have changed the local ports, remember: tried it on 9876 and 5631,
   specifically.)

   -- Derek
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to