VMware Cloud Community
Barnman
Contributor
Contributor
Jump to solution

Need help with DHCP on Windows 2003 R2 VM in ESXi

Hi there,

I've recently downloaded and installed ESXi on a new IBM X 3400. I have a VM with Windows Server 2003 R2, and I've migrated the DHCP server role over from another box. When I turn off the service on the other box and start it in the VM I am unable to service DHCP requests. It's as if I don't have a DHCP server on my network.

Any ideas?

Reply
0 Kudos
1 Solution

Accepted Solutions
DLeid
Expert
Expert
Jump to solution

can you confirm that the DHCP server is authorized using the DHCP manager.

If you find this or any other information helpful or correct, please consider awarding points.

View solution in original post

Reply
0 Kudos
7 Replies
DLeid
Expert
Expert
Jump to solution

Can you ping the new DHCP server from the vm?

If you find this or any other information helpful or correct, please consider awarding points.
Barnman
Contributor
Contributor
Jump to solution

Hi,

Sorry I should have indicated that before. Yes, the server had good ping. DNS runs fine, and it sucessfully joined the domain. It appears as if there is some issue with the DHCP broadcast packets. The other thing I thought of is trying to get DHCP running without doing a migration/import, and then importing the reservations later.

Reply
0 Kudos
DLeid
Expert
Expert
Jump to solution

can you confirm that the DHCP server is authorized using the DHCP manager.

If you find this or any other information helpful or correct, please consider awarding points.
Reply
0 Kudos
RParker
Immortal
Immortal
Jump to solution

When I turn off the service on the other box and start it in the VM I am unable to service DHCP requests. It's as if I don't have a DHCP server on my network.

This isn't a VM issue. You need to talk to your Network Admin and have them change your helper address on the network switch to allow this new Server to be the DHCP for the network. Either that or set the IP the same as the last DHCP server. That's the problem.

The network switch tells the network cards where to 'look' for their DHCP scope, if you don't have this set, your NIC's will be 'duh'.... That's what's going on.

Reply
0 Kudos
hstagner
VMware Employee
VMware Employee
Jump to solution

Yep, I will have to agree with Rparker here. I would check the "UDP Helper" address in the core switches / routers (whatever you have). Change it if the VM has a different address (like Rparker said) or change the VM address to the same one as the previous DHCP server (if possible).

Don't forget to use the buttons on the side to award points if you found this useful (you'll get points too).

Regards,

Harley Stagner

----------------------------------------- Don't forget to mark this answer "correct" or "helpful" if you found it useful (you'll get points too). Regards, Harley Stagner VCP3/4, VCAP-DCD4/5, VCDX3/4/5 Website: http://www.harleystagner.com Twitter: hstagner
Barnman
Contributor
Contributor
Jump to solution

Thank you for the suggestion gentlemen. At most locations I run that would be an excellent idea, except at this location I'm running an un-managed switch.

I'll try redoing DHCP from scratch and see what happens. I thought there might be a trick with the Virtual Switches to let in the broadcast packets, but I see now that isn't the case.

I'll post back once I find out more. Thank you for your suggestions.

Reply
0 Kudos
Barnman
Contributor
Contributor
Jump to solution

Hi again. I worked this last night a bit and it is a domain issue. There DHCP Authorization issue is just the most visible. I'm rolling back the server and starting again from scratch.

Thanks for all of your input--they are all good suggestions.

Reply
0 Kudos