Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[I_want_an_Omega]

Can anyone provide clarification on using DHCP in the context of a home network please.

Network is a BT wireless Router, HP laser printer connected via Ethernet and a load of PCs via wireless.

When I set it up an IT chum suggested having the printer set to a fixed IP address rather than use DHCP - this has proven to be reliable as it was a bit hit and miss when set to DHCP before.

Thing is that I now want to add a HUMAX networked PVR. It gives me the option of DHCP or fixed IP address. Which should I do as I'm sure that there are  pros and cons with each.

TIA - Rob

[Kevin Wood]

DHCP is simply a server task running, probably on your router, which hands out IP addresses to all machines connected to the network which have "obtain an address automatically" set.

I would normally say let it allocate a dynamic one as this way each machine should always get a unique address and you don't have to keep track of that. The server is doing that for you.

The time when you might want a static IP address is for devices that you need to connect into from one of the hosts on the network. Your printer might have a web-based management interface, for example. Tricky to find unless you know what IP address is on.

I guess the same might be true of the Humax box? Having said that, it might well come with software to manage it which will locate it on the network anyway.

"Always on" devices such as a set top box will generally keep the same DHCP-assigned address for a long period of time anyway, so one you've found it once, you should be able to remember the IP address.

What you must ensure is that any static IP addresses you assign are outside the range of IP addresses that the DHCP server is allocated as its' "pool" or you will get multiple devices sharing the same IP address, which is often fun.

Kevin

[TheBoy]

As you never need to connect to the Humax, set it DHCP - it matters not if its IP changes (which it shouldn't, though I don't believe the Humax comes out of standby to renew its lease).

General rule of thumb for less intelligent devices is to keep static for those devices you need to connect to, and DHCP everything else (intelligent devices like PCs have other ways of finding out IP addrsses of other intelligent devices)

[cem_devecioglu]

I also use some enough amount of pcs and printers at home.. but as a general habit I always use static ip's.. I find it easy to adress and map them whenever required.. using dhcp is mostly designed for  crowded environments that add or remove many pcs at a time where there is already loads of machines which will take time to find a free ip for one imo..

[Chris_H]

I always tend to gravitate towards static IP addresses eventually.

The main disadvantage is portable devices that come and go on the network.  They work best with dynamically-allocated IP addresses as it means you don't have to tweak settings every time you do connect.

As mentioned, the thing to remember is to take the static IP addresses you use out of the pool that the DHCP server can allocate, otherwise you risk getting a conflict when some new device connects.

Network printers are a classic example of being a pain on DHCP.  You can get round it with dynamic DNS but I always plump for static on them.

[TheBoy]

I tend to use DHCP - those that need statics (printers, MCE etc) are set to DHCP, but have reserved addresses.  Makes it much easier to change networks around - routers, DNS, boot servers etc etc.

[aaronjb]

I tend to use DHCP - those that need statics (printers, MCE etc) are set to DHCP, but have reserved addresses.  Makes it much easier to change networks around - routers, DNS, boot servers etc etc.

Ditto to that.