• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DHCP Client

M

Modular

Diamond Member
I noticed this in my log on my router:

2006/07/24 15:56:35 DHCP Client : Request sent from (IP Address here)
2006/07/24 15:56:35 DHCP Client : Server response sent from (IP Address here)

Should I be concerned? Maybe it's best to shut off the DHCP client.

What does it do? Should I disable it?
 
Keep DHCP enabled on your router unless you want to manually enter the IP address for each computer, which I don't recomend.
 
Originally posted by: tfinch2
Originally posted by: InlineFour
Keep DHCP enabled on your router unless you want to manually enter the IP address for each computer, which I don't recomend.
Click to expand...

And which totally sucks.
Click to expand...

Hi tfinch2, I always see you in here.

Although, static IP addressing is mandatory for servers. 😀
 
Originally posted by: InlineFour
Originally posted by: tfinch2
Originally posted by: InlineFour
Keep DHCP enabled on your router unless you want to manually enter the IP address for each computer, which I don't recomend.
Click to expand...

And which totally sucks.
Click to expand...

Hi tfinch2, I always see you in here.

Although, static IP addressing is mandatory for servers. 😀
Click to expand...

y helo thar.

That would suck having to reconfigure port forwarding on your router everytime your lease is up. 😛
 
Few things here. Your log and what your seeing is for your router. Sounds like the discussion following the original post was about nodes on your LAN. Assuming your ISP hands out DHCP leases, and they would usually unless you request and pay for a static IP, then having your router's DHCP client service is a must. It's just getting a new IP when the lease on the existing IP is up. Something like 14 days. Maybe 3 days. Could be 3 hours. Up to your ISP typically.

Static IP for a server is a best practice though not mandatory. I also prefer static IP addressing on my network. It's not as if most of us have 100 machines to address. I have 7 or 8 nodes and consider that more than average but still prefer to address statically. With that said most SOHO routers will continue to hand out the same IP to DHCP clients normally. It's a pseudo static Ip anyway and for the average user DHCP client addressing on a home network is preferable and many times necessary to avoid confusion by the user.
 
Originally posted by: tfinch2
Originally posted by: InlineFour
Originally posted by: tfinch2
Originally posted by: InlineFour
Keep DHCP enabled on your router unless you want to manually enter the IP address for each computer, which I don't recomend.
Click to expand...

And which totally sucks.
Click to expand...

Hi tfinch2, I always see you in here.

Although, static IP addressing is mandatory for servers. 😀
Click to expand...

y helo thar.

That would suck having to reconfigure port forwarding on your router everytime your lease is up. 😛
Click to expand...
I agree that the DHCP client should remain enabled but wanted to point out that static addresses are not mandatory for most servers (although frequently it's a good idea). Just like with hardcoded clients it can quickly become a PITA to maintain a large number of hardcoded servers.

Anyway, if you cant trust DHCP and DNS than you have problems, so may as well take advantage of them when it makes sense. Some examples where it might not be a bad idea:
Development servers
File servers
Departmental servers (that arent doing DHCP or DNS)
VMWare servers
Some NLB Clusters
etc.

Admins that maintain the "This is always the best way to do job X" mentality are the ones that (eventually) run into trouble down the road.
 
Originally posted by: ktwebb
Assuming your ISP hands out DHCP leases, and they would usually unless you request and pay for a static IP, then having your router's DHCP client service is a must. It's just getting a new IP when the lease on the existing IP is up. Something like 14 days. Maybe 3 days. Could be 3 hours. Up to your ISP typically.
Click to expand...

Very good then. That what it is. I only have three computer connected to the router:

Lappy
Desktop
Desktop

So I'm assuming this was the 2 week Comcast DHCP release.

Thanks.
 
DHCP client does other things beside getting an IP address. For example, in a domain environment, it registers records in DNS. This is espeically critical for domain controllers. DCs by design must have a static IP, so people assume they can turn off the DHCP client, which usually ends badly.
 
DHCP client does other things beside getting an IP address. For example, in a domain environment, it registers records in DNS. This is espeically critical for domain controllers. DCs by design must have a static IP, so people assume they can turn off the DHCP client, which usually ends badly.
Click to expand...

People probably wouldn't assume that if the service didn't mysteriously do more than it's name suggests.
 
If every service had information on every task they performed in the service name the names would be useless 😉

Besides, what good is google if nobody uses it.
 
Also, per DHCP lease time, the DHCP client will renew the lease half-way through the leases' expiration period (so if you had a 6 day lease, it would renew it at the 3 day mark)...so in theory, your lease would never change from what the router handed to you if your machine was (nearly) always on.
 
It isn't too smart to make assumptions about things without full knowledge of what it does.
Click to expand...

Obviously, but IME Windows admins are all about making assumptions without reading the docs.
 
Nice generalization there.
Click to expand...

Well of all the ones that I've met I can count on one hand the ones that I know read documentation about things before they jump in and start clicking and hoping.
 
Nothinman, you just lost a few points in my book with that. You still have plenty of points left but it's disappointing anyway.

🙁
 
Originally posted by: stash
DHCP client does other things beside getting an IP address. For example, in a domain environment, it registers records in DNS. This is espeically critical for domain controllers. DCs by design must have a static IP, so people assume they can turn off the DHCP client, which usually ends badly.
Click to expand...

:thumbsup:
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top