On Fri, 3 May 2002 16:15:47 +0800 "David" <[EMAIL PROTECTED]> quietly intimated:
> Hi ABrady, > > > Are ports 5901 (for running vncviewer on the client) and/or 5801 > > (for connecting with a browser) opened in the firewall? If the > > correct one isn't, vnc can't allow connections. Is the password > > being passed properly (case, spelling, etc)? If not, vnc won't allow > > the connection. > > > > You say you ssh into the machine and start the server. Are you then > > trying to run vncviewer from there (the machine you logged into) or > > from the one you're sitting in front of? > > Thanks for your reply. I don't have a firewall configured for either > of my machines. (don't need one at the moment) What happen is that I > am using a laptop and a PC. The PC has sshd running on it. I use my > laptop to control my PC through a network connection (internal > network). So, I ssh into my PC from my laptop, tried to start the > vncserver by typing "vncserver", before I run vncviewer on my laptop > to 'see' the PC. The problem now is that there is some authorized > thingy in the vncserver logs on the PC after I run the"vncserver" > command through ssh. The vncserver is unable to start properly.(or > rather KDE is unable to start properly due to: > > AUDIT: Fri May 3 02:00:24 2002: 817 Xvnc: client 1 rejected from > local host Xlib: connection to ":1.0" refused by server > Xlib: Client is not authorized to connect to Server > xsetroot: unable to open display ':1' > > and many others similar lines with the final lines: > > ksmserver: cannot connect to X server :1 > kdeinit: Fatal IO error: client killed > kdeinit: sending SIGHUP to children. > kdeinit: sending SIGTERM to children. > kdeinit: Exit. > > So, I would more correctly say that Xvnc started ok, but due to some > authorization thingy, KDE is unable to connect to Xvnc (since KDE is > the client here right?). So, how can I go about solving this problem? > > I tried to start vncserver from the console of my PC and it works > wonderfully. But I don't want to do that. I want to do the above. > > Thanks, > David I really don't know the answer to that. I've never tried starting the vnc sessions through ssh, and I'd say that's where the problem comes from at first glance. I only use it casually and I always keep a session opened on a guest account (can su from there) for the rare instances I need it. Since it's started at boot, I don't run into this problem. I was on the vnc mailing last a few years ago and recall getting all sorts of great advice there. Possibly that's the best place to seek info. -- The best things in life are free, but the expensive ones are still worth a look. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
