Remote Desktop to a Windows 8.1 guest

[jborn]

Hi all,

I'm trying to get Remote Desktop working from an Windows 8.1 guest running on OS X Mavericks on my Mac Pro. I have Display, Remote Display, Enable Server checked and on Server port 3389. Under network setting I have Adapter 1: Attached to: Bridged Adapter. From my google searches that is all I should have to do, but from the host I cannot ping the assigned IP address. From my Mac Book Pro I cannot connect to the assigned IP address.

What am I missing? Is there some OS X setting to allow this traffic to go through? Something on my router? Since I can't even ping from the host, I'm not sure where to begin.

Thank for any help!

[socratis]

- In your Windows guest run in the Command Prompt "ipconfig" and post the output.
- In your OSX host run in the Terminal "ifconfig" and post the output.
- Check the firewall status on your guest. Pay attention to the Private/Public networks.

[jborn]

After ruling everything else out I found out that you can download an application called "Microsoft Remote Desktop" that will connect to the Windows 8.1 guest OS from a separate computer running Mavericks. The "Remote Desktop Client Version 2.1.1" will not work.

[jborn]

Well, I thought I had this figured out 6 months ago, but I plan to use this next week and retested this week. It did not work, so I'll post what I know.

Latest VirtualBox version 4.3.16 r95972
I still have a Windows 8.1 guest. Fully updated with all patches.
OS X 10.9.4 (this is a Hackingtosh also)

When I use Microsoft Remote Desktop Version 8.0.9 (Build 25073) I can connect from the Host, but not a separate computer on the same local network.

Guest ipconfig /all output:

Code: Select all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Hoth
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : 10.157.236.38
                                       10.157.236.22

PPP adapter Peachtree Geographics VPN:

   Connection-specific DNS Suffix  . : peachtree.local
   Description . . . . . . . . . . . : Peachtree Geographics VPN
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.2.3.50(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 0.0.0.0
   DNS Servers . . . . . . . . . . . : 10.2.3.21
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-F3-73-D8
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6989:ed08:7b09:e34c%3(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.190(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 50855975
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-73-7E-3F-08-00-27-F3-73-D8
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{059F9902-7E7D-45C2-BDF6-209D9C225658}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.peachtree.local:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : peachtree.local
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Host ifconfig -a output:

Code: Select all

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet6 ::1 prefixlen 128 
	inet 127.0.0.1 netmask 0xff000000 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
	ether 94:de:80:a0:e4:01 
	inet6 fe80::96de:80ff:fea0:e401%en0 prefixlen 64 scopeid 0x4 
	inet 192.168.1.141 netmask 0xffffff00 broadcast 192.168.1.255
	nd6 options=1<PERFORMNUD>
	media: autoselect
	status: active

[jborn]

I recently retested this and it is finally working! I'm not sure if the fix was Windows 8.1 updates, VirtualBox updates, OS X updates, or numerous fiddling with various network settings.

I think the fix was turning my router into more of a switch, but once again that is a hunch.

[loukingjr]

I would go with the "numerous fiddling with various network settings" choice. As near as I can tell, most networking problems are because of bad configurations.