Questions

Migrate to DHCP from a static IP network

Tags:
+
0 Votes
Locked

Migrate to DHCP from a static IP network

conleys
We are currently running an all Windows Environment. We use static IP. We are thinking about setting up DHCP on our Domain controller. If some of the PCs or Copiers are set to static IPs when I enable DHCP, will DHCP try to assign that IP or will it see its being used? I'm not sure if I have to reserve IPs that I plan on keeping static. Thanks
  • +
    0 Votes
    ugadata

    As part of setting up a DHCP server you will assign a consecutive range of IP addresses that the DHCP server will use to assign addresses from. You can limit the scope of the DHCP addresses or exclude one or mre ranges of addresses

    It's not unusual to have servers and printers with static IP addresses and workstion configured as dynamic.


    No, the DHCP server will not be aware of statically assigned IP addresses. If an IP address on the network is availible for DHCP and also has been applied as a static IP address, sooner or later there will be a conflict.

    +
    0 Votes
    Triathlete1981

    we all know the benefits of dhcp. but, depending on what else in on your server, you might not want to create a central point of failure by having your 2003 server running DHCP as well as shared folders.

    you can set up a basic box that doesn't need too many resources, install linux on it and run the dhcp service. set a range between, say, 100 and 199. now set up your statics outside the scope. there'll never be a conflict, and you get a better sense of identifying which is static and which is dhcp simply by looking at the ip!

    as long as the statics are on the same subnet as the dhcp scope, they'll be no problems.

    but if you decide to run the dhcp service on your windows server, then do what the first guy said. but you can use the same idea with dhcp and statics as you would with creating a linux dhcp server.

    the benefit of having a second server just to run dhcp is that there are no potential issues with other apps on the server and there's no central point of failure.

    and realistically you can actually get a very resource unintensive box with a linux dhcp server.

  • +
    0 Votes
    ugadata

    As part of setting up a DHCP server you will assign a consecutive range of IP addresses that the DHCP server will use to assign addresses from. You can limit the scope of the DHCP addresses or exclude one or mre ranges of addresses

    It's not unusual to have servers and printers with static IP addresses and workstion configured as dynamic.


    No, the DHCP server will not be aware of statically assigned IP addresses. If an IP address on the network is availible for DHCP and also has been applied as a static IP address, sooner or later there will be a conflict.

    +
    0 Votes
    Triathlete1981

    we all know the benefits of dhcp. but, depending on what else in on your server, you might not want to create a central point of failure by having your 2003 server running DHCP as well as shared folders.

    you can set up a basic box that doesn't need too many resources, install linux on it and run the dhcp service. set a range between, say, 100 and 199. now set up your statics outside the scope. there'll never be a conflict, and you get a better sense of identifying which is static and which is dhcp simply by looking at the ip!

    as long as the statics are on the same subnet as the dhcp scope, they'll be no problems.

    but if you decide to run the dhcp service on your windows server, then do what the first guy said. but you can use the same idea with dhcp and statics as you would with creating a linux dhcp server.

    the benefit of having a second server just to run dhcp is that there are no potential issues with other apps on the server and there's no central point of failure.

    and realistically you can actually get a very resource unintensive box with a linux dhcp server.