Share via

Windows 11 unable to ping server 2016

Anonymous
2025-02-22T21:37:07+00:00

Hi

My two windows 11 pro 64bit PCs are unable to ping to a sever MS 2016. However when trying to ping the same PCs from this server I get the correct response.

Oddly the same PCs are able to ping to any other PC on the local network and even to an old Server 2012.

I've already tried all the solutions from this page How to Remove the “Ping: Transmit Failed General Failure” Error Message — Auslogics Blog and enabled SMB 1.0 in the windows 11 PC which was given as alternative solution elsewhere.

Windows Server Networking

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-02-24T15:11:00+00:00

    Hello,

    Based on my understanding of the issue, I recommend you try the following steps to troubleshoot:

    1. Make sure that the firewall settings on both the Windows 11 PC and MS Server 2016 are not blocking ICMP (ping) requests. You can temporarily disable the firewall on the server for testing purposes to see if this resolves the issue.
    2. Check that they are both on the same subnet and are properly configured with the correct IP address, subnet mask, and default gateway.
    3. Check if there are any routing issues that could cause packet transmission from the Windows 11 PC to the MS Server 2016 to fail. This could include checking the routing table on the Windows 11 PC, which you can view by opening a command prompt and running route print.

    Windows Client for IT Pros and Windows Server forums are moving to Microsoft Q&A

    We’re transitioning to Microsoft Q&A for a more streamlined experience. Starting24 February*, new questions can only be posted on*Microsoft Q&A. Existing discussions will remain accessible here.

    From the26 Februarycustomers looking for support on Answers will be automatically redirected toMicrosoft Q&A.

    Best Regards

    Zunhui

    0 comments
  2. Anonymous
    2025-02-24T16:01:45+00:00

    Hi Zunhui

    Thank you.

    1. I've made sure of that.
    2. All checked and correct.
    3. The route print seems correct to me with active routes on IPv4 showing 'on-link' (although my level of expertise on this things is limited). Note sure If I should share that information publicly but could do so privately if you wish to see it.

    PS. I do not think the issue relates to it by I missed motioning that the Server 2016 is a VMware machine. And I think it is not related because the Server 2012 is also a VM machine with exact same settings within the same host PC (and 2012 works wit no issues).

    0 comments