Windows Server 2003 DHCP issue - binding problem?

jeffvcs · 2012-09-21T19:31:41.000Z

I’ve got a server with 2 NICs that I want to supply DHCP for one interface.

Both interfaces are static IPs, one on 172.24.4.x and the other on 172.24.8.x.

The 8.x interface should be the DHCP server for that network.

I set the interface to static, created a scope in the proper range, gave it the proper options, stared the DHCP server the server and activated the scope.

Clients can’t pull IP addresses on either interface.

When I try to bind the server to the interface (Right click on the sever, add binding) I see both interfaces, I can put a check box in the interface I want to use, but I cannot click apply. If I click OK the box does not fill in.

I’ve reinstalled the DHCP service, I’ve reinstalled the NIC, but no joy.

Anyone have idea?

dustoncourtney0806 · 2012-09-21T19:43:10.000Z

Does DHCP work when you only have one scope?

craignj · 2012-09-21T19:51:11.000Z

If you can’t click “Apply” that’s usually due to a ranged IP scope issue, I would first double check that your IPs are all correct.

I’ve never tried it on a server…but if you use Windows Enabler, it will allow you to click that Apply button =)

dustoncourtney0806 · 2012-09-21T19:55:33.000Z

Also this is gonna sound stupid but try disabling IPV6 aswell.

jeffvcs · 2012-09-21T20:11:20.000Z

I only have one scope…so…nope ;p

Looks like you win CraigNJ. A fabulous NEW CAR!*

it’s going to be a scope issue.

Just as a test I put in a plain old 192.168.0.x scope and it works.

I’ll have to double-check my scope.

*Actual car not given.

craignj · 2012-09-27T15:56:31.000Z

I already have a car, but I’ll take the cash option instead!