2

This often happens and it kind of solves itself after a while or after reboots. But I would like to stop relying on luck and understand why one server can ping the other but not the other way around.

Notice that neither pings were working before one of them started working

enter image description here

Edit: Just to add more information, the server that is not able to ping the other is a AD controller server. The other one is a regular windows server 2019 without anything on it.

RollRoll
  • 467
  • 3
  • 8
  • 19
  • The server which cannot ping has the wrong DNS Server. Unless it’s a DNS server itself, it won’t be able to resolve anything that isn’t in the hosts file, since it’s DNS Server is configured to 127.0.0.1 – Ramhound Mar 19 '22 at 20:11
  • 1
    @ramhound except the pings were to IP addresses, so no DNS resolution is required. – davidgo Mar 19 '22 at 20:15
  • @davidgo replied before I could, yes there is no DNS for those servers only IP so no DNS work is required here I think. – RollRoll Mar 19 '22 at 20:15
  • I tried adding to the host file anyway, the IP with the computer names, the behavior persists – RollRoll Mar 19 '22 at 20:21
  • 1
    I am still suspicious of the DNS server being 127.0.0.1 is that intentional? – Ramhound Mar 19 '22 at 21:14

1 Answers1

0

The Windows Server 2019 might block inbound pings:

  • Run : Windows Defender Firewall with Advanced Security
  • On the left pane click Inbound Rules
  • Click the Name column to sort the rules for easier access
  • Find the two rules titled "File and Printer Sharing (Echo Request - ICMPv4-In)", right-click each rule and choose "Enable Rule".

This should enable ping to this server.

harrymc
  • 455,459
  • 31
  • 526
  • 924