Remote Management and Windows VNC clients

Question

Level 1

5 points

Remote Management and Windows VNC clients

Hey guys,

I recently had a go at getting the built-in VNC server in Leopard (as part of remote management) up and running.

Remote control works flawlessly from other Macs, but it refuses connections to Windows clients most of the time (throws up errors like 'Error waiting for server message' or something).

Any ideas? I thought it might have something to do with the Windows client not understanding the encryption, but haven't found any way to change security settings.

Thanks in advance!

Mac Pro, Mac OS X (10.5.6), 2 × 2.66 GHz Dual-Core Intel Xeon, 2 GB 667 MHz DDR2 FB-DIMM.

Posted on Jan 31, 2009 8:38 AM

Reply

Answer 1

BobHarris

Level 9

53,147 points

Jan 31, 2009 9:19 AM in response to stephenshaw

Have you giving the server a VNC password?

System Preferences -> Sharing -> Remote Management -> Computer Settings -> VNC viewers may control screen with password: xxxxxxx

What VNC client are you using on Windows. Not all VNC clients are created equal? I know about TightVNC (which has been reported to work), RealVNC, and UltraVNC are 3 that I've heard about.

You can also install your own VNC server (in parallel using a different port or instead of the Mac OS X VNC). Vine Server (aka OSXvnc) has been used successfully for years. After all not all VNC servers are created equal either 🙂

Reply

Answer 2

stephenshaw Author

Level 1

5 points

Jan 31, 2009 9:58 AM in response to BobHarris

I have set a password. As I said, sometimes it works, sometimes it doesn't. It also seems to break the SSH daemon from time time when I try to tunnel the connection, so it (the daemon) has to be restarted.

I have most of the 'standard' clients: RealVNC, TightVNC, dotnetVNC,etc.

I had been using OSXvnc for a while before this experiment, and it worked flawlessly. I just don't like having to run it alongside Remote Management, since I envisage eventually migrating to full-blown Apple Remote Desktop. 🙂

Reply

Answer 3

stephenshaw Author

Level 1

5 points

Jan 31, 2009 3:00 PM in response to stephenshaw

Ok guys. I've figured out what's happening. Apple being Apple, it has implemented VNC in a peculiar way. It only supports HexTile, so when I tried to use color compression the server would kick the clients.

It works if you turn off all compression, but that means remote control is hideously slow over the Internet. 😟

Still haven't solved my SSH woes...

Reply

Answer 4

stephenshaw Author

Level 1

5 points

Jan 31, 2009 3:01 PM in response to stephenshaw

When connecting an Apple Remote Desktop VNC server from a non-Mac client, you must turn off all color compression.

Reply

Answer 5

Jan 31, 2009 3:02 PM in response to stephenshaw

Windoze has no preinstalled SSH client or server. That is a UNIX thing. You can use Putty for SSH on Windoze.

Reply

Answer 6

stephenshaw Author

Level 1

5 points

Jan 31, 2009 3:05 PM in response to Community User

I know that of course! What I meant was that attempts to tunnel VNC to my Mac seems to crash the SSH daemon on the Mac.

Reply

Answer 7

Feb 3, 2009 8:09 AM in response to stephenshaw

I have three Mac Pros in my office and a MacBook Pro that I use at home. I have previously used Vine Server and Chicken of The VNC client on the MBP. I would like to use the built-in features of Leopard's
VNC server. I have everything working flawlessly in the office, however I cannot figure out how to remote in from home. The Vine Server had the "External" settings that it would give you including port setting and such that you can then input into the Chicken of the VNC client and remote in. Can anyone help me with how to set this up? Thanks.

Reply

Answer 8

BobHarris

Level 9

53,147 points

Feb 3, 2009 8:40 AM in response to ElasticPictures

The built-in Mac OS X VNC server uses port 5900

But since your questions have nothing to with Windows VNC clients (as per the thread title), you should really start a new thread with a properly named title.

Reply