@iP


Recommended Posts

I've never had to ask a question here but I'm doing this in faith hoping someone can help. I feel that I have looked at everything I possibly can w/ logic.

OS: Fedora

What happens:

When I run TightVNC client on an XP Pro box connecting to my Fedora box I:

-Get the password prompt

-Login

-Get Black/White fuzzy **** with an "X" as a cursor.

I can't see the desktop, or do ****.

What I've Done:

I found an article that made reference to a flaw in the original Fedora VNCSERVER package. They have an update available which I downloaded and installed ( I assume - Since the installer procedures went as normal )

I rebooted after the install yet problem still persists.

Other Info:

- Fedora comes with an automated KDE remote assistance feature, which creates a password and a time window for remote login. When I create one w/ this wizard, I can connect fine!

- I do believe that I read an article that stated having two vnc servers running can cause my symptoms.

- I also read something that made reference to "xvnc" which apparently is what allows the desktop to be displayed via terminal connection.

- In terminal, I'm typing vncserver [enter]. It states that a server was started successfully and gives me the port Ie :0.

- I also read that you should specify a name for the port and password using vncpasswd / something similar. I did so successfully, yet when I try to connect to that specific port, no go again. BTW, when I say "port" obviously I'm not talking "data port" but the logical channel / terminal. I am specifying them correctly also IE 192.168.X.X:X

- I went into "services" and vnc is the only thing oriented to this that I can find. Obviously its started. Stopping it does halt my connections so it seems to be the right service.

- I also read somewhere, which suggested I ditch the default packaged VNC server and download "realvnc". I did this successfully; went through previous procedures with the same non-functioning results.

Plead

I'm really hoping someone can shed light on this because I konw that if the KDE Desktop Sharing feature works, there has to be a way to get this functioning. PLEASE HELP

Thanks in advance,

asdf

Link to comment
Share on other sites

I had this one time... not sure exactly what caused it or what fixed it... but here is all I remember.. I killed off all vncservers running (or you could reboot, windows sytle!). Next I started a normal x server (startx). Then I started vncserver. that put it on display 1. Never had a problem since them.

I really like Fedora, but man its certainly got some strangeness compared to RH9. Good luck!

Link to comment
Share on other sites

Try the following while logged on as the user who will run the VNC:

touch .xinitrc

echo "gnome-session" > .xinitrc

(or should you be using KDE)

echo "kdestart" > .xinitrc

Then restart the VNC server and enjoy.

Link to comment
Share on other sites

Im checking things out again now. I did one of the steps above

- logged in as regular user on fedora, went to terminal, typed the following

me@blah: touch .xinitrc

me@blah: echo "gnome-session" > .xinitrc

- The next step was to restart the server so, I went to services, and vncserver wasnt listed.

I added it and checked it.

Then rebooted.

Came up, logged in as normal user..

Went to terminal and typed vncserver

It started :1 w/ the name of X

Went to remote PC, logged in, and got a blue-ish/green-ish colored window putting me at the terminal. I tried typing startx but it said :0 was using it.

I saw somewhere that I could share my current session. Maybe thats it. Im giong to play with it some more now.

Here is my blah:1.log

>vncserver

01/02/04 17:24:26 Xvnc version 3.3.7 - built Feb 28 2003 18:27:24

01/02/04 17:24:26 Copyright © 2002-2003 RealVNC Ltd.

01/02/04 17:24:26 Copyright © 1994-2000 AT&T Laboratories Cambridge.

01/02/04 17:24:26 All Rights Reserved.

01/02/04 17:24:26 See http://www.realvnc.com for information on VNC

01/02/04 17:24:26 Desktop name 'X' (X-nix1:1)

01/02/04 17:24:26 Protocol version supported 3.3

01/02/04 17:24:26 Listening for VNC connections on TCP port 5901

01/02/04 17:24:26 Listening for HTTP connections on TCP port 5801

01/02/04 17:24:26 URL http://X-nix1:5801

gnome-session: you're already running a session manager

01/02/04 17:24:38 Got connection from client 192.168.10.200

01/02/04 17:24:38 Protocol version 3.3

01/02/04 17:24:40 Pixel format for client 192.168.10.200:

01/02/04 17:24:40 8 bpp, depth 8

01/02/04 17:24:40 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6

01/02/04 17:24:40 Using ZRLE encoding for client 192.168.10.200

01/02/04 17:25:55 Client 192.168.10.200 gone

01/02/04 17:25:55 Statistics:

01/02/04 17:25:55 key events received 35, pointer events 96

01/02/04 17:25:55 framebuffer updates 116, rectangles 268, bytes 11998

01/02/04 17:25:55 ZRLE rectangles 268, bytes 11998

01/02/04 17:25:55 raw bytes equivalent 1037453, compression ratio 86.468828

TIA

Link to comment
Share on other sites

ah , one way round this is to just goto the linux machine and do "xterm -display localhost:0&" replacing 0 with the display number

you then get a terminal on the vnc desktop which can be used to run a window manager or whatever

Link to comment
Share on other sites

Still havent gotten it to work guys.

I dont understand why the Desktop Sharing Application works fine in gnome. It shares the gnome desktop and everything. The file name is KRFB. The problem w/ KRFB in gnome, is that it only allows the defaults, meaning opening the krfb utility automatically sets the password and one hour duration.

If I use the KDE manager instead of gnome, there is a utility in the control center that allows configuration of an "always on" type of account. Check these pics:

configuration.png

Is there a way that I can that utility in a gnome session? Via gui or terminal will work. I just want remote access to my desktop :(

Link to comment
Share on other sites

I got it working. What did I do?

Went to http://www.karlrunge.com/x11vnc/ and downloaded the x11vnc server package from the projects page under "download"

Then simply installed it w/ ./configure make then make install

typed in x11vnc, and wala Went to my windows PC, opened Tight VNC, typed in server IP :0 Bam, no pswd by default so, its up.

Gotta customise it and put on some security w/ passwords and ssh but... hopefully this will help anyone else w/ the same prob.

Thanks for the help guys. :)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.