VPN issue

I have three sites which are connected together using a firewall based IPSEC site to site VPN. I also have several machines which connect to a server using SSTP VPN for remote access. The issue is that the machines which are connecting using the SSTP VPN are only able to connect to machines on the local subnet of the server which they are connecting and not the other sites. I found a work around in adding a static route manually on machines; however these machines are out of my control and the users aren't exactly "tech savvy". If I try adding a route using the routing and remote access console I loose access to the network which the route relates to.

How can I overcome this?

Any help is greatly appreciated
Who is Participating?
kieran_stoneyConnect With a Mentor Author Commented:
Issue resolved by creating new scope for vpn clients and assigning static routes within it.
Not sure if this still applies on 2008, or if its been replaced by something else, but approach #2 is still an option.


Approach #2, DHCP configured static routes.
(look at the "static routes" section)
kieran_stoneyAuthor Commented:
Won't that cause an issue with dhcp clients on the local network not being able to access other sites?
WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

Depending on how your network is configured. If you need to worry about that then maybe configuring reservations is the way around that.
kieran_stoneyAuthor Commented:
I've done some research and came across using the default routing and remote access class within DHCP. However when I create the route using this it doesn't appear to be assigned to any machines.
Craig BeckCommented:
The routes specified in the RRAS class will only apply to the RRAS server - not the clients.  

Also, as I understand it, RRAS actually obtains the DHCP lease and kind-of proxies it to the client (for want of a better way of explaining it).  The client receives a /32 address from the RRAS server which was assigned to the RRAS server via DHCP, so any options from the DHCP scope won't actually reach the client over a VPN-established connection.
kieran_stoneyAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.