Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1385
  • Last Modified:

Able to VPN to 193.x.x.x domain but unable to reach the 194.x.x.x domain

Hello,
    Please look at the following diagram. We have a VPN setup to the 193.168.0.1 box using that VPN we are able to access 193.168.0.87, 193.168.0.88 and other machines on the 193.x.x.x network. Unfortunatelly we are not able to access the 194.x.x.x network and that is our final goal. We can access the 194.x.x.x network by VPN into 193.168.0.1 box and then connecting to the 193.168.0.88 or .87 box.
   From 193.168.0.1 box we cannot ping the 194.x.x.x network and vice versa. From any other machine in the 193.x.x.x network we can get to the 194.x.x.x network and vice versa.
    If we connect 193.168.0.1 to the 194.x.x.x network and give it an 194.x.x.x IP address in addition to the 193.168.0.1 address then we can get there from 194.x.x.x but then the VPN goes no where and is unable to get to any machine either on the 193 or 194 network besides the 193.168.0.1....
   So we are trying to be able to VPN to the 193.168.0.1 machine and get to the 194.x.x.x network.
Any ideas of how to fix the issues please..
Thank you
Peter Chikov
OfficeNetwork.jpg
0
Epitel0920
Asked:
Epitel0920
1 Solution
 
arnoldCommented:
Here is a question, are the IPs you are using 193.168.x.x and 194.168.x.x or these are tpos and should reflect 192.168.x.x IPs?

It is not advisable to use Public IPs such as 193.x.x.x and 194.x.x.x as an Internal Nated IPs.
193 and 194 networks are assigned to RIPE (Europe)

How many routers/firewalls do you have? It seems you have?  Did you configure the firewall that has access to the 193.x.x.x and the 194.x.x.x to allow traffic from one to the other?  Is this firewall the default router for both segments?  If you have two firewall/routers, you need to specify a routing table on each to route the traffic to the other.

Post a netstat -rn from a system on each segment.
0
 
Epitel0920Author Commented:
Thank you
The problem was that the 193.168.0.1 server that I was VPN to was not on the same subnet as the rest of the 193.x.x.x machines(different netmask). So I reset the netmask to be the same in all cases,
Then I put a static route between 193.x,x,x and 194.x.x.x and that fixed it.
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

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