Dhcp client configuration

Hello,
we have two dhcp server running in our network. However, only one distributes ip adresses
I can use to access the internet. How can I configure the dhcp client such that he accepts
only ip adresse from the correct server ? In linux a simple
reject <server ip>
in /etc/dhclient.conf does the job, but I don't find any configuration file for the dhcp client
on my Mac OS X system.
Thanks
Michael

Hi Michael,
No expert here, but I wonder if we don't do that in /etc/hostconfig ?

Similar Messages

How to configure dhcp client identifier

Hi Everybody,
The DHCP client ID is an id that is unique for DHCP clients at least in the same subnet. Usually the client uses MAC-address as Client-Identifier in the DHCPDISCOVER message. The Client-Identifier may be different other than MAC-Address, For example a FQDN name, as per the RFC 2132 Ref, (code 61).+_
Usaually, we use the following to bind the ip address based on MAC-address
pntadm -r SUNWfiles -p /var/dhcp -A 10.42.32.86 -i '0:3:ba:a5:a9:93' -a 10.42.32.80
At server side, I am using the following for specifying the FQDN name.
pntadm -r SUNWfiles -p /var/dhcp -A 10.42.32.86 -i 'one.atr.com' -a 10.42.32.80
and at client side, I am inserting the following entry in the /etc/default/dhcpagent file
CLIENT_ID='one.atr.com'
But this is not working. What I am doing wrong.
+1. At the server side, then how to assign the ip addresses to the clients , if the Client-Identifier is FQDN name in the DHCPDISCOVER message other than MAC-Address.+
+2. How to configure the client-identifier as FQDN name at client side.+
Please help me,
Thanks Inadvance,
Mummaneni.

Sandman,
Here is an example of a router acting as a DHCP server. Please remember that you have to exclude IP addresses that you don't want to lease out.
ip dhcp pool example
import all
network 192.168.1.0 255.255.255.0
dns-server 1.2.3.4
default-router 192.168.1.1
ip dhcp excluded-address 192.168.1.1 192.168.1.149
ip dhcp excluded-address 192.168.1.200 192.168.1.254
HTH,
Mark

Cisco ASA 5505 and DHCP Client Problems

Hi, i have a problem. I've connected my ASA appliance to an ADSL modem, and i dont get an DHCP address on the outside interface (e0/0). I use the asa-722-19.bin firmware.
I turned on the debugging for the DHCP client and could see that the ASA device was sending out broadcasts but a reply never came. Instead I connected the device to my internal network where the ASA got an address instantly.
I read somewhere that if I was to use ?ip address dhcp client-id fastethernet 0″, then I got an address from the ISP.
I tried looking for a similar command on the ASA5505 but I couldn?t find anything. I did however find a page on the Cisco site confirming my suspicions. It said some ISP?s require the client-id field of the DHCPDISCOVER request to be filled.
I've also read that this issue has beed fixed since a few weeks, now they have released version 7.2(2).22 where you can define ?dhcp-client client-id interface outside? in global configuration mode. Im running 7.2(2).19 and i cannot find any command like that in my appaiance. How do i fix my problem ? Or how do i get about recieving the 7.2(2).22 firmware update.
Regards !
Leif

Hi again! I thought I should share the solution that worked for me. I use software version 7.2(2) on this device. ASDM 5.2(2). In ASDM open configuration / Interfaces. Click in outside (my case 0/0) and press Edit. Then open the tab Advanced and set the correct Active Mac address. Fore some reason its empty by default and the ISP/modem don't like that. You will find the correct MAC address under the help menu / "About ASA". Im sure there is some another way to do this but this is a simple "how-to" that works with Swedens biggest ISP and their standard DSL modem.
When I used a Linksys DSL modem in bridge mode without the MAC address set I got an inside IP adress (192.168.x.x) from the modem to the ASA. After setting the MAC address I just had to do a renew and got the outside address right away. /Bjorn
(future users searchwords: no ip from isp, ASA 5505 and cable modem).

Using Extreme in Bridge mode, can't see the DHCP clients if the D-Link router

