Troubleshooting VNC server (specifically "-inetd" flavor)
Hello all,
Here's where I'm trying to get to: I want to be able to make a VNC connection to a Red Hat 9 box (call it Sammy) and have the GDM login screen displayed. I have successfully done this on a different Red Hat 9 box (call it Billy) by doing the following: 1. Added the following line to /etc/services: Code:
vnc 5901/tcp #VNC Code:
service vnc When I do the exact same thing on Sammy and try to connect with a VNC client, I get an "Invalid Protocol" error message. I read that "Invalid Protocol" simply means, "The server said something I didn't understand." Attempting to telnet to Sammy on port 5901 exposed the real problem: Code:
Fatal server error: Now, there are some differences between the two machines: Billy was a fresh install of Red Hat 9, while Sammy was upgraded from an earlier release (7.3 I think). Billy was set up to use GDM graphical login at install time, while Sammy was converted later by changing id:3:initdefault: in /etc/inittab to id:5:initdefault:. Both are running the same version of VNC (3.3.3r2-47). I have investigated the /etc/rc.d/init.d/vncserver script and /etc/sysconfig/vncservers, but my understanding is that these do not apply when Xvnc is started by xinetd. So... how does "Xvnc -inetd" learn which displays are unused? How can I best teach this slow learner? Thanks for your time. I'd be happy to post additional info if needed. |
shameless bump
|
OK, I feel pretty dumb. Reviewing Sammy's configuration I discovered a couple of formatting errors in the /etc/xinetd.d/vnc file which resulted in the server_args being messed up. Sure enough, if you just try to run Xvnc with no arguments, you get the same error I was seeing. Fixed the file, fixed the problem. Just wanted to let the thread know.
cheers |
All times are GMT -5. The time now is 04:18 PM. |