Ken Schneider wrote:
rsesktop is for connecting to windows servers.
so it isn't for connecting to other Linux PCs. Ok , thanks
rdesktop isn't just for connecting to windows machines. I connect to a SuSE 8.2 machine through a ssh session and through a firewall regularly using rdesktop. vncserver runs on the remote machine and rdesktop fires up the the local one. The ssh command I use is "ssh -C -X -L 5905:192.168.1.5:5901 user@myserver.no-ip.com". The remote machine is protected by an IPCop firewall which allows requests coming in on port 22 from my local IP address. ssh then tunnels to the 192 address within the remote DMZ. Start up rdesktop locally and point it to localhost:5 and ssh tunnels the request to the remote vncserver. If your client and server are local you don't need the ssh stuff. I only included it in case others were curious. The issue you're seeing Damon is that windows only has one display so when you run vncserver on that display you effectively export that display through vnc. Any vncviewer client will then connect to it and will see what the remote user sees. On UNIX X can run multiple displays, as can vncserver. If X is using display :0 then vncserver will start up on the next free (virtual) display - in this case :1 so you don;t see what the remote user sees (:0). Damian