VNC Solaris 8 to Windows 2000

[Björn Persson]

Liu, Terence wrote:
> It seems NVC is listening.  But I am not sure about it. See below:

Yes, it is obviously listening. These three lines correspond to the ports 
XVNC uses, and they disappeared when you killed the VNC server:

>       *.6001               *.*                0      0 24576      0 LISTEN
>       *.5901               *.*                0      0 24576      0 LISTEN
>       *.5801               *.*                0      0 24576      0 LISTEN

The first line is the one we're interested in.

> Both "telnet localhost 6001" and "telnet 127.0.0.1 6001" failed.
>
> Both "telnet mickey 6001" and "telnet 169.144.80.61 6001" works.

So the loopback address doesn't work. That's odd. It doesn't seem like this 
could be causing your problem though, since the error messages indicate that 
the X clients use the name "mickey", which worked for Telnet:

> xrdb: No such file or directory
> xrdb: Can't open display 'mickey:1'
> xsetroot:  unable to open display 'mickey:1'
> Error: Can't open display: mickey:1
> twm:  unable to open display "mickey:1"

You could of course try to fix the loopback address anyway. I don't know how 
Solaris does it, but Linux has a virtual network card called the "loopback 
interface", or "lo" for short.

It could also be a problem with the X authority file so that the clients 
can't authorize themselves to the server, but in that case you should get 
error messages saying so. In Redhat, when I try to put a window on another 
user's XVNC server I get messages like these:

$ xterm -display :1
Xlib: connection to ":1.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
xterm Xt error: Can't open display: :1

Otherwise I don't know what could be wrong. I don't think the "No such file 
or directory" message from XRDB is that bad. It has never prevented me from 
using VNC. Maybe someone who knows more about X on Solaris can help?

Of course you could also try it the other way and solve the problem with the 
Unix socket so you can remove the "-nolisten local" parameter. It may be as 
simple as missing write permission in /tmp/.X11-unix or 
/usr/spool/sockets/X11.

Bjvrn Persson