Windows 10 - General failure when pinging my own IP (works for localhost)











up vote
-2
down vote

favorite












This is related to me trying to resolve problem from this question (Win10 - can't reach ubuntu VM after last big windows update (again :-/ )).



System: windows 10 pro.
Problem: pinging my own IP returnes general failure:



ipconfig:



Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.10.21.181
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.21.1


ping 10.10.21.181:



C:Userswojtek>ping 10.10.21.181

Pinging 10.10.21.181 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 10.10.21.181:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Does anybody has any idea what might be the reason? Or how to proceed in trying to resolve this?



[EDIT] - Resolved. The problem was some weird interaction between networking stack, virtualbox adapters and NordVPN/NordVPN TAP Driver. Everything was working fine together before last windows update and went belly up after that.



I have uninstalled NordVPN and related TAP driver, uninstalled network interfaces and let windows reinstall them after restart. Now it is working as expecting. I will now try to reinstall Nord VPN on top of it and see if it still works.










share|improve this question
























  • Please read Can I answer my own question? Then remove your solution from the question, post it as an answer.
    – Kamil Maciorowski
    Jun 13 at 9:05















up vote
-2
down vote

favorite












This is related to me trying to resolve problem from this question (Win10 - can't reach ubuntu VM after last big windows update (again :-/ )).



System: windows 10 pro.
Problem: pinging my own IP returnes general failure:



ipconfig:



Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.10.21.181
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.21.1


ping 10.10.21.181:



C:Userswojtek>ping 10.10.21.181

Pinging 10.10.21.181 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 10.10.21.181:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Does anybody has any idea what might be the reason? Or how to proceed in trying to resolve this?



[EDIT] - Resolved. The problem was some weird interaction between networking stack, virtualbox adapters and NordVPN/NordVPN TAP Driver. Everything was working fine together before last windows update and went belly up after that.



I have uninstalled NordVPN and related TAP driver, uninstalled network interfaces and let windows reinstall them after restart. Now it is working as expecting. I will now try to reinstall Nord VPN on top of it and see if it still works.










share|improve this question
























  • Please read Can I answer my own question? Then remove your solution from the question, post it as an answer.
    – Kamil Maciorowski
    Jun 13 at 9:05













up vote
-2
down vote

favorite









up vote
-2
down vote

favorite











This is related to me trying to resolve problem from this question (Win10 - can't reach ubuntu VM after last big windows update (again :-/ )).



System: windows 10 pro.
Problem: pinging my own IP returnes general failure:



ipconfig:



Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.10.21.181
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.21.1


ping 10.10.21.181:



C:Userswojtek>ping 10.10.21.181

Pinging 10.10.21.181 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 10.10.21.181:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Does anybody has any idea what might be the reason? Or how to proceed in trying to resolve this?



[EDIT] - Resolved. The problem was some weird interaction between networking stack, virtualbox adapters and NordVPN/NordVPN TAP Driver. Everything was working fine together before last windows update and went belly up after that.



I have uninstalled NordVPN and related TAP driver, uninstalled network interfaces and let windows reinstall them after restart. Now it is working as expecting. I will now try to reinstall Nord VPN on top of it and see if it still works.










share|improve this question















This is related to me trying to resolve problem from this question (Win10 - can't reach ubuntu VM after last big windows update (again :-/ )).



System: windows 10 pro.
Problem: pinging my own IP returnes general failure:



ipconfig:



Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 10.10.21.181
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.21.1


ping 10.10.21.181:



C:Userswojtek>ping 10.10.21.181

Pinging 10.10.21.181 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 10.10.21.181:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Does anybody has any idea what might be the reason? Or how to proceed in trying to resolve this?



[EDIT] - Resolved. The problem was some weird interaction between networking stack, virtualbox adapters and NordVPN/NordVPN TAP Driver. Everything was working fine together before last windows update and went belly up after that.



I have uninstalled NordVPN and related TAP driver, uninstalled network interfaces and let windows reinstall them after restart. Now it is working as expecting. I will now try to reinstall Nord VPN on top of it and see if it still works.







networking windows-10 ping






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 13 at 9:00

























asked Jun 13 at 8:40









wciesiel

12715




12715












  • Please read Can I answer my own question? Then remove your solution from the question, post it as an answer.
    – Kamil Maciorowski
    Jun 13 at 9:05


















  • Please read Can I answer my own question? Then remove your solution from the question, post it as an answer.
    – Kamil Maciorowski
    Jun 13 at 9:05
















Please read Can I answer my own question? Then remove your solution from the question, post it as an answer.
– Kamil Maciorowski
Jun 13 at 9:05




Please read Can I answer my own question? Then remove your solution from the question, post it as an answer.
– Kamil Maciorowski
Jun 13 at 9:05










1 Answer
1






active

oldest

votes

















up vote
0
down vote













You don't have to uninstall and reinstall NordVPN. There's a setting in the software that when turned on, makes your computer "invisible" to others on the network when connected to the VPN. Even though NordVPN wasn't running, it still had impact. The fix? Turn that setting off and you'll be able to see your network again.






share|improve this answer




















    protected by Community Nov 20 at 6:56



    Thank you for your interest in this question.
    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



    Would you like to answer one of these unanswered questions instead?














    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    You don't have to uninstall and reinstall NordVPN. There's a setting in the software that when turned on, makes your computer "invisible" to others on the network when connected to the VPN. Even though NordVPN wasn't running, it still had impact. The fix? Turn that setting off and you'll be able to see your network again.






    share|improve this answer

























      up vote
      0
      down vote













      You don't have to uninstall and reinstall NordVPN. There's a setting in the software that when turned on, makes your computer "invisible" to others on the network when connected to the VPN. Even though NordVPN wasn't running, it still had impact. The fix? Turn that setting off and you'll be able to see your network again.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        You don't have to uninstall and reinstall NordVPN. There's a setting in the software that when turned on, makes your computer "invisible" to others on the network when connected to the VPN. Even though NordVPN wasn't running, it still had impact. The fix? Turn that setting off and you'll be able to see your network again.






        share|improve this answer












        You don't have to uninstall and reinstall NordVPN. There's a setting in the software that when turned on, makes your computer "invisible" to others on the network when connected to the VPN. Even though NordVPN wasn't running, it still had impact. The fix? Turn that setting off and you'll be able to see your network again.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 18 at 13:32









        Glenn Colvin

        1




        1

















            protected by Community Nov 20 at 6:56



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?



            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            RAC Tourist Trophy