need some info about what is needed to get things going. installed tightvnc w/ mandrake 9.0, and kde desktop. i get a shell, and xserver dialog box- so what is needed to get it working? noticed some threads talk about viewers as well ( would hope to see the desktop). searched the available docs, but seem to come up dry. i think a config guide should pop up when any input is needed. assistance is appreciated.

Take a look at:
http://www.uk.research.att.com/vnc/start.html

And for a more detailed list of docs on all platforms:
http://www.uk.research.att.com/vnc/docs.html

even though i'm using tightvnc, vnc config is applicable? ok- thanks for the info.

Yes - TightVNC was developed from the source of VNC. The TicghtVNC site even points you to the VNC site for documentation. The commands are all the same except that TightVNC is more secure and offers compression.

dave, no luck so far

tightvnc was installed as an add on from mandrake (stated download- previously i've had an occurance of taking it off of the cd set). i'm just wondering at what status tightvnc exists on my system currently?

i try to input commands, (the tightvnc selection brings up a terminal, and server dialog box) and is unresponsive to commands.

i'd like to test what's installed to see where it's at. i might even uninstall it, and go a different route. not sure if it's my lack of knowledge of commands, or if the module (correct term?) is not installed correctly, or needs to be activated some how?

dave, i tried a different konsole/ terminal (still not 100% sure of the differences) other than the one presented when i selected tightvnc. i was able to start a couple of servers. i then killed the ones that i started (vncserver :1, vncserver :2, vncserver -kill :1, vncserver -kill :2), i then figured that i'd try to kill a server w/o a # [vncserver -kill (think that's correct)], which killed tightvnc- gave version #, and some commands. had a hunch that the install would activate something- this was activated w/o a password. still not sure what's the correct manner, but i figure if i kill it, then i can start over!

still puzzled by the terminal that opens w/tightvnc.

It looks like you have manged to install and get the server side working. The next thing to do is go to another machine and see if you can connect to the server.

dave, i have tried to connect w/ a windows machine running win2kpro. i did get connected to one of the machines through it's ip address, but what i saw was really perplexing! i was able to get my kde desktop of a machine that i was currently using w/ gnome!?!?! i have another comp that is much slower, so when i saw the kde desktop, i figured that i had gotten it. it was like, man this thing is really responding fast, this doesn't make sense, and then after a couple of wtf's it dawned on me- so then i manually hooked my keybd, mouse, and monitor to it, and yes it was running the gnome desktop!

so what do you make of this?

btw, i did load all desktops available w/ mandrake 9.0. perhaps installing multiple servers, then ties vnc to different desktops? perhaps there is some potential there for performing sysadmin (or cracker) functions while the comp is being used? perhaps i'm the one to crash the party? anyway, i really want access that is correct- w/o any freakish split personality stuff (yeah, call it psycho, or skitzo- cool dudes- ?!?!?).

perhaps when they say to verify all source packages/ and verify kernel, ect.. before using, there is a reason. i'm definitely not doing things correctly right now. i think that this is a lesson of some sort that i won't forget!

The deskto environment depends on what commands is in the file:
~/.vnc/xstartup

This is the command that is run when you connect. It usually loads a window manager or gui program.

i didn't to my knowledge add any commands to a line like that. this might be done by tightvnc, as kde is default browser. i think i faintly remember seeing a reference to setting when i entered vncserver in a terminal (after passwords were entered). i need to the make certain to pass the desktop to the tightvnc module (correct term?)?

does this command (:~/.vnc/xstartup) stand alone or is the tilde recognized as a tie-in to another command?

btw, is there a core linux code logic that would be helpful (something to copy and hang at or near my monitor)- perhaps rules, syntax, associatives (whatever?? )?

The tilde represents your home directory - eg:
/hom/len/.vnc/xstartup


As for guides - most people reccomend the "Rute User's Tutorial and Exposition":
http://www.icon.co.za/~psheer/book/index.html.gz

thanks again!

btw, rute's appears to be quite popular.