Microsoft-Windows-Dhcp-Client-Even ts Error ID 1001
In my Windows Server 2008 R2 OS in the Event Viewer there is an error pertains as Microsoft-Windows-Dhcp-Client-Events Error ID 1001 states-(Your computer not assigned an address from the network (by the DHCP server) for the Network card with network address 0xC24620524153.The following error occurred:0x79.Your computer will continue to try an obtain an address on its own from the network address (DHCP) server). What is this error? And What is the remedy for this error?MumthazMuhsin
October 29th, 2011 7:05am

seems your server is trying to reach the dhcp server to get the ip adress but its not reachable
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2011 7:37am

Hello, please make sure that you have a DHCP server available in your network to give a DHCP IP address for your 2008 R2 server. If you have a DHCP server in another network then you can configure a DHCP relay agent to use it. More if you ask them here: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/threads This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer
October 29th, 2011 5:37pm

Hi, Identify and fix any network connectivity problems To resolve this issue, identify and fix any network connectivity problems between the‚ DHCP server and domain controller by doing the following: Determine if there is a network connectivity problem by using the ping command. Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem. To perform these tasks, refer to the following sections. Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command. To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. Determine if there is a network connectivity problem To determine if there is a network connectivity problem between the‚ DHCP‚ server and domain controller: At the DHCP server, click Start, click Run, type cmd, and then click OK. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the domain controller (for example, server1.contoso.com), and then press ENTER. If the ping was successful, you will receive a reply similar to the following: Reply from IP_address: bytes=32 time=3ms TTL=59 Reply from IP_address: bytes=32 time=20ms TTL=59 Reply from IP_address: bytes=32 time=3ms TTL=59 Reply from IP_address: bytes=32 time=6ms TTL=59 At the command prompt, type ping IP_address, where IP_address is the IP address of the domain controller, and then press ENTER. If you can successfully ping the domain controller by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution. If you cannot successfully ping the domain controller by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration. Perform additional troubleshooting steps The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem: Ping other computers on the network to help determine the extent of the network connectivity issue. If you can ping other servers but not the domain controller, try to ping the domain controller from another computer. If you cannot ping the domain controller from any computer, first ensure that the domain controller is running. If the domain controller is running, check the network settings on the domain controller. Check the TCP/IP settings on the local computer by doing the following: Click Start, click Run, type cmd, and then click OK. At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct. Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter. Type ping IP_address, where IP_address is the IP address assigned to the 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. Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers. If the domain controller is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware. In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK. Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling. Check firewall settings by using the Windows Firewall with Advanced Security snap-in. Check IPsec settings by using the IP Security Policy Management snap-in. For more information, please refer to the following Microsoft TechNet article: Event ID 1001 — DHCP Client Lease Validity http://technet.microsoft.com/en-us/library/dd380233(WS.10).aspx Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 31st, 2011 5:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics