Jump to content

Recommended Posts

Posted

Hi All

 

So I am having a bit of an issue creating the new DHCP server on our new network.

 

We have a new physical server running Xenserver 7.0 and the DHCP is being run on Server 2016.

Our switches are all HP and the core switch has the the old DHCP hard coded into the Trap Receiver

 

So these are the steps I have done so far...

 

  • Created new DHCP on Server 2016
  • Assigned the same IP address and MAC address to the network for the new VM hosting the new DHCP so it mimics the OLD DHCP server settings.
  • The Core switch has the Trap Receiver set to the old DHCP and this goes for every other switch in the school so by giving the new DHCP server the same IP I can save a lot of time by not changing the IP address on ever switch.
  • I have made a copy of all the scopes from the old DHCP and copied them to the new one (checked all the copes for consistency).
  • I then un-authenticated the old DHCP and stopped the DHCP Server service then authenticated the the new DHCP and restarted the service.

 

I have added the credentials for the server on the IPV4 settings on the DHCP settings here:

AdminSettings.png

 

The bindings is set to the IP address of the server like the old one DHCP server is:

Bindings.png

 

So with all of that I get the Blue Explanation Mark on the IPV4 saying I have run out of IP address which is wrong because I have thousands left so no IP address are being sent out

 

BlueMark.png

 

What else could I be missing? Its been driving me mad for weeks.

 

Any help with the issue would be brilliant

 

Regards

 

Safa

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...