I have an Airport Extreme attached to my DLink modem/router. I have configured the Airport Extreme in Bridge mode, and I was expecting all clients to show up in my D-Link router. Although the configuration works most of the time, I have been experience a few issues:
1. From time to time, computers attached (both Windows and/or Mac) complain about an IP address conflict. I can ignore the error and it works fine.
2. From time to time, I loose Internet connectivity, and I need to disconnect my computer and reconnect again to solve the issue. This is not necessarily linked to symptom #1
3. On my D-Link router/modem (which I only use to connect my Airport to my ISP), if I check the DHCP clients, I can see the Airport router connected and *some* of the wireless clients that connect through the Airport. The list changes quite randomly, and at times, I see the airport appearing twice with different IP addresses.
Any help configuring it "right" will be appreciated!
Alain

When the AirPort Extreme is in bridge mode, the AirPort Extreme is simply passing through the DHCP settings and services that are handled by the D-Link modem/router.
In other words, the D-Link device is in total charge of the DHCP services for devices on the network.
You might want to check with D-Link support to see if they have any recommended practices for configuing the modem/router when another router....the AirPort Extreme in this case....is being used in bridge mode on the network

WRT54G v7 WAN DHCP client problem

I've recently started having a strange problem with my WRT54G. Internet access is via a Cable modem and has been working fine for months, and the cable modem works fine so I suspect the problem is with the router. However the router is also working, mostly, so I figured I'd see if anyone here has any suggestions. Here are the details of the problem:
The router WAN configuration was set to DHCP.
It used to happily pick up a new IP address from the cable modem whenever necessary.
One night the router stopped picking up an IP on the WAN side. (nothing was changed. I'm the only one in the house who goes anywhere near the router)
Connecting the modem directly to a PC works fine (suggesting the modem's DHCP server is fine).
Copying the WAN IP config from the PC to the router, as a Static IP, also allows it to work when the modem is plugged back into the router and the router to a PC (which is how it's setup now, but it's a pain to have to mess with the physical connections and manually reconfigure the router every time the modem drops a connection (which is another issue, but not one for this forum...)).
So both the modem and the router seem to work except for the router's DHCP client. It works fine as a DHCP server for the LAN.
The firmware was already upgraded (and working), I've followed the standard power-cycle procedure, I've released and renewed the IP via the Status tab in the web interface, and I've tried resetting the router using both the button on the unit and via the web interface to revert to factory defaults.
Any suggestions?
Solved!
Go to Solution.

I also had this problem which occurred after >2 years of the router working fine. After changing MTU to 1300, cloning the PC MAC address, and power cycling the router and modem fixed the problem. But I was curious to see which change did the trick, so I changed both back to the default (MTU = auto and not cloning the MAC address) and it worked fine! I think the router problem is intermittant and may appear to be fixed by changing setting, but I fully expect it to reoccur.

How to setup default gateway in a DHCP client. The default gateway will be the Ip address of the server that has RRAS installed, hence routing cabalities.

How to setup default gateway in a DHCP client. The default gateway will be the Ip address of the server that has RRAS installed, hence routing cabalities.

Hi Bill,
Thank you for replying back...Yes, I was actually asking how do you set the default gateway address on the DHCP server?,
I believe I got the answer below:
To configure the DHCP default gateway option Click Start, point to Administrative Tools and then click DHCP. In the console tree, expand the applicable DHCP server, expand IPv4, and then right-click Scope Options Click Configure Options, check 003
Router, type the applicable Server name and IP address, and then click OK.
Thank you

DHCP client fails to get an valid IP address from DHCP server. windows 8.1

I have a win 8.1 Pro 64 bit pc in my office .I'm trying to connect it to my wireless cisco router with either wireless or hardwired connection but I get an error in the event viewer with discription DHCP error 1007. and Ip address showing
169.254.93.17 but our dhcp range is 192.168.1.x
Log Name: Microsoft-Windows-Dhcp-
Source: Microsoft-Windows-Dhcp-Client
Date: 23/Jun/2014 12:03:21 PM
Event ID: 1001
Task Category: Address Configuration State Event
Level: Error
Keywords: (1)
User: LOCAL SERVICE
Computer: sanddeplap.vts.com
Description:
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0xF4B7E22D8721. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its
own from the network address (DHCP) server.
Event Xml:
<Event xmlns="http://schemas.">
<System>
<Provider Name="Microsoft-Windows-Dhcp-
<EventID>1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>75</Opcode>
<Keywords>0x4000000000000001</
<TimeCreated SystemTime="2014-06-23T08:03:
<EventRecordID>363</
<Correlation />
<Execution ProcessID="988" ThreadID="7932" />
<Channel>Microsoft-Windows-
<Computer>sanddeplap.vts.com</
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HWLength">6</Data>
<Data Name="HWAddress">F4B7E22D8721<
<Data Name="StatusCode">121</Data>
</EventData>
</Event>
I tried to track issue with microsoft network monitor I'm attaching the capture file also please help me to sort out this issue
capture report https://onedrive.live.com/redir?resid=AFE3D0245A92F6F8%21183

The issue is that your machine is not being assigned an IP address / was unable to reach the DHCP server to receive one. The 169.254.x.x IP your machine is showing isn't assigned from DHCP, it's assigned by the local machine and is referred to as an APIPA
address.
So something is preventing your machine from reaching your DHCP server, which could one of a number of things. In the first instance I'd suggest having a look at
http://epan36.blogspot.co.uk/2012/09/eventid-1001-dhcp-your-computer-was-not.html which lists several of things that could cause this error and things you can try in order to resolve it.
If none of those work, can you confirm whether you have any other machines connecting via the same method on the network, which might indicate whether this is an issue at the machine end or somewhere between the machine and DHCP server?

Policy Based Routing with VPN Client configuration

Hi to all,
We have a Cisco 2800 router in our company that also serves as a VPN server. We use the VPN Client to connect to our corporate network (pls don't laugh, I know that it is very obsolete but I haven't had the time lately to switch to SSL VPN).
The router has two WAN connections. One is the primary wan ("slow wan" link with slower upload 10D/1U mbps) and it is used for the corporate workstations used by the emploees. The other is our backup link. It has higher upload speed - 11D/11U mbps, (fast wan), and thus we also use the high upload link for our webserver (I have done this using PBR just for the http traffic from the webserver). For numerous other reasions we can not use the `fast wan` connection as our primary connection and it is used anly as a failover in case the primary link fails.
The `fast wan` also has a static IP address and we use this static IP for the VPN Client configuration.
Now the thing is that because of the failover, when we connect from the outside using the VPN Client, the traffic comes from the`fast wan` interface, but exits from the `slow wan` interface. And because the `slow wan` has only 1mbps upload the vpn connection is slow.
Is there any way for us to redirect the vpn traffic to always use the `fast wan` interface and to take advantage of the 11mbps upload speed of that connection?
This is our sanitized config
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp client configuration group dc
key ***
dns 192.168.5.7
domain corp.local
pool SDM_POOL_1
acl 101
max-users 3
netmask 255.255.255.0
crypto isakmp profile sdm-ike-profile-1
   match identity group dc
   isakmp authorization list sdm_vpn_group_ml_1
   client configuration address respond
   virtual-template 1
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec profile SDM_Profile1
set security-association idle-time 3600
set transform-set ESP-3DES-SHA
set isakmp-profile sdm-ike-profile-1
interface Loopback0
ip address 10.10.10.1 255.255.255.0
interface FastEthernet0/0
description *WAN*
no ip address
ip mtu 1396
duplex auto
speed auto
interface FastEthernet0/0.3
description FAST-WAN-11D-11U
encapsulation dot1Q 3
ip address 88.XX.XX.75 255.255.255.248
ip load-sharing per-packet
ip nat outside
ip virtual-reassembly
interface FastEthernet0/0.4
description SLOW-WAN-10D-1U
encapsulation dot1Q 4
ip address dhcp
ip nat outside
ip virtual-reassembly
no cdp enable
interface FastEthernet0/1
description *LOCAL*
no ip address
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/1.10
description VLAN 10 192-168-5-0
encapsulation dot1Q 10
ip address 192.168.5.1 255.255.255.0
ip nat inside
ip virtual-reassembly max-reassemblies 32
no cdp enable
interface FastEthernet0/1.20
description VLAN 20 10-10-0-0
encapsulation dot1Q 20
ip address 10.10.0.254 255.255.255.0
ip access-group PERMIT-MNG out
ip nat inside
ip virtual-reassembly
!!! NOTE: This route map is used to PBR the http traffic for our server
ip policy route-map REDIRECT-VIA-FAST-WAN
no cdp enable
interface Virtual-Template1 type tunnel
ip unnumbered Loopback0
tunnel mode ipsec ipv4
tunnel protection ipsec profile SDM_Profile1
interface Virtual-Template3
no ip address
interface Virtual-Template4
no ip address
ip local pool SDM_POOL_1 192.168.5.150 192.168.5.152
ip forward-protocol nd
!!! SLOW-WAN NEXT HOP DEFAULT ADDRESS
ip route 0.0.0.0 0.0.0.0 89.XX.XX.1 5
!!! FAST-WAN NEXT HOP DEFAULT ADDRESS
ip route 0.0.0.0 0.0.0.0 88.XX.XX.73 10
ip nat inside source route-map FAST-WAN-NAT-RMAP interface FastEthernet0/0.3 overload
ip nat inside source route-map SLOW-WAN-NAT-RMAP interface FastEthernet0/0.4 overload
access-list 101 remark SDM_ACL Category=4
access-list 101 permit ip 192.168.5.0 0.0.0.255 any
access-list 101 permit ip 10.10.0.0 0.0.0.255 any
ip access-list extended FAST-WAN-NAT
permit tcp 192.168.5.0 0.0.0.255 range 1025 65535 any
permit udp 192.168.5.0 0.0.0.255 range 1025 65535 any
permit icmp 192.168.5.0 0.0.0.255 any
permit tcp 10.10.0.0 0.0.0.255 range 1025 65535 any
permit udp 10.10.0.0 0.0.0.255 range 1025 65535 any
permit icmp 10.10.0.0 0.0.0.255 any
ip access-list extended REDIRECT-VIA-FAST-WAN
deny   tcp host 10.10.0.43 eq 443 9675 192.168.5.0 0.0.0.255
permit tcp host 10.10.0.43 eq 443 9675 any
ip access-list extended SLOW-WAN-NAT
permit ip 192.168.5.0 0.0.0.255 any
permit ip 10.10.0.0 0.0.0.255 any
route-map FAST-WAN-NAT-RMAP permit 10
match ip address FAST-WAN-NAT
match interface FastEthernet0/0.3
route-map REDIRECT-VIA-FAST-WAN permit 10
match ip address REDIRECT-VIA-FAST-WAN
set ip next-hop 88.XX.XX.73
route-map SLOW-WAN-NAT-RMAP permit 10
match ip address SLOW-WAN-NAT
match interface FastEthernet0/0.4

Can you try to use PBR Match track object,
Device(config)# route-map abc
Device(config-route-map)# match track 2
Device(config-route-map)# end
Device# show route-map abc
route-map abc, permit, sequence 10
Match clauses:
track-object 2
Set clauses:
Policy routing matches: 0 packets, 0 bytes
Additional References for PBR Match Track Object
This feature is a part of IOS-XE release 3.13 and later.
PBR Match Track Object
Cisco IOS XE Release 3.13S
The PBR Match Track Object feature enables a device to track the stub object during Policy Based Routing.
The following commands were introduced or modified: match track tracked-obj-number
Cheers,
Sumit

Setting options in DHCP client ...

Hi everyone, ...
Im having problems connecting to my corporate intranet DHCP network and investigating I realize the DHCP server requires a fixed DHCP Option 60 (vendor-class-identifier) with the value "MSFT 5.0".
Please, How can I configure this option in my osx DHCP client?
Regards,
Raul.

So you Mac is supporting Windows 2000 or older Microsoft operating systems? That is what Microsoft DHCP Vendor and User Classes. The 10.6.x system shouldn't need and changing.

How get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?

Hi,
I have a RVS4000 router with DHCP enabled and in router mode.
The LAN is 192.168.2.x. The RVS4000 static IP address is 192.168.2.8
The router is not the RVS4000 and is at 192.168.2.1
The RVS4000 dhcp is assigning it's clients a default gateway of 192.168.2.8 instead of what I want 192.168.2.1.
How can I get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?
Thanks

Hi Gail, you cannot do this. The router, as the DHCP server will only assign a default gateway of what IP interface the DHCP server runs on. If you have the default IP, the gateway is 192.168.1.1. If you create a second vlan, by default it would be 192.168.2.1.
There are not configuration options for the built-in DHCP server. If you'd like to expand this functionality, you would need an external dhcp server.
-Tom
Please mark answered for helpful posts

DNS record ownership for DHCP clients

my configuration:
dhcp/dns/dc installed on same system - Windows 2008 R2 SP1 in domain environment.
all zones configured to secure updates only with aging and scavenging enabled
dhcp servers are member of DNSupdateproxy group.
dhcp are configured with standard domain user account (this user was made a member of dnsupdateproxy as well, DOES THAT MATTER?)
dhcp scopes are configured with default DNS setup (force DNS update by DHCP)
now...
all DNS records for endpoint devices on dhcp lease (windows7, mac os X, ubuntu) are owned by SYSTEM
in security tab for some DNS records i can see service account with write permission to record ( i believe this is desired state)
in other records service account has no permission but timestamps are still updated by computer account (hostname$ has write permission). these records have pencil icon on computers in dhcp lease table.
Problem with this (hostname$ has write permissions) is when user connect to network via VPN (obtains dhcp lease) it get's two records registered in DNS -> 1 record for ip distributed by dhcp server and 2nd record for his home private network.
Have anyone seen this before?
i've tried deleting DNS records / releasing ip on endpoint device (example win7). It would not register to DNS by DHCP. However if i do ipconfig /registerdns it will do it, but dhcp service account won't have permission no this record.

Apparently it appears that DHCP may not be configured with credentials, DHCP DNS settings are not configured to force DHCP to register ALL requests, nor has the DHCP server itself have been added to the DnsUpdateProxy group. These are all prerequisites
for DHCP to own all records, otherwise you will see default behavior, which is:
By default, a Windows 2000 and newer statically configured machines will
register their A record (hostname) and PTR (reverse entry) into DNS.
If set to DHCP, a Windows 2000 or newer machine will request DHCP to allow
the machine itself to register its own A record, but DHCP will register its PTR
(reverse entry) record.
The entity that registers the record in DNS, owns the record.
In summary:
Configure DHCP Credentials. The credentials only need to be a plain-Jane, non-administrator, user account. Give it a really strong password.
Set DHCP properties, DNS tab, to update everything, whether the clients can or cannot.
Add the DHCP server(s) to the Active Directory, Built-In DnsUpdateProxy security group.
Make sure ALL other non-DHCP servers are NOT in the DnsUpdateProxy group. For example, some believe that the DNS servers or other DCs not running DHCP should be in it. They must be removed or it won't work.
On Windows 2008 R2 or newer, DISABLE Name Protection.
If DHCP is co-located on a Windows 2008 R2 or Windows 2012 DC, you can and must secure the DnsUpdateProxy group by running the following:
dnscmd /config /OpenAclOnProxyUpdates 0
Configure Scavenging one one DNS server. Set the NOREFRESH and REFRESH values combined to be equal or greater than the DHCP Lease length. What it scavenges will replicate to others anyway.
DHCP Service Configuration, Dynamic DNS Updates, Scavenging, Static Entries, Timestamps, DnsUpdateProxy Group, DHCP Credentials, prevent duplicate DNS records, DHCP has a "pen" icon, and more...
Published by Ace Fekay, MCT, MVP DS on Aug 20, 2009 at 10:36 AM 3758 2
http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group.aspx
Good summary:
How Dynamic DNS behaves with multiple DHCP servers on the same Domain?
http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/e9d13327-ee75-4622-a3c7-459554319a27
DNS Record Ownership and the DnsUpdateProxy Group
http://technet.microsoft.com/en-us/library/dd334715(v=ws.10).aspx
DNS Record Ownership and the DnsUpdateProxy Group
"... to protect against unsecured records or to permit members of the DnsUpdateProxy group to register records in zones that allow only secured dynamic updates, you must create a dedicated (NON-ADMIN) user account and
configure DHCP servers to perform DNS dynamic updates with the credentials of this account (user name, password, and domain). Multiple DHCP servers can use the credentials of one dedicated user account."
http://technet.microsoft.com/en-us/library/dd334715(WS.10).aspx
DNS record ownership and the DnsUpdateProxy group
http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/b17c798c-c4b2-4624-926c-4d2676e68279/
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights.

Why doesn't my airport express router issue proper DNS server address to DHCP clients?

I have an Airport express router (version 7.6.4). It was configured to connect to internet via a cable modem, acting as a router with NAT. This means it obtians WAN address from cable modem, and in LAN it assumes IP address 10.0.1.1 as a gateway, and issue IP address to my 4-5 wireless clients (MBA, iPads, PCs) vi DHCP.
However I recently encounter an issue, that the router no longer issues DNS server address obtained from Cable Modem(206.x.x.x) but instead tell every DHCP client to use router ip address (10.0.1.1) as DNS server. I was pretty sure before Dec 2013 it is issueing (206.x.x.x) to all DHCP clients.
Apparently now the Airport express is acting as a DNS server or as a DNS cache. This works sporadically and very often result in long DNS look up or DNS look up failure.
Is this a bug or is it supposed to do so? Any configuration can turn it off so Airport express will issue Cable modem obtained DNS server to DHCP clients?
My network otherwise works fine. for some of the Clients (e.g. one MBA) I configured DNS for it mannually and it's internet is working very smoothly.

But this will be a problem for my ipad and iphone that uses wifi.
These devices either allow full DHCP. If you need to mannually enter DNS server, you will need to turn entire IP configuration to mannual and that will be a problem for me.

Strange DHCP client identifier

I am troubleshooting DHCP between server and client (both Cisco IOS). I have discovered, that server sees client under completely nosensical client identification:
R1#sh ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
10.0.6.3 0063.6973.636f.2d30. Apr 01 2001 10:40 PM Automatic
3062.302e.6332.3838.
2e31.3637.312d.4661.
30
Yes, the client id server sees is "3062.302e.6332.3838.2e31.3637.312d.4661.30" instead of little more conventional "00b0.c288.1671". What's up here? This thing makes manual binding impossible, as that long number is not accepted in "client-identifier" on server.
Edit: No, I wasn't cut'n'pasting properly, that long client-id can be entered into pool configuration. So that solves the problem, and the only think that remains unanswered for me is what were Cisco thinking, when they decided that client-id is going to be this kind of crazy stuff instead of plain MAC.

Some Cisco networking devices use a DHCP client identifier format that is different from the format used by networking devices running Cisco IOS release 12.4(1) or newer.
Ref link: http://www.cisco.com/en/US/partner/products/ps6441/products_configuration_guide_chapter09186a008054afa2.html
But, you should be able to bind that full (long) address to the the client IP in your DHCP pool configuration and I've done that before. If you are having problems refer to this link:
http://www.cisco.com/en/US/partner/products/ps6350/products_configuration_guide_chapter09186a008054addc.html#wp1204466
HTH
Sundar

Windows could not start the DHCP Client service on Local Computer, Error 2

Hi everyone,
I assign IP addresses via my router but today installed OpenVPN and it depends on the DHCP Client service. I checked in services and found it wasn't running. If I try starting it I get this message "Windows could not start the DHCP Client
service on Local Computer." "Error 2: The system cannot find the file specified.".
There's plenty of info out there about this issue but nothing seems to fix it for me. I've tried the following as an administrator,
"sfc /scannow" - It reported and error which it fixed but after a restart the problem persists.
"NET LOCALGROUP administrators "NT Authority\Local Service" /add"
"netsh winsock reset catalog"
I also checked that all dependencies of the DHCP Client service are working. I used "CMD /K
SC QC DHCP" to check the dependencies and compared them to an identical computer and they are. Hope someone can help. Thanks in advance.

Hi,
Did you mean after the restart the sfc /scannow command still could find the corrupted files?
Have you check this these related registry entries permission for your account?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp
permission needed: Query value, Create value, Enumerate Subkeys, Notify, Read Control
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Configurations
permission needed: Full Control, Read
for more information, read this article:
Some services do not start in Windows Vista and Windows 7
https://support.microsoft.com/kb/943996?wa=wsignin1.0
If the issue still cannot be resolved, I would like to suggest you use the recovery media to repair your computer.
Karen Hu
TechNet Community Support

WRT54G dhcp clients table missing linux boxes - only windows listed

I've searched the forum and similar messages and other routers mention that a firmware update will fix the problem where not all dhcp connections show up in the status/local networks/dhcp clients table.
I have WRT54G hardware version 6, firmware v 1.00.06.
I've looked at the firmware updates and no mention of this problem appears. I don't want to needlessly update my firmware.
Does anyone know if this problem has been fixed in the latest firmware?

More info:
It seems that the linux box (ubuntu 7.04) is using the bootp protocol, not full dhcp. From some reading of the rfc's it seems that dhcp is an enhancement to bootp, and it is valid for clients to request an ip address from a dhcp server (the protocols use the same ports etc.).
However, bootp does not deal with a lease and since the dhcp client tables list a lease time, I am guessing that this different way of getting an ip address is what is messing with the router.
On the one hand, it could be said that since it's not a full dhcp client, the router would be technically correct to not show it in the client list.
But, it does make for a bit of a messy situation as some clients can appear invisible to the network configuration manager. This could be a security issue.

Dhcp client configuration

Similar Messages

Maybe you are looking for