Originally Posted by Antipathy
So your workstation (host) is a Windows XP box that is a member of the domain. The VM running on this host is also a member of the domain? And it can communicate with the domain controller, but not the host?
Sorry for the confusion everyone, this is the general idea yes. My workstation is part of the domain, and is the host of the VM. I can see the VM from the domain controller, but not from the workstation (host).
I'm using VMware player 3.0.0, along with the specialised folding image located here
. I dont thinks its running apache (unless that's what's built in to it) but even so all configuration should be possible through the web based utility. Here's a screenshot of the configuration (taken from the domain controller, as the host (workstation) cannot access this page)
The domain controller on the local subnet has an IP address of 192.168.0.2, while the main router is 192.168.0.253. My workstation is 192.168.0.27. The workgroup field is set to the domain name with the .local suffix. I have 2 virtual network adapters on the workstation named "VMware Network Adapter VMnet1" and "VMware Network Adapter VMnet8", both of these have seemingly random IP Addresses that were automatically generated by VMware. The normal "Local area connection" has the VMware bridge protocol enabled. I can ping both of the virtual adapter addresses, and oddly enough, I can also ping 192.168.0.20, which is the address of the VM. I cannot however, add this IP to HFM.Net in order to monitor it, nor can I access it by typing \\192.168.0.20\fah into the run box.
EDIT: I don't think permissions are an issue, I'm a member of both the Administrators and Domain Admins security groups