DHCP Not Working With Deployed Linked Clone Desktops

Hi All,

I've been working on an issue with my VMWare environment.  I had created a virtual machine in vcenter and attempted to use the MAC address to reserve an IP address in the DHCP protocol from my DC.  I setup the IP range and setup the filter to allow the IP address for this one desktop; however, it doesn't seem to work.  The virtual desktop is stuck with a 169.254 ip address.  Is there something I'm missing with the vm itself?  I'm currently using vSphere 5.5 and View 6.  

Any direction on this would be extremely helpful.

Who is Participating?

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

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.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
seems like it's not getting an IP Address at all.

If you just setup DHCP, set the TCP/IP in the VM to DHCP (Obtain IP Address)

Don't set a MAC Address in DHCP Scope, does it get an IP Address normally ?
Anthony6890Author Commented:

I just noticed that this server I'm working on doesn't have an activated version of Windows Server 2008 R2.  Would DHCP not work if it's not properly activated?
Seth SimmonsSr. Systems AdministratorCommented:
if windows isn't activated and when you login it prompts for a key, network connectivity won't function except for an activation attempt.  so yes, i can see that being the blocker here
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Anthony6890Author Commented:
Ok that makes sense then.  Let me try to get the activation correct and then I'll give it the old college try again.

Anthony6890Author Commented:
Ok, so I was able to activate the server correctly and I removed the MAC address filtering to attempt to get any IP address and still nothing.  Still remains with the 169.254 address.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, so DHCP is not working.

Do you have anything non-virtual which can check DHCP is working ?
Seth SimmonsSr. Systems AdministratorCommented:
is the dhcp server authorized?
can you temporarily give that client a static address and see if you can ping the 2008 server to make sure there are no network issues in between preventing it from getting an address?
Anthony6890Author Commented:
Unfortunately I don't have something non virtual that I can check. Is there a possibility I have an issue with the setup of the vm?  Is there anything I need to do to the vm itself?
Anthony6890Author Commented:
I gave the client a static IP and I can ping the DHCP server.
Seth SimmonsSr. Systems AdministratorCommented:
is there any firewall in between that could cause dhcp communication to not go through?
Anthony6890Author Commented:
The firewall on the Windows side is turned on.  I would have to check and see if the physical firewalls wouldn't allow it.
You said you reserved the MAC address. Are you sure the MAC address is correct for the virtual NIC, and that it isn't being used by any other device that is already running?
Anthony6890Author Commented:
I removed the MAC address reservation to see if I could get any IP address from the range specified and still no luck...
Anthony6890Author Commented:
If it helps any, the network is setup with VLAN's so each designated VM Desktop will have it's own specific VLAN...
Have you checked your DHCP server's logs?
Seth SimmonsSr. Systems AdministratorCommented:
that was another thought that i had...if they are not on the same vlan then that would explain it
the dhcp server would have to be on the same vlan or (if you have cisco equipment) has the ability to have dhcp broadcast go across vlans

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
Anthony6890Author Commented:
Ok, then that's it because they are not on the same VLAN.  So this is something I won't be able to use then, which now makes more more sense.
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

From novice to tech pro — start learning today.