DHCP is especially dangerous when combined with an unprotected wireless network. You wouldn't think this would happen very often, but homeowners who don't understand the risks do this all the time. This makes it possible for someone to sit with a laptop in a car on the street and gain access to every network resource: every computer, every network drive, and every tablet or phone connected to the LAN.
It's like leaving your doors and windows open while at the same time leaving a welcome mat out for data and identity thieves. For most home networks, fully dynamic or mixed addressing configurations are just fine. As long as all wireless networks are locked down and no "bad guys" can gain physical access to the network, DHCP is a good option for easy home networking. But if you are truly serious about network security—if you have sensitive data residing on your network or just want to make data or identity theft much less likely—you're probably better off sticking with disabling DHCP and maintaining full manual control of your home network.
Free Magazine. Smart Home Magazine Smart Home is the magazine that brings you the latest trends in home control solutions and smart devices. Download Free. Get Started Sign up below to receive more information. First Name. Last Name.
An advantage of a static IP is when one of the users brings in their home wireless router and plugs it into the network it doesn't stuff up everyone network connectivity. I've had this discussion a number of times with various admins and managers over the years.
The danger with DHCP is it is just so useful for pushing networking settings to all your devices, without having to actually touch them, that the temptation is to add everything in there.
This results in the DHCP server being vitally important for your network. When not if your DHCP server falls over, you can be scrambling to get connectivity working. Personally, I configure servers and networking gear switches, routers, WAP with static addresses. This way they are always available provided they have physical network connectivity. Printers are setup using reservations in DHCP to make changing them over easier.
Like anything DHCP is a tool and needs to be used to minimise admin overheads, and maximise up time. Having said that, there is very little need for static addresses in this day and age except for the actual Layer3 network infrastructure that provides routing on your network. The desktop guys are often hard to convence that their printers have no need for static addresses, and the network guys are even harder to convince that their Layer2 devices' management addresses don't need to be static, but with a lot of that work being shifted over to unskilled labour using various SDN tools, all that static stuff is finally disappearing.
You can have network failure scenarios whereby only one DHCP server sees the offer and it ignores it because it assumes its partner will send the offer.
If the failure scenario is a link agg bug, even that test might lead you astray. People who assign IP addresses statically then have to maintain spreadsheets consisting of "static" data that fails to keep up with the dynamic reality of what's on the network. Forget it. As for the comment above about static IPs for routing traffic DHCP can use reservations to keep a device on the same IP address so it isn't simply about remembering.
It's never mattered so far, but it makes sense just in case. Everything else gets static. I have a standard for how I break up subnet ranges, so I know what is what, and it is documented well. As a bare minimum I would say all networking devices should have static, and would strongly recommend servers physical and virtual also get static. I only do servers and printers statically, outside of the DHCP scope, which usually starts at. Everything else is controlled with DHCP. I liked doing reservations for printers.
It usually made swapping out a printer fairly seamless for end users. Yeah I can see that, but for the last 10 years i've been working to rid offices of small personal printers and replace them with 2 leased large MFP's so the occurrence of swapping out printers is very rare for me :.
The key here is to not rely on a single DHCP server. It works and it probably fine for SOHO type installations. For an enterprise network, however, your far better off with redundant servers to perform the job. To continue this discussion, please ask a new question.
Get answers from your peers along with millions of IT pros who visit Spiceworks. Let me know. Edited Jul 30, at UTC. Popular Topics in General Networking. Which of the following retains the information it's storing when the system power is turned off? List of Partners vendors. Bradley Mitchell. Updated on June 16, Chris Selph. Lifewire Technology Review Board Member. Article reviewed on May 09, Tweet Share Email. In This Article. Static IP Address Uses.
Static vs. Was this page helpful? Thanks for letting us know! Email Address Sign up There was an error. Please try again. You're in! Thanks for signing up.
There was an error. Tell us why! More from Lifewire. What Is the Dynamic Host Configuration Protocol. Your Privacy Rights. To change or withdraw your consent choices for Lifewire. At any time, you can update your settings through the "EU Privacy" link at the bottom of any page.
0コメント