RE: Connecting to RHES returns: Failed to connect to server

[John A. <JAl...@co...>]

Bret Goodfellow wrote on Wednesday, March 29, 2006 5:32 PM:

> Hi John,
> 
> Thanks for responding.  I am attempting to connect to my
> RHES via the agent, and not http.  Do I still need a port
> open? Should I still care about 5800, 5801, 5900, 5901
> even if I am not using http? Also, I am accessing this
> server from the same network, and not the 
> internet.  One
> thing that I did notice on the RHES was the vnc.log.  The
> following messages were in the log: 
> 
> Xvnc versoin 4.0 - built Nov 24 2004 16:52:36
> Underlying X server release 60801000, The X.Org Foundatoin
> 
> Wed Mar 29 22:00:05 2006
>  vncext:	VNC extension running!
>  vncext:	Listening for VNC connections on port 5901
>  vncext:	Listening for HTTP connectoins on port 5801
>  vncext: 	created VNC server for screen 0
> Error opening secruity policy file
> /usr/X11R6/lib/X11/xserver/SecurityPolicy
> Could not init font path element
> /usr/X11R6/lib/X11/fonts/TTF/, removing
> from list!
> Could not init font path element
> /usr/X11R6/lib/X11/fonts/CID/, removing
> from list!
> 
> Any ideas John?  I'm going to google these messages and
> see 
> if I come up
> with something.
> 
Yep. I'd be willing to be it's the "SELinux" crap... the "security" stuff
that was added back around the time they spun off the "free" version to the
Fedora project. Also, make sure that you've got a hole in the firewall for
590x. And no, you don't need 580x if you're not going to access it via HTTP.
:-)

One other thing... I don't know about RHEL, but Fedora ships with RealVNC
instead of TightVNC now, so for maximum compatability, you may want to
switch to the RealVNC client on whatever machine you're trying to access the
RHEL server from.
	John