Forum Discussion

Copper Contributor

Oct 11, 2018

Solved

Windows Server 2016 is not pingable while it can ping other devices and have DNS problems

Hello Community, I have the following problem: On my VMWare vSphere ESXi 6.7 I have two Windows Server 2016 VMs. One (WDS-01) provides the AD, DNS and DHCP Server, the other one (WDS-02) should pr...

DNS

ping

Windows Server

Dave Patrick
Oct 15, 2018
On DC1 remove the router address listed for DNS and replace with 172.29.114.52, then do ipconfig /flushdns, ipconfig /registerdns, and reboot.

The ipconfig on "problemclient" is Ok.

The two ipconfig files you put up both have the same hostname? Which would be problematic.

For some reason root hints are IPv6 only. (would have expected IPv4)

As a work around you can add your ISP or other public DNS as forwarders. (remove router address here as well)

Dave Patrick

MVP

Oct 11, 2018

When NLA starts to detect the network location, the machine will contact the domain controller via port 389. If this detection successful, it will get the domain firewall profile (allowing for correct ports and IPv4 ICMP ping) and we cannot change the network location profile.
If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.

So I'd check the domain controller and problem client have the static address of DC listed for DNS and no others such as router or public DNS

If you needed further help then you can run;

Dcdiag /v /c /d /e /s:DCName >c:\dcdiag.log
(please replace DCName with your domain controller's netbios name)
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\problemclient.txt

then put files up on OneDrive and share a link.

Jonas Löffel

Copper Contributor

Oct 12, 2018

Okay, I've found out, that the Windows 7 Client is not able to receive network config from my DHCP, but when configured manualy using the DNS 172.29.114.52, it is able to connect to the internet.

Dave Patrick
MVP
Oct 15, 2018
On DC1 remove the router address listed for DNS and replace with 172.29.114.52, then do ipconfig /flushdns, ipconfig /registerdns, and reboot.

The ipconfig on "problemclient" is Ok.

The two ipconfig files you put up both have the same hostname? Which would be problematic.

For some reason root hints are IPv6 only. (would have expected IPv4)

As a work around you can add your ISP or other public DNS as forwarders. (remove router address here as well)
- Jonas Löffel
  Copper Contributor
  Oct 15, 2018
  Hello Dave,
  
  I allready changed the 2nd hostname, but thanks for the hint :)
  
  I removed the gateway IP Adress from the DNS config. Now the 2nd have connection to the internet, thank you very much :) I wish you a good day!
  - Dave Patrick
    MVP
    Oct 15, 2018
    Good news, you're welcome. (please don't forget to mark "best response" if my replies were helpful)
Dave Patrick
MVP
Oct 15, 2018
Jonas Löffel wrote:

Okay, I've found out, that the Windows 7 Client is not able to receive network config from my DHCP, but when configured manualy using the DNS 172.29.114.52, it is able to connect to the internet.

I'd check the system event log on DHCP server as the server has problems. (ran out of addresses)