Welcome, Guest. Please login or register.
Did you miss your activation email?
Friday 21 January 2022, 04:52:34 pm

Login with username, password and session length

Download the latest community FREE version  HERE
14143 Posts in 4323 Topics by 6270 Members
Latest Member: luizcarlosnery
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  VPN Support
| | |-+  Point to Point Cannot Access Certain Clients
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Point to Point Cannot Access Certain Clients  (Read 5403 times)
Full Member
Offline Offline

Posts: 12

« on: Wednesday 04 January 2012, 05:50:36 pm »

I have an openvpn bridged on green between two endian firewalls. One network set at vpn server) and the other client). Here is the scenario.

I have been able to get access to some computers from side I can access (,,

I do however have several that I can not access like,,

Any ideas on why I can access some but not the others? If I connect via the endian windows vpn client I can connect to all computer without a problem.

Hero Member
Offline Offline

Posts: 495

« Reply #1 on: Thursday 05 January 2012, 03:52:09 am »

Check backwards routing, check tracert from to the .20. subnet.
You must ensure that all computers are using the same routes, forward and backwards.

Also check
1-If windows machines, disable firewall for your tests. Check that you can ping the machines from their local subnet.
2-Check that all machines have their local EFW IP as gateway
3-On Endian Firewalls, check your VPN Firewall rules. Just create an ALL ALL rule to allow any traffic from the VPN tunnel, on both Endians. Mark log options, to track the traffic on live logs.
4-Open the live logs on both firewalls and analyze the traffic you see on the tunnel.

This should give you the answer to why you can't see all the machines.
Full Member
Offline Offline

Posts: 12

« Reply #2 on: Thursday 05 January 2012, 07:27:02 am »

I think I see the issue. When I tracert an IP that is working it goes strait to the IP address. > When I tracert on that isn't working it goes and stops at the gateway > 65.xx.xx.xx. 

So it seems like it isn't on the right gateway, but they all have the correct gateway address attached to them?

Any thoughts?
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.047 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com