2

Hey guys I have a Problem.

I have no idea why but when I'm connected via VPN I'm not albe to connect to the LAN Servers in our Network. I can surf through the internet with the VPN but I'm not even able to Ping them... It's not a site to site VPN just normal Client To Network.

Did I forgot something? Do you need further information?

1st Pic VPN -> LAN 2nd Pic LAN -> VPN

VPN -> LAN Policies LAN -> VPN Policies

    netstat -r
Routing tables

Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
default            192.168.37.1       UGSc           26        0     en1
80.150.XXX.4       192.168.37.1       UGHS            0        0     en1
127                localhost          UCS             0        0     lo0
localhost          localhost          UH             14 35760176     lo0
169.254            link#5             UCS             0        0     en1
192.168.0.1        192.168.5.3        UH              1        2    ppp0
192.168.5          ppp0               USc             0        0    ppp0
192.168.37         link#5             UCS             1        0     en1
192.168.37.1       68:7f:74:1:d1:5d   UHLWIir        33      173     en1   1162
ersatzbook         localhost          UHS             0       25     lo0

NatPolicy

This is the VPN Access:

VPN Access

And here we can See the Address Object which is defined in the Firewall.

Address Object

After all that there are no changes in the connection to the LAN server. But still I'm not able to connect to them.

  • are you using ssl or vpn client to connect vpn? – Damon Nov 18 '14 at 3:42
  • I'm just using normal VPN with PreSharedKey, Username and Password. – gaRt3n Nov 18 '14 at 7:00
1

First, check if your client has correct routes. Asumming windows, execute route print in cmd. You should see a line containing a route for your LAN throught your VPN interface. Something like

192.168.10.0 (your lan) 255.255.255.0 192.168.10.200 (your VPN asigned IP)

Does this route exist on your client routing table?

In case not, your SonicWall fw is not passing correct network proposals in one of the phases of IPSec negotiation. There are an option where you can specify what networks can be accesible from your remote client.

This VPN allowed networks are not in the firewall rules, they are located in a tab called VPN Access in the user config, i mean the user you configured for VPN access. Check this URL for screenshots and a further explanation.

  • as above look at the Topic. – gaRt3n Nov 18 '14 at 12:01
  • I am in the LAN but i have no idea why I'm not able to ping for example Server 192.168.0.9 – gaRt3n Nov 18 '14 at 12:13
  • I am able to ping the SonicWALL on 192.168.0.1 – gaRt3n Nov 18 '14 at 12:56
  • Which is the IP assigned to your remote client? Maybe 192.168.5.3? – KorXo Nov 18 '14 at 16:57
  • Yeah that's the VPN-IP I got when I'm in the network – gaRt3n Nov 19 '14 at 7:27
0

Awww man.... I'm so ****. I found the issue... There was/is a setting in the VPN Client from MacOSX to put every network connection through the VPN... Now it routes everything through the VPN and I'm able to Ping and SSH the Server in LAN and DMZ. Arigatou Gozaimasu! Thanks Alot Every One!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.