Why can't domain-joined computers ping non-domain joined ones on the same network?
Asked by
TechWizard42
I'm running into an issue where my domain-joined computer can't ping a non-domain joined laptop on the same network. To illustrate, I have a domain controller labeled DC-2 and a non-domain laptop termed laptop1 connected via DHCP. I can't ping laptop1 from DC-2. However, when I connect a different laptop (laptop2) that is domain-joined to the same network port as laptop1, I can ping it without any problems.
Interestingly, when I set a static IP on laptop1 using the same IP, subnet, gateway, and DNS it received from DHCP, then I can successfully ping it from DC-2. What could be causing this issue? Is it a firewall policy, a DNS misconfiguration, or something else?
Answers
If laptop1's network profile is 'public', then it's likely that ICMP is blocked on the firewall. You can verify the network profile settings and see if it's set to public or private, which impacts ping responses.
Reply to this answer
By default, non-domain PCs have their network profile set up in a way that they don't respond to ping/ICMP. This has been true for standalone Windows PCs since at least Windows 8. You can fix this by enabling network discovery in the settings.
Reply to this answer
It sounds like the network profiles might be causing the issue. Typically, non-domain PCs have stricter firewall rules, which could be blocking ICMP requests. Check the firewall settings on laptop1 to see if ICMP is allowed.
Reply to this answer
I remember that by default, Windows firewall does block ICMP on non-domain networks. Have you tried pinging laptop1 from another non-domain joined machine? If that still fails, you might need to adjust the Windows firewall settings on these devices.
Reply to this answer
Add your answer
Answers are reviewed before publication.
ExplorerExpert: Yeah, enabling network discovery is key here. This allows your device to be seen on the network, improving connectivity.