Connecting to VMware VNC server with Mac OS X Snow Leopard Screen Sharing client

[ryandesign]

I find that I am not able to connect to VMware Fusion 3.0.1 VMs with VNC enabled using Mac OS X 10.6.2's built-in Screen Sharing program (/System/Library/CoreServices/Screen Sharing). I have tested a guest running Mac OS X Server 10.6 and another running Linux 2.6, so I don't think the guest OS matters. The vmx file has these lines added:

RemoteDisplay.vnc.enabled = "TRUE"
RemoteDisplay.vnc.port = "5902"

I attempt to connect to the VM by entering "vnc://localhost:5902" into the Safari address bar, or by typing "open vnc://localhost:5902" in the Terminal. Either way, Screen Sharing opens and says "Contacting 'localhost'..." and never connects. I have tried other valid hostnames for this computer, with no change. Yes, I am certain the hostname and port are correct; if I use a different hostname or port, Screen Sharing instead shows the error message "Connection failed to ''." Two other Mac OS X VNC viewers -- Chicken of the VNC 2.0b4 and JollysFastVNC 1.00 -- both connect to the VMware VNC server successfully. Meanwhile, Screen Sharing can connect successfully to another Mac OS X VNC server -- Vine Server 3.1.

Is there a way to make VMware's VNC server work with Mac OS X's built-in Screen Sharing VNC client? It is preferable to be able to use VNC without having to install another 3rd-party program.

Yes, I can run a separate VNC server within the guest OS, but it is desirable to control the VM's screen from the moment it starts up, and without needing to install or configure anything inside the guest.

[asatoran]

Try using the Finder, Go Menu, Connect To Server. Type in the same thing you did (vnc://x.x.x.x:590x).

I normally just open the Screen Sharing app directly, rather than going through Safari or Terminal. If you type directly in to Screen Sharing, you do not need to type "vnc://" prefix.

[daemonchild]

Two things to try here:

- Drop to a terminal and try a "netstat -an | grep 5902". This will show you whether fusion is actually listening on port 5902 for incoming connections.

- Check your OS X firewall settings. (Yes, I realise this is locahost to localhost, but worth a check?)

---

VCP, VCI, MBCS CITP

[TEMc]

Just curious, did you get this working. I have the exact same problem with a very similar set up. I have even tried disabling all firewalls but still get on ongoing "Contacting" when I try to remotely connect to the Fusion VM.

UPDATE: I got it working. It took two steps. 1) I must have a password entered on the Fusion VM Settings options for VNC and 2) I had to reduce the screen color resolution on the Windows 7 environment to 16-bit Color from 32-bit.

The first thing I did was the password which got me in but the screen was basically not refreshing at all. On the host the mouse pointer was moving and things were happening but you didn't see anything on the client/guest side. After changing the the color resolution it worked. I tried to remove the password but was back to the "Connecting...." point.

[ryandesign]

asatoran, using the Finder's Connect To Server or entering the hostname and port directly into the Screen Sharing app makes no difference.

daemonchild, turning off the firewall makes no difference. Yes, netstat shows it is listening on the port, and I am able to connect to it using two other VNC clients on this computer, just not using Apple's built-in Screen Sharing VNC client.

TEMc, thanks, enabling the VNC password was the trick. This is fine since I will want a password anyway, I just hadn't set it up yet.

So, whose bug is it that Screen Sharing cannot connect to VMware Fusion's VNC server when it doesn't have a password -- Apple's or VMware's? Do I need to report this bug to VMware more formally or is this forum posting sufficient?

[rcardona2k]

I am able to connect to it using two other VNC clients on this computer, just not using Apple's built-in Screen Sharing VNC client.

So, whose bug is it that Screen Sharing cannot connect to VMware Fusion's VNC server when it doesn't have a password -- Apple's or VMware's? Do I need to report this bug to VMware more formally or is this forum posting sufficient?

This sounds like Apple's bug. To take VMware out of the loop, try using a different VNC server like VineServer. Rather than being a bug, Apple may not allow their client to connect to VNC servers without a password, in this case, the bug may be that the connect button should be dimmed until you enter a password.

[ryandesign]

I had tested Vine Server before, but only with a password. Testing now without a password, I see the problem there too. So you're right, it's a Screen Sharing issue. I've filed this as rdar://7527653 .

[asatoran]

asatoran, using the Finder's Connect To Server or entering the hostname and port directly into the Screen Sharing app makes no difference.

I'm able to use OSX Screen Sharing to VM in Fusion on local host, as attached screen shot illustrates.. Screen shot shows Fusion 3.0 and Screen Sharing client from OSX 10.6.2. OSX firewall is disabled. The only issue I have with this is slow screen update when going to local host this way. But Screen Sharing client works for me when I VNC to other machines. (More specifically, I normally VNC directly to the VM rather than through the host, as this is company procedures to maintain consistency with remote access to physical machines.)

[ryandesign]

asatoran, do you have a VNC password set in your virtual machine settings? If so, that would be consistent with everything observed above. I only see the problem when I do not have a VNC password set.

[asatoran]

asatoran, do you have a VNC password set in your virtual machine settings? If so, that would be consistent with everything observed above. I only see the problem when I do not have a VNC password set.

Yes, I have a password set. Company policy. We found other VNC variants that had issues when no password was set. (Not Apple Screen Sharing servers or clients. This was with PCs VNCing to PCs.)

(And sorry, I missed that bit in your post where you said it worked after you added the password.)