[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Unable to connect to VNC Server (Fedora Core 4) from Win2000 client - Used to work fine



Aamir,

It was my gdm.conf file that was causing the problem. I didn't even try your services or vnc1024 file. I mean, I compared these two files to my own counterpart files and determined that the configuration you chose was almost identical to mine so I backed up my existing gdm.conf file and then copied yours to my /etc/X11/gdm directory and then rebooted my machine. I was then able to VNC to the ports I used to use before my VNC/GDM login stopped working after the FC4 upgrade... I analyzed my old gdm.conf file to yours and noticed where I had a few awkward parameter settings... these 'abnormal' config settings I had were the reason my vnc/gdm setup wasn't working. Thanks for letting me use your files to compare to mine. If you hadn't let me use them, I'd still be irritated and 'so sure!' my configuration couldn't be at the heart of why things hadn't been working...

What I think it is though... I had previously been using the Gnome graphical configuration tool and I think that it had been putting these awkward parameters into the file... I had a problem just a couple of weeks ago where I had been trying to use the Gnome "Network" tool to configure my server's NIC for multiple ip addresses when a guy had recommended that I just configure this by using config files in /etc/sysconfig/network-scripts instead of the 'Network' tool which apparently was not editing the configuration files properly... stuff like this are probably the most significant kinds of bugs the community spends time fixing for average users and I guess the point of all this is...

Graphical configuration tools are bad and you can save alot of time by setting configurations more manually instead of assuming that the graphical tool is properly appending the configurations and running the proper scripts to initialize configuration.... Maybe I'm slowly but surely becoming less of a 'newbie'...

Ferindo

Aamir Malik wrote:

Ferindo,
I have tar'ed the requested files and attached them. Tell me if you get them.

aamir malik

On 7/22/05, Ferindo Middleton Jr <fmiddleton verizon net> wrote:


Would you mind sending me your configuration files?:
- */etc/X11/gdm/gdm.conf
- **/etc/services*
- the service files for the vnc located in */etc/xinetd.d/*

I want to copy them to my system and test and see if my system will work
with your exact config.

Ferindo

Aamir Malik wrote:



Well sorry to hear that - I would like to know the solution if you hit upon it.

thanks
aamir malik


On 7/21/05, Ferindo Middleton Jr <fmiddleton verizon net> wrote:




Well that's upsetting.. I thought it was some kind of FC4 issue... I
have named (the firewall/router program service turned off too but my
problem still exists... why why why....  vncserver works if I setup a
static login in the /etc/sysconfig/vncserver file but it doesn't work in
as an xinetd service as I set mine up just like in the forum you
referred me to. Maybe some day I'll figure it out.... like I said...
it's worked in FC3, and then I upgraded and suddenly it fails... this sucks.

Ferindo

Aamir Malik wrote:





I am using FC4. The fix for me was that the default iptables (i think
thats the firewall settings) were preventing incoming VNC connections.
To overcome this in gnome i went to
Desktop>System Settings>Server Settings>Services
There I stopped iptables - and immediately I was able to connect!

aamir malik


On 7/20/05, Ferindo Middleton Jr <fmiddleton verizon net> wrote:






Aamir,

What version of Fedora are you running... This address below is exactly
the same thing I did to get mine working back with FC3... but when I
updted to FC4... it stopped working. So, I'm still wondering if this is
an issue with FC4 regression with VNC support.

Ferindo

Aamir Malik wrote:







Fernindo!
I got my vnc & gdm working! I used the following notes:
http://forums.teamphoenixrising.net/showthread.php?t=32325

Then since i had X working from my PC (using cygwin's X11 support) i
when ahead and launched vncviewer on my Linux box. Then I went into
services and turned off iptables (firewall) via gui (that was the only
way I knew).

After this I was able to vnc from my PC to the Linux box!

hope this helps!

aamir malik

On 7/14/05, Aamir Malik <aamirm gmail com> wrote:








Ferindo:
Thanks for your detailed response. I tired your trick - I can't even
get your trick to work on my machine. Something else seems to be
messed up too for me. Some feature i am not aware of is throwing me
off. Will keep you posted if I get anywhere close to the gnome login
screen!

thanks for your reply, i really appreciate it.
aamir malik


On 7/13/05, Ferindo Middleton Jr <fmiddleton verizon net> wrote:








I've given up really... I have instead opted to run VNC the easier way
(with the Gnome login screen for authentication) and now I just use a
static kind of setup for it. I edited /etc/sysconfig/vncservers and
appended the following:

VNCSERVERS="2:s068913 3:s068913"
VNCSERVERARGS[2]="-geometry 750x530"
VNCSERVERARGS[3]="-geometry 980x700"

And then restarted Xvnc ....

This configuration works and I can vnc into the server using the either
of the the servers above. It isn't what I had before and wanted (the
dynamic login screen like sitting at the machine) but it works... I'd
like the setup I had before where I could use the Gnome login screen for
authentication just like as if I was sitting at the local machine and
initially logging in... if you figure out what the problem is with using
GDM for authentication, let me know... I submitted this as a bug (bug #
162002 at bugzilla.redhat.com) but the technician assigned to the the
vnc component insisted it was 'not a bug' and insisted that I use the
'easier to configure' method I give above for doing VNC... I don't like
the method above. I'd like for anybody VNCing into my server to have to
choose the login and password dynamically instead of it being tied to a
static default... but hey, sometimes you've got to just be happy with
what you've got.

Ferindo

Aamir Malik wrote:









Ferindo,
Did you reach a conclusion to this problem? I have the exact same
problem - and I fall into the same trap!

thanks
aamir malik



Unable to connect to VNC Server (Fedora Core 4) from  Win2000 client -
Used to work fine         James Weatherall           jnw "at"
realvnc.com
Tue Jun 28 10:56:01 2005
Previous message: Unable to connect to VNC Server (Fedora Core 4)








from Win2000 client - Used to work fine








Next message: VNCThing - Mac OS 9, Redux
Messages sorted by:                [ date ]               [ thread ]
        [ subject ]               [ author ]
________________________________
Ferindo,

I'd recommend looking into why no logfile is being generated before trying
to debug the connection issue.  vncserver will always cause Xvnc and the
other processes it spawns to write to a logfile in your .vnc directory.

The SecurityPolicy and font path messages won't affect the VNC side of
things.

Regards,

Wez @ RealVNC Ltd.












-----Original Message-----
From: vnc-list-admin "at" realvnc.com
[mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Ferindo Middleton Jr
Sent: 27 June 2005 23:20
To: James Weatherall
Cc: vnc-list "at" realvnc.com
Subject: Re: Unable to connect to VNC Server (Fedora Core 4)








from Win2000 client - Used to work fine








I use the VNC Server & client that came packaged with Fedora
when I'm on
the server but I use version 4.1.1 on my Windows 2000 machine running
remotely on my LAN... both them act the same way way
connecting to the
server. Locally in the .vnc folder of the user on the server,
the most
recent logfile seems to be a couple of days ago (strange
thing is I ran
it again just now but no logfile generated). Anyhow, the file
contains
this, tell me what you think, thanks:

Free Edition 4.1.1 - built Apr 27 2005 02:35:07
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 60802000, The X.Org Foundation

Sat Jun 25 22:51:10 2005
vncext:      VNC extension running!
vncext:      Listening for VNC connections on port 5902
vncext:      Listening for HTTP connections on port 5802
vncext:      created VNC server for screen 0
error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy
Could not init font path element
/usr/X11R6/lib/X11/fonts/CID/, removing








from list!








vnc Free Edition 4.1.1 - built Apr 27 2005 02:35:07
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 60802000, The X.Org Foundation

Sat Jun 25 22:51:10 2005
vncext:      VNC extension running!
1 - built Apr 27 2005 02:35:07
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 60802000, The X.Org Foundation

Sat Jun 25 22:51:10 2005
vncext:      VNC extension running!
vncext:      Listening for VNC connections on port 5902
vncext:      Listening for HTTP connections on port 5802
vncext:      created VNC server for screen 0
error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy
Could not init font path element
/usr/X11R6/lib/X11/fonts/CID/, removing








from list!








vnc Free Edition 4.1.1 - built Apr 27 2005 02:35:07
--------------------------------------------------------------
------------------------------
(192.168.1.2 is the address of the server's NIC on my LAN)
When I run vncviewer 192.168.1.2  on the shell, I get the
following output:

VNC viewer for X version 4.0b4 - built Apr 14 2004 12:25:22
Copyright (C) 2002-2003 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Mon Jun 27 17:59:10 2005
CConn:       connected to host 192.168.1.2 port 5901
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.7
TXImage:     Using default colormap and visual, TrueColor, depth 16.
CConn:       Using pixel format depth 6 (8bpp) rgb222
CConn:       Using ZRLE encoding

Mon Jun 27 17:59:11 2005
main:        End of stream
[s068913 "at" localhost .vnc]$ vncviewer 192.168.1.2 |
$HOME/text_from_vnc_viewer
bash: /home/s068913/text_from_vnc_viewer: No such file or directory

VNC viewer for X version 4.0b4 - built Apr 14 2004 12:25:22
Copyright (C) 2002-2003 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Mon Jun 27 18:00:11 2005
CConn:       connected to host 192.168.1.2 port 5900
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.7
TXImage:     Using default colormap and visual, TrueColor, depth 16.
CConn:       Using pixel format depth 6 (8bpp) rgb222
CConn:       Using ZRLE encoding

Mon Jun 27 18:00:12 2005
main:        End of stream



James Weatherall wrote:











Ferindo,

The fact that the viewer is showing the desktop window but










is then closing










suggests that you are able to connect to the server, but










that the server is










then closing the connection again, so you may want to look










at the server's










log (in your .vnc directory) to see why it is doing so.

Are you using the standard VNC server for GNU/Linux, or the










one bundled with










Fedora?

Regards,

Wez @ RealVNC Ltd.














-----Original Message-----
From: vnc-list-admin "at" realvnc.com
[mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Ferindo










Middleton Jr










Sent: 26 June 2005 15:01
To: vnc-list "at" realvnc.com
Subject: Unable to connect to VNC Server (Fedora Core 4) from
Win2000 client - Used to work fine

1. I'm sure the VNC Server is running and excepting connections
2. the Windows VNC client and  Linux  Fedora Core 4 Server
running VNC
Server are on the same LAN
3. nothing is being prohibited in my server's host.deny file
4. When I try to connect to Server from VNC client the










client window










opens for a couple brief seconds with a blue screen and then closes
5. It does the same thing even when I use a VNC client
running locally
on the server
6. VNC connections used to work fine before I recently
upgraded from FC3
to Fedora Core 4
7. I've tried opening up my system more by turning off iptables and
SELinux but that doesn't seem to be the reason

I've looked through troubleshooting guides available from










realvnc.com










and some affiliates and just can't figure out what's suddenly going
wrong and why my vnc clients are abruptly closing when trying to
connect. The Server seems ready to go but something goes
wrong. When I
look in the client logfiles.. it's doesn't say anything is
going wrong
and it seems as though a connection was made successfully.










Is there a










logfile mantained by the VNC Server itself that can give me
some ideas
as to why the connection is being dropped.

Ferindo

--
Ferindo Middleton
Sleekcollar.com
_______________________________________________
VNC-List mailing list
VNC-List "at" realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

















--
Ferindo Middleton
Chief Architect
Sleekcollar.com
_______________________________________________
VNC-List mailing list
VNC-List "at" realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list










 ________________________________

Previous message: Unable to connect to VNC Server (Fedora Core 4)








from Win2000 client - Used to work fine








Next message: VNCThing - Mac OS 9, Redux
Messages sorted by:                [ date ]               [ thread ]
        [ subject ]               [ author ]











--
Ferindo Middleton
Chief Architect
Sleekcollar.com










--
(650)254-0869 (home)
(650)210-0615 (work)













--
Ferindo Middleton
Chief Architect
Sleekcollar.com












--
Ferindo Middleton
Chief Architect
Sleekcollar.com










--
Ferindo Middleton
Chief Architect
Sleekcollar.com









-- Ferindo Middleton Chief Architect Sleekcollar.com


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]