> I set up VNC via SSH (mostly using > http://ubuntuswitch.wordpress.com/2007/07/01/securely-remote-control-your-ubuntu-via-putty-from-a-windows-host-vncssh/) > which works, almost, ok. > > My problem is that after a reboot, I need to login using the local keyboard, > before I can remote in.
Can you clarify. Is the problem not getting a commandline via putty, or not being able to get a vnc connection until you have logged in to your desktop? If you are just running on your local network (as opposed to accessing from elsewhere on the internet, which the article you refer to is about), SSH tunnelling the VNC session is overkill. If you are running headless, you probably don't want 'remote desktop sharing', you want ordinary VNC service, which creates a standalone VNC (though there is an option to automatically log one user in on startup which might work for you) Install an ordinary vnc server "sudo apt-get install tightvncserver" Run the server, follow the prompts it gives you. "tightvncserver" It will say something like New 'X' desktop is mymachine:1 Now you should be able to connect from VNC to mymachine:1 Note the :1, different from :0 if you are doing desktop sharing. > Some posts also mention problems with getting error messages on boot if > there is no monitor (error messages which require a local keyboard or mouse > OK to get rid off) which will also cause problems when I shift it to the > garage. Easy enough to test before you move it. Unplug monitor/kb/mouse, boot, replug monitor, see where it got to. If it works, no need to ask for more help... -- Eliot
