strange tightvnc issue

[S.D.Willie]

hey, after doing some searching around im wondering something. im using kde as my default desktop. when i start tightvnc from my mandrake box i run

vncserver : 27 <-- so its running on display 27 right?

well when i access this machine from my windows box over my lan i get the connection, it logs in after password prompt but i get windowmaker running instead of kde. :rolleyes:

i have startkde in my .xinitrc file as well. is there something else im missing? i also log in from the cli with startx and kde starts so it seems kde is my default desktop but as far as vnc goes.............

[Cuthbert]

Take a look in your ~/.vnc directory and edit the file called xstartup to call KDE rather than WindowMaker.

[S.D.Willie]

thanks yeah i see what the problem was. but i only have an X server with my wallpaper, but no kicker, no icons, blah blah.

http://www.uk.research.att.com/vnc/extras.html#x0rfbserver

do i HAVE to use X0rfb? ive used it on my lan but dont know how good it is remotely. also, is there a port i need to forward in my linksys router from vnc?

dont matter, x0rfb does me no good as it gives me the same window.

[S.D.Willie]

bump?

[hlrguy]

Why are you specifying 27 as the desktop number? I have had problems with VNC when the desktop numbering gets out of sync. I have 5 running on my WS at work, all with the desktops configured the way i need them, however, when I start, for example, desktop 5, specifying 5 as the server and 4 doesn't exist, I get the same problem you have. The bottom line, at least for me, is I now script it to start them sequentially, with sleep 3 between commands so that when 2 is started, 1 already exists, 3 before 4, 4 before 5, etc. Try starting it without specifying the desktop number, then connect to the one it picks and see if that is better.

hlrguy

[S.D.Willie]

ok, i guess when you run vnserver the display SHOULD be on 1 and not 0 right?(unless specified like 27 as i was using)

as in id be connecting to"localhost1" right?

ill have to change the display later on when im at home. my other question is what is the syntax to connect to my home machine is im running vncviewer from say mandrake at work? i have a router(linksys) and i have ports 5900 to 5901 forwarded.

my assumption is when i run vncviewer its:

myipaddress:1
doesnt seem right to me as i though id have to put it the port number somewhere.

as far as the kde thing its not a big deal, im using fluxbox now and i see it fine when i run vnc at home on my lan.

edit: i think i might know what the problem is but i cant verify it until later/tomorrow. in my router i have ports 5900 to 5901 forwarded for vnc.
stupidly, i ran vncserver:27 when i was at home so when i try logging in it wont connect.

my guess? i should be using
vncviewer ipaddress:5901

since the display for fluxbox would be on 1 correct?

[hlrguy]

Originally posted by S.D.Willie
ok, i guess when you run vnserver the display SHOULD be on 1 and not 0 right?(unless specified like 27 as i was using)

..what is the syntax to connect to my home machine is im running vncviewer from say mandrake at work? i have a router(linksys) and i have ports 5900 to 5901 forwarded.

my assumption is when i run vncviewer its:

myipaddress:1
doesnt seem right to me as i though id have to put it the port number somewhere.

edit: i think i might know what the problem is but i cant verify it until later/tomorrow. in my router i have ports 5900 to 5901 forwarded for vnc.
stupidly, i ran vncserver:27 when i was at home so when i try logging in it wont connect.

my guess? i should be using
vncviewer ipaddress:5901

since the display for fluxbox would be on 1 correct?

VNC desktops start at 1 and go up (0 is always reserved for the console, VNC won't 'steal' it, but you are correct, although I connect at localhost.localdomain:1 for the first VNC server started locally.

Your connection to work is correct. vncviewer <myip>:1. The viewer knows that :1 is 5901, :2 is 5902, etc.

I checked the docs at /usr/share/doc/vncdoc, and it does specify that you can manually start, in their example, vncserver 13, withouth 1-12 running, but like I said, that caused me to have the problem you are having.

hlrguy

[S.D.Willie]

ill be trying this tomorrow(in a few hours look at the damn clock! ugh) so ill let you know how it goes.

SD

edit: ok, when i run vnc viewer(mandrake laptop @ work) with the ip address and the port number it just hangs. i figured id try rfbdrake and low and behold it connects but as soon the the image on the desktop loads it crashed and disconnected. i tried getting back in but it just hung again. i couldnt even connect with tightvnc on my windows box at work, just hung and timed out eventually. what a pisser this task has become.

[S.D.Willie]

just to update i ran the vncserver on my redhat 9 box(another i had) and i was able to connect from my job when using xorfb.

problem is, i see the desktop but after about 3 or 4 seconds the connection just drops and i lose the screen. with tightvnc on winders i STILL cant access this anyhow so one thing at a time. why would the connection just drop in x0rfb?

i tried connecting in vncserver like so:

vncviewer -geometry 800x600 -depth 16 myipaddress:5901

but yet it still hangs so at least i was able to get in with xorfb for a few seonds b4 it dropped. how frustrating.

[S.D.Willie]

just wanted to follow and finish this thread happily. i am able to actually connect to my "current" running KDE desktop(from work) with x0rfb. problem was i had to connect with"

myipaddress:0 instead of :1 as the session.

THEN im able to connect from tightvnc on windows and what not. i also set gnome as my default desktop so when i run vncserver and i connect remotely i get a full gnome desktop which runs though on :1 and not :0 as x0rfb does. :)

ill tell you though, both are slow with even fluxbox running on vncserver! but, alas, at least i accomplished what i wanted to do. heres a shot of the proof from a win98 machine running tightvnc to my mandrake box running rfbdrake

[hlrguy]

Cool. I will have to try X0rfb sometime. Although, my machine at work never has X running. I use it purely as a passthrough and VNC server. Happy trails. If you get *****ious and want to speed up the VNC view, you can pipe it through SSH. Here is a thread on that....

http://justlinux.com/forum/showthread.php?s=&threadid=106184&highlight=vnc+and+ssh

I describe how I got VNC over ssh running in post #11. For me, over 56K, it speeds it up immensely. (ABout 6 times faster)

hlrguy

[S.D.Willie]

cool deal, thanks, ill have to check that thread out.