Solved

Unable to access the server via VPN unless on the same gateway

Posted on 2008-10-21
4
265 Views
Last Modified: 2010-04-02
Hi,

I believe this to be a very simple routing issue and I will attempt to explain.

We currently have two connections coming into the company the first is an ADSL the second is an SDSL, behind the connections are 2 Windows 2000 servers both acting as domain controllers

Connected to the SDSL is a sonicwall firewall, we have several site offices also with sonicwalls. Each with established hardware to hardware VPN connections.

The first server has an IP of 192.168.0.52
and the second server has an IP of 192.168.0.20
and they are both currently using the Gateway 192.168.0.1 which is the SDSL connected to the sonicwall.

As long as both servers are using the above Gateway the remote sites can see both servers with no problems,
what I need to do is set the second server to use a different Gateway i.e. the ADSL account, however when I do this, none of the site offices are able to see the second server.
0
Comment
Question by:jacass
  • 2
4 Comments
 

Expert Comment

by:Fess332
ID: 22767884
This is a routing issue, the LAN server see's all IP's not in your 192.168.0.x as not on its LAN so it goes out its gateway (192.168.0.1), if you know the IP address of the second location that goes out the ADSL connection you can set a route on the gateway (sonicwall) to use the ADSL route when it needs to go to that particular address range, So leave the gateway on the servers the same as they are now and tell the Gateway (sonicwall) that there is a different route to the other office ans to use the IP on the ADSL connection
0
 
LVL 1

Accepted Solution

by:
Novensiles earned 500 total points
ID: 22767960
On the second server set a default route so the remote VPN subnet uses the correct VPN gateway - VPN client communication will only happen via VPN gateway.

ie. assuming a remote subnet is 192.168.1.0/24 (modify as required for your remote subnet)
On server two, with default gw on ADSL IP

route -p add 192.168.1.0 mask 255.255.255.0 192.168.0.1

repeat for each remote subnet.
0
 

Author Comment

by:jacass
ID: 22768127
The second gateway is IP address 192.168.0.98

however I am by far a sonicwall expert would you be able to give me a little bit more information as to where in the sonicwall would I put this information?
0
 

Author Comment

by:jacass
ID: 22768801
Novensiles,

I did what u said and it worked a treat, thanks for that.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We sought a budget ($5,000) firewall solution that would provide all the performance we needed with no single point of failure.  Hosting a SAAS web application in our datacenter, it was critical that we find a way to keep connectivity up and inbound…
If you have a multi-homed DNS setup in windows, you can have issues with connectivity to the server that hosts the DNS services (or even member servers of your domain if this same DNS server is a DC). This is because windows registers all of its IPs…
Video by: Mark
This lesson goes over how to construct ordered and unordered lists and how to create hyperlinks.
Hi friends,  in this video  I'll show you how new windows 10 user can learn the using of windows 10. Thank you.

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now