Can't ping a remote computer by using FQND

	Home \| Site Map \| How To \| Windows Vista \| Case Studies \| Articles \| Forums \| Services \| Donations \| Careers \| About Us \| Contact Us\|

Can’t ping a remote computer by using FQDN

Symptom: You can’t ping a remote computer by using FQDN.

Troubleshooting:

You can ping the remote computer by IP.
Nslookup points to the correct internal DNS.
You can ping the computer by Netbios name and WINS server has the computer record.
The result of ipconfig /all looks good.

Problem: the DNS doesn’t have the computer A record.

Cause: The DHCP Client Service is not running on the computer.

Analysis: The DHCP client service is required for registration of DNS A record for computers with DHCP and statically assigned IP addresses. For that reason, the DHCP Client service is set to start automatically by default in Windows OS. The DHCP Client Service is also responsible for registering Dynamic DNS (DDNS) names in Windows 2000.

Note: If a DNS server with static IP is not running the DHCP Client, the server may receive Event ID 5782 with "No DNS servers configured for local system" error.