VNC & ssh tunneling problem: getsockopt TCP_NODELAY error

[Jan Grant]

On Fri, 5 Sep 2003, Scott I. Remick wrote:

> On Fri, 5 Sep 2003 11:58:16 +0100 (BST), Jan Grant wrote:
>
> > Loks like the VNC srever isn't listening at that location. Is it
> > running?
>
> Yep:
>
> -bash-2.05b$ ps
>   PID  TT  STAT      TIME COMMAND
> 60273  p0- S      0:00.49 Xvnc :1 -desktop X -httpd
> /usr/local/share/vnc/classes
> 60277  p0- S      0:00.20 /usr/X11R6/bin/blackbox
> 61709  p0  Is     0:00.03 bash
> 80005  p1  Is     0:00.02 bash
> 96020  p2  Ss     0:00.01 -bash (bash)
> 96025  p2  R+     0:00.00 ps
>   490  v0  I      0:00.01 -bash (bash)
> 61622  v0  I+     0:00.01 /bin/sh /usr/X11R6/bin/startx
> 61634  v0  I+     0:00.01 xinit /home/scott/.xinitrc -- -nolisten tcp
> 61640  v0  I      0:00.00 sh /home/scott/.xinitrc
> 61641  v0  I      0:01.31 /usr/X11R6/bin/gnome-session
> 61644  v0  S      0:01.62 /usr/X11R6/libexec/gconfd-2 13
>
> Blackbox is the wm being started from ~/.vnc/xstartup since I normally use
> gnome. And I'm forwarding the ports in PuTTY:
>
> 2003-09-05 09:02:56	Local port 7001 forwarding to localhost:5901
> 2003-09-05 09:02:56	Local port 7002 forwarding to localhost:5902
> 2003-09-05 09:02:56	Local port 7003 forwarding to localhost:5903
>
> (the same port-forwarding that worked for me before).
>
> On the Windows system, I then VNC to localhost:7001 which triggers that
> error on the VNC box.

I'd still recommend double-checking with sockstat on the BSD box, (and
netstat -an on the windows box, but I don't think that's the problem).

-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/
Random act of violence against bread: whole pint.
  -- extract from the "Hawk the Slayer" drinking game