Configuring VNCserver in Linux...

[stix_kua]

I have a Red Hat Linux 9 box setup and I want to be able to VNC from my Windows box to the Linux box but I cannot get it to work. I have issued this exact command and still nothing works...

vncserver :1 -name redhat9 -depth 16 -geometry 800x600

but Windows cannot find the host yet. As far as I know, vnc server is already up and running. The real thing that gets me is the fact that I can however use TightVNC from Linux and see and control the Windows box but only after entering an IP address and then the computer's name and then the password.

If I do not do it in that order from Linux, it will not connect. This works even if it is not the correct IP address...

[stix_kua]

Anything?

[rraehal]

Do you need to confgure Samba so Windows thinks Linux is a windows PC before it will try to connect to the VNC server? I know that VNC packages often offer Java packages so that no additional software is needed to control the host. Maybe Windows does not want to work with a non-windows host.

I have never tried VNC because I use pcAnywhere as needed for this. I have also used remote desktop a little. I telnet to my linux box unless I need to make major changes and then I will log into it directly.

[stix_kua]

Originally posted by rraehal
Do you need to confgure Samba so Windows thinks Linux is a windows PC before it will try to connect to the VNC server? I know that VNC packages often offer Java packages so that no additional software is needed to control the host. Maybe Windows does not want to work with a non-windows host.

I have never tried VNC because I use pcAnywhere as needed for this. I have also used remote desktop a little. I telnet to my linux box unless I need to make major changes and then I will log into it directly.

I think I got it figured and didn't need to configure Samba...Thankfully...

I can connect fine but for some reason vncserver is not a startup item. How do I fix that? Thanks rraehel...;)

[rraehal]

You should have a script that will start your VNC server. You may need to custom write it.

Once you have the script you can go to /etc/rc3.d (Run level 3) and rc5.d (Run Level 5) and copy the script there. It must sat with a capitol S and have a number just like the other files. Anything that has a capitol S will start when that run level is enetered. anything with a K will be killed when the run level is changed (going to X from the command line or restarting).

You shoul dlook at the way the links are set up. each file in the rc#.d directories has a link to another directory where all start scripts are kept. You could set up your script the samne way. I don't remember the command to make the link as I do not know if the startup scripts are hard links or symbolic links.

[stix_kua]

Originally posted by rraehal
You should have a script that will start your VNC server. You may need to custom write it.

Once you have the script you can go to /etc/rc3.d (Run level 3) and rc5.d (Run Level 5) and copy the script there. It must sat with a capitol S and have a number just like the other files. Anything that has a capitol S will start when that run level is enetered. anything with a K will be killed when the run level is changed (going to X from the command line or restarting).

You shoul dlook at the way the links are set up. each file in the rc#.d directories has a link to another directory where all start scripts are kept. You could set up your script the samne way. I don't remember the command to make the link as I do not know if the startup scripts are hard links or symbolic links.

Didn't need to write a script...i just had to get to Services configuration menu and check on vncserver and then restart...

But thanks for the help...:)