Remote desktop requires confirmation.

[RET423]

I have been trying to figure out a way to get PcLinuxOS 2009 to stop asking for a confirmation when I connect to the machine via VNC.

I have used the pcc wizard from both root and my default user but it always requires someone to be at the machine to confirm the request, once the connection request is confirmed the password box will appear on the other machine and I can enter the password and control the target normally.

I use vnc to control this computer from the other end of my house so it sort of defeats the purpose if I have to run down the hall and confirm the VNC request to complete the connection. Is there some way to tell the pclinuxos 2009 box to always accept the remote desktop connection?

[GuypronouncedGuynotGuy]

are you running the VNC service on the host system?

You should be able to password protect the connection, then as long as you know the password it should work fine. (I do the same thing here)

[RET423]

are you running the VNC service on the host system?

You should be able to password protect the connection, then as long as you know the password it should work fine. (I do the same thing here)

I think so, I used pcc to setup remote desktop sharing and I told it to "allow others to control this machine" and "start the service", I was prompted to enter a password and the the wizard completed.

I can successfully contact the computer from any of the others in my workgroup but unless I am at the terminal to click "allow" the password box never appears on the computer I initiated the connection with.

[GuypronouncedGuynotGuy]

sounds like you have it correct. Could be a bug with the beta.

[RET423]

O.K. Here is what I did.
I had been using krfb as the vnc server because that is what is configured from pcc.

I stopped that service and grabbed tightvnc server from the repository (tightvnc client was already installed by default) and I configured tightvnc. I can now log in to the PcLinuxOS desktop from any machine on the network with just the vnc password and no confirmation prompt needed at the local machine.

The only problem I am having now is figuring out to get tightvnc to start automatically with the machine in a state that is ready to use. I have the service enabled (and it shows "running") but I have to run "vncserver" from a terminal after boot-up and renter the password for it to function.

A small inconvenience since I never shut this machine off but I would like to automate the process at some point.

[pags]

Are you using 2009 still with KDE 3, or has it been updated to KDE 4?

In KDE 3, it can be set from within the KDE Control Center (see http://www.pclinuxos.com/forum/index.php/topic,70220.msg577118.html#msg577118).

For KDE 4, I couldn't find it in a centralized area, but when I ran krfb from the konsole, it opened a window to manage invitations from.  On there, there is a "Configure" button.
On the config window, go to "Security".  Add a check to "Allow uninvited connections", and then remove the check from "Ask before accepting an uninvited connection".  I would strongly recommend a password.

Hope that helps. 

[RET423]

Are you using 2009 still with KDE 3, or has it been updated to KDE 4?

In KDE 3, it can be set from within the KDE Control Center (see http://www.pclinuxos.com/forum/index.php/topic,70220.msg577118.html#msg577118).

For KDE 4, I couldn't find it in a centralized area, but when I ran krfb from the konsole, it opened a window to manage invitations from.  On there, there is a "Configure" button.
On the config window, go to "Security".  Add a check to "Allow uninvited connections", and then remove the check from "Ask before accepting an uninvited connection".  I would strongly recommend a password.

Hope that helps. 

Yeah, I am running 2009 specifically because of KDE-3 (thank you to the developers for keeping this as long as possible!). This particular server does not have enough RAM to make use of KDE-4 and I never use it as a desktop anyway. I just like the stability of PcLinuOS and it is easy to setup and then forget, it just does its job.

The steps you describe are exactly the routine I went through, I don't know why krfb keeps asking for confirmation. Tightvnc is doing great except for me having to remember to click the application link I put on the desktop to enable it after a reboot. If I forget the service is not usable until I do it.