Running window DHCP server in host-only mode on VMware workstation

Hi

I am trying to set up a lab environment using VMware workstation 10.

I have 2 VMs, a Windows 8 client and a Windows Server 2012 R2 server.

I have put them both into VMnet2 which is configured as a host only network.

I have unchecked the box that enables the built in VMware DHCP server.

The windows server 2012 VM has dhcp server set up and it is authorized.

My Windows 8 VM will not pick up an IP address from the server.

Any suggestions to what I am doing wrong?
LVL 1
roy_battyDirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
host only means that it will only communicate with the host and not other vm's nor the outside network.
0
Brett DanneyIT ArchitectCommented:
Do you have a domain controller for this lab? Having an authorised DHCP server you will also need a DC with working DNS. Another issue I can see here is that on physical switches there is a DHCP help address which is the address of the DHCP server, this provides clients with a means to identify the DHCP server and obtain an address. I am not aware of a way to set this helper address on a virtual switch in vmware.
0
roy_battyDirectorAuthor Commented:
I think I have been misunderstanding exactly what "host only" means. I thought any VM added to the host only network would be able to communicate with each other. Is this not the case?

I have therefore put both VMs on a NAT network. I'm still cant get the client to get an IP address from the server.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

roy_battyDirectorAuthor Commented:
After moving both VMs to a NAT network I was still having issues getting the clients to talk to one another. I noriced that there was an additonal TAP-Windows Network adaptor which was confusing things on both VMs.

So I deleted all the network adaptors on both VMs and rebooted them and let them install the adaptors again (this time just the one adaptor each - no TAP)

It is all working now. Client VM is getting IP from DHCP VM.

Many thanks.
0
vivigattCommented:
You were right (and David Johnson is wrong) :
Host only is a "private network" internal to the host that does not allow packets to get outside this network.
All VMs in host-only can communicate together, and they can also communicate with the host, but that's all :
http://pubs.vmware.com/workstation-10/index.jsp?topic=%2Fcom.vmware.ws.using.doc%2FGUID-93BDF7F1-D2E4-42CE-80EA-4E305337D2FC.html

If you want the DHCP server to work from a guest VM, you have to check the usual stuff for DHCP servers.
DHCP server Authorization requires a Active Directory Domain. You can use a stand-alone server (no AD) with DHCP service, and then it does not need to be authorized (because it can't).
Things to check:
- Firewall (disable it completely for diagnosis purposes)
- Network Bindings
- Event Logs
- Reboot the DHCP Server VM and see if this is any better
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
roy_battyDirectorAuthor Commented:
Well its all working now and I also have the benefit of being able to access the internet from the VMs now too.

I only wanted to use host only to stop the Lab interfering with my home network. e.g didn't want wife's laptop to suddenly start getting ip addresses from the virtual dhcp server.

I now realize that this wouldn't happen anyway as the virtual nat network is "protected" by the nat itself. i.e no broadcast dhcp requests.

Now that the host-only function has been cleared up, I feel that the initial issue was caused by the dhcp server binding to the TAP adaptor.

You deserve some point for this but I think its too late now.

Thanks though.
0
vivigattCommented:
You accepted a wrong solution, that does not explain/resolve your issue and that may confuse users in the future !
Once again : a host-only network is a private network in which ALL the guests can communicate together and with the host but not with the outside world.
0
roy_battyDirectorAuthor Commented:
As I mentioned. I think the issue was down to DNS server network bindings.

Thanks for the help guys.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.