• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 935
  • Last Modified:

Cant ping remote subnet

Hi,

We are having an issue with connectivity between two subnets.

Subnet 1;

IP address: 172.16.1.0
Subnet mask: 255.255.0.0
Default gateway: 172.16.1.251

Subnet 2;

IP address 172.16.60.0
Subnet mask: 255.255.255.0
Default gateway: 172.16.60.1

There is a LAN-LAN VPN set up between the two routers at both subnets.

Some users / Servers are unable to ping machines on the other subnets.
0
Powerhousecomputing
Asked:
Powerhousecomputing
  • 2
  • 2
  • 2
  • +2
1 Solution
 
Ernie BeekCommented:
IP address: 172.16.1.0
Subnet mask: 255.255.0.0


Are you sure that subnet is ok? This means that subnet2 is a part of subnet1 which probably is the issue here.
I assume from subnet2 they are able to get to subnet1?
0
 
emilgasCommented:
are you sure your VPN is setup correctly?
First try to ping from one gateway (say 172.16.1.251) to the other one (172.16.60.1) if that works then you know the VPN is up and running but the internal routing is wrong inside the router. But if you can't ping the gateway then troubleshoot your VPN.

What kind of routers are these?
0
 
TheMakCommented:
are they trying to ping IP address or Machine name?
you can't ping Machine name but you can ping IP address of the subnet or you need to added common DNS for your local machines to ping remote machine.

Regards,
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Craig BeckCommented:
erniebeek has the answer!

Subnet1 hosts don't send data to the gateway to talk to hosts on Subnet2 as the subnet mask defines the IP range of subnet2 to overlap with subnet1.
You would need to implement a NAT solution to make this work without renumbering one of the subnets.
0
 
emilgasCommented:
I assumed the subnet mask of 255.255.0.0 was a typo
0
 
PowerhousecomputingAuthor Commented:
Thanks for your replies. I will look into what you have suggested and let you know if this is a solution.
I agree the subnet mask of 255.255.0.0 looks a bit odd. We have recently taken over support of this network, this was the way it was previously set up.
0
 
PowerhousecomputingAuthor Commented:
Subnet was the issue, this has been changed to the same on both subnets. The issue is now resolved. Thanks.
0
 
Ernie BeekCommented:
Glad I could help & Thx for the points :)
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now