Cannot ping server name when connected to other VPN


  1. Posts : 4
    WIN/10
       #1

    Cannot ping server name when connected to other VPN


    I have a local server where the Server name is setup with the server IP address.
    I can ping the server name or the IP address from my Win/10 PC.
    I also connect to several other companies using a VPN connection.
    When I am connected to one of the VPNs, I can no longer ping to my server name, only my server IP Address.
    It tries to connect to the name of my server followed by a dot and another VPN connection name.
    I was told by the server group that this a Windows issue and must be in my DNS setting within Network sharing.
    Can anyone tell me what I need to do to resolve this?
      My Computer


  2. Posts : 8,057
    windows 10
       #2

    Welcome to the forum. Once connected to a VPN you are not on local network so you will have problems connecting unless you have port forwarding
      My Computer


  3. Posts : 4
    WIN/10
    Thread Starter
       #3

    Samuria said:
    Welcome to the forum. Once connected to a VPN you are not on local network so you will have problems connecting unless you have port forwarding
    I have Access to my router. I see the Port Forwarding Rules. What would I need to do?
      My Computer


  4. Posts : 9,765
    Mac OS Catalina
       #4

    It is most likely that the VPN server is blocking Ping requests or the Gateway is. Usually VPN's will not respond to a Ping, since you are encapsulating traffic inside packets that appear to the Gateway as transparent. Depending on what VPN Server software you are using or if using the Gateway to be the VPN server, along with what you are using for the connection.

    We do not want the devices behind the wall to respond to pings from a computer outside of the LAN that is connecting via a VPN connection. We want to define in the VPN software what devices or shares that only the outside user is only allowed to be given access to. If we do want a Ping to go through the VPN, we allow ICMP requests, which is not needed, unless you have a remote server using that IP ping as a way to give a Heartbeat keep alive or for WOL to make sure that the device we wish to wake up is actually still on the network with the Static IP assigned.

    Now if you are using RDP, VNC or Teamviewer, you really are not using a VPN. You are just making a remote connection.

    VPN types
    Remote Access VPN.Site – to – Site VPN.
    Internet Protocol Security or IPSec:
    Layer 2 Tunneling Protocol (L2TP):
    Point – to – Point Tunneling Protocol (PPTP):
    Secure Sockets Layer (SSL) and Transport Layer Security (TLS):
    OpenVPN:
    Secure Shell (SSH):
      My Computer


  5. Posts : 4
    WIN/10
    Thread Starter
       #5

    VPN


    bro67 said:
    It is most likely that the VPN server is blocking Ping requests or the Gateway is. Usually VPN's will not respond to a Ping, since you are encapsulating traffic inside packets that appear to the Gateway as transparent. Depending on what VPN Server software you are using or if using the Gateway to be the VPN server, along with what you are using for the connection.

    We do not want the devices behind the wall to respond to pings from a computer outside of the LAN that is connecting via a VPN connection. We want to define in the VPN software what devices or shares that only the outside user is only allowed to be given access to. If we do want a Ping to go through the VPN, we allow ICMP requests, which is not needed, unless you have a remote server using that IP ping as a way to give a Heartbeat keep alive or for WOL to make sure that the device we wish to wake up is actually still on the network with the Static IP assigned.

    Now if you are using RDP, VNC or Teamviewer, you really are not using a VPN. You are just making a remote connection.

    VPN types
    Remote Access VPN.Site – to – Site VPN.
    Internet Protocol Security or IPSec:
    Layer 2 Tunneling Protocol (L2TP):
    Point – to – Point Tunneling Protocol (PPTP):
    Secure Sockets Layer (SSL) and Transport Layer Security (TLS):
    OpenVPN:
    Secure Shell (SSH):
    I am using a VPN created in Win 10 Settings> Network and Internet > VPN
      My Computer


  6. Posts : 8,057
    windows 10
       #6

    Local PC don't use DNS they use NetBIOS that's why the name won't work
      My Computer


  7. Posts : 4
    WIN/10
    Thread Starter
       #7

    Name


    Samuria said:
    Local PC don't use DNS they use NetBIOS that's why the name won't work
    The name does work on my LAN except when I have a VPN connection to somewhere else.
      My Computer


  8. Posts : 9,765
    Mac OS Catalina
       #8

    entrack said:
    The name does work on my LAN except when I have a VPN connection to somewhere else.
    On a LAN it will use the DNS after the NetBios. In a VPN, Netbios is locked, because it requires a ICMP request. If you want to know more about VPN's and how they work, Microsoft's technet section has a lot of good information, so does Cisco's website and plenty of others that go over it. OpenVPN is now becoming the standard for doing any type of remote connection. That is because it is more secure and that it is cross platform capable.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:53.
Find Us




Windows 10 Forums