• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DHCP server troubles

dawks

Diamond Member
As I posted in a previous thread, I am migrating from a 2000 Server box, to a Server 2003 box running in a virtual machine. I have been trying to get DHCP to work, but its not going. I configured the new server with what appears to be all the correct settings and authorized it. I then un-authorized the 2000 DHCP server, and tried a release/renew. My XP box (and OS/X box wont get an IP - error sometimes says "DHCP server cannot be contacted). The only thing I can figure would be an issue is that the server is running in a virtual machine, but I can't find anything on that being an issue (the virtual DHCP server is disabled).

Now heres the odd part... We run a Mitel VoIP system. All of our phones use DHCP on boot to get operating info. They can get their configuration settings from the server without a problem, so its partially working.

The other possibility has to do with my previous post where active directory replication is only going one way. The DHCP server is authorized on the Server 2003 box, but perhaps thats not replicating to the 2000 Server box. (Though when I add the Server 2003 DHCP server to the 2000 Server DHCP MMC, and I right click on it, it only shows the 'unauthorize' option, not 'authorize'.)

Any suggestions would be appreciated. Danke!
 
is this one flat L2 subnet we are talking, or a multiple subnet setup? Have you sniffed to see if the replies are getting sent, and have you released and rebooted rather then just release/renew?
 
Originally posted by: nweaver
is this one flat L2 subnet we are talking, or a multiple subnet setup? Have you sniffed to see if the replies are getting sent, and have you released and rebooted rather then just release/renew?

Right now it is just one subnet. We will have two subnets, but I wanted to get the first one working.
I thought of sniffing, but have not tried yet.
I did try rebooting yes.

Originally posted by: ITJunkie
Are you running a managed switch with bootp relay set to the old DHCP server?

This might be something to look into. I do not yet have admin rights to our switch, however I am in the process of getting those rights. I know we have a single port on the switch assigned to handle traffic to our other subnet, so this it may also be that it was programmed to only allow dhcp on the one port/ip. I didn't consider this one.

Thanks for the suggestions.
 
Back
Top