Event 1001, Dhcp – client

Asked By Asa Wilson 0 points N/A Posted on - 01/07/2012

Hi All,

In my home computer which has Windows 7. I get this error in the event logs.

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x544598479210.  The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

Can anyone help to solve.

Regards

• Status: Open
• Question Views: 3403
• Answer Count: 3
• Vote Up 0 Vote Down

• Answer Accepted: Yes
• Question Category: Networking

Best Answer by Hathy Brain

Go To Solution

Answered By Aristono Martin 20 points N/A #101193

Event 1001, Dhcp – client

It may help if you try to disable IPV6 for the network connection: To disable right click the Network Connection icon in the Notification Area > Open Network and Sharing Center > Click on "Change Adapter Settings" on the left hand pane > Right click on your Network connection(If you are using LAN Cable, it should be called Local Area Connection) > Properties > Uncheck the box under "The Connection Uses the following items:" that says Internet Protocol Version 6 > Click OK. If there are some more connections who have the same error try to do the same steps as above.

You may also try to change from DHCP to Static IP and disabling the firewall.

About Aristono Martin

Questions
3

Answers
370

Best Answers
53

• Vote Up 0 Vote Down

• Posted on - 01/07/2012
• Question Category: Networking

Best Answer

Best Answer

Answered By Hathy Brain 0 points N/A #101194

Event 1001, Dhcp – client

Hi!

 

It is either due to network connectivity between your domain controller, server and DHCP or it is due to router, maybe it does not support IPv6.

 

Try to ping all three of them at the DHCP server. Run the command prompt by typing ping [server_FQDN] wherein FQDN is your fully qualified domain name of the domain controller. If you successfully ping the domain controller by IP address but not by FQDN, this could be an issue with DNS host name resolution. If you cannot ping the domain controller by IP address, it could possibly there is an issue in your network connectivity or IPsec configuration. 

Try to ping your localhost, if it is unsuccessful it may indicate a corrupt TCP/IP stack. 

Try to ping your IP address [the one assigned in your computer], if you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.

Try to ping your DNS_server, if the ping is unsuccessful again, it indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.

 

If you already verified all networks are operating properly then it may be an issue with your router, not supporting IPv6. Disabling IPv6 for your current network adapter might keep the error from showing up in the Event Viewer. Go to Network and Sharing Center – Change adapter settings then Right click on said network adapter – Properties – Uncheck 'Internet Protocol Version 6 (TCP/IPv6)' and then OK.

 

Hope this helps!

About Hathy Brain

Questions
1

Answers
16

Best Answers
4

• Vote Up 0 Vote Down

• Posted on - 01/07/2012
• Question Category: Networking

Answered By nkosana 0 points N/A #101195

Event 1001, Dhcp – client

You should reset TCP/IP manually, this will help you solve the problem. You can find the reset command in the Nutshell's utility IP context (https://support.microsoft.com/en-us). To achieve this,

 

Please follow these instructions:

 

1. Open command prompt. There are two ways to this: Go to Start menu – Accessories – and select Command prompt; or click Start menu – choose Run – type in Cmd – press Ok or Enter.

 

2. Type, or copy paste this text in Command prompt: Netsh int ip reset c:resetlog.txt and press Enter. The other way to do this without specifying the directory where the log file is saved is to use this command: Netsh in ip reset resetlog.txt

 

3. Reboot your computer. With this command you get the same result as removing and reinstalling the protocol, because it rewrites both of the registry keys used by TCP/IP. These are the two registry keys that will be rewritten after using reset command:

 

1. SYSTEMCurrentControlSetServicesTcpipParameters

2. SYSTEMCurrentControlSetServicesDHCPParameters

 

 

About nkosana

Questions
2

Answers
1

Best Answers
0

• Vote Up 0 Vote Down

• Posted on - 01/09/2012
• Question Category: Networking