> -----Original Message----- > From: . . [mailto:cmap_17@;yahoo.co.uk] > Subject: problem with vnc fake display
Nothing fake from vnc, just virtual ;-) > I'm trying to use vnc on a solaris 8 box with no display > capability. Reading a document on metalink (its so i can run > oracle stuff) made it seem like it was possible, and I > followed it to the letter but I get - General note on Solaris: default vnc on default solaris has problems with X11 locks in /tmp/... directories. Making this /tmp/... subdirectory world writable removes the problem. General note on Oralce: it is tricky on the colordept. something with needing pseudocolor or not working on pseudocolor, don't recal details here. > > # vncserver > You will require a password to access your desktops. > Password: > Verify: > # vncserver > New 'X' desktop is machine:1 > Creating default startup script /export/home/oracle/.vnc/xstartup > Starting applications specified in /export/home/oracle/.vnc/xstartup > Log file is /export/home/oracle/.vnc/saturn.machine.uk:1.log > # more /export/home/oracle/.vnc/saturn.machine.uk:1.log > 14/11/02 11:31:58 Xvnc version 3.3.3r2 > 14/11/02 11:31:58 Copyright (C) AT&T Laboratories Cambridge. > 14/11/02 11:31:58 All Rights Reserved. > 14/11/02 11:31:58 See http://www.uk.research.att.com/vnc for > information on VNC > 14/11/02 11:31:58 Desktop name 'X' (saturn.machine.uk:1) > 14/11/02 11:31:58 Protocol version supported 3.3 > 14/11/02 11:31:58 Listening for VNC connections on TCP port 5901 > 14/11/02 11:31:58 Listening for HTTP connections on TCP port 5801 > 14/11/02 11:31:58 URL http://saturn.machine.uk:5801 So far, so good. I expect you can now connect from remote to see the gray display with the X pointer with `vncviewer saturn.machine.uk:1`. > Xlib: connection to "unix:1.0" refused by server > Xlib: Client is not authoriAUDIT: Thu Nov 14 11:32:01 2002: > 815 Xvnc: client 1 > rejeXlib: connection to "AUDIT: Thu Nov 14 11:32:01 2002: 815 > Xvnc: client 1 > rejected from local host I think the security to the created Xdisplay ($DISPLAY == :1) is a little to high. Try stopping the current vncserver ( vncserver -kill :1 ) and restart it with the "-ac" option: `vncserver -ac`. This will create a vncserver without X11 security. You can set it with `xhost` at runtime. > AUDIT: Thu Nov 14 11:32:01 2002: 815 Xvnc: client 1 rejected > from local host fused by server > Xlib: Client is not authorized to connect to Server > twm: unable to open display ":1" > Xlib: connection to "unix:1.0" refused by server > Xlib: Client is not authorized to connect to Server > xterm Xt error: Can't open display: :1 > # xhost + > Xlib: connection to "saturn.machine.uk:1.0" refused by server > Xlib: Client is not authorized to connect to Server > xhost: unable to open display "saturn.machine.uk:1" Is the Xvnc process running at this point? Wild guess that it might have crashlanded. IF you have root access, retry it as root. If that succeeds, it is most likely the general solaris problem: no access for the X11 lock in the /tmp directory. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
