	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.7

How do I get my Watchguard VPN clients to see the two distinct networks attached to my trusted interfaces? They can only access the one.

Asked by GreatSlaveIT in Watchguard Firewall, Virtual Private Networking (VPN), IPSec Security Protocol

Tags: watchguard, vpn, ipsec, core, x750e, remote networks, access, subnet, trusted interface, gateway

Ok, here is the scenario...

I have a fully functioning IPSEC VPN on my Firebox Core x750e that has been working great for a couple years - However, I have now been tasked to connect our sister company's network to our network to streamline our IT services. Everything has worked out great so far - through a MAN connection, I was able to connect our sister company's network to an interface on the Firebox and set that interface as the default gateway for their network. Communication between the networks is working beautifully.

Now the key to finishing the job is to allow our VPN clients access to our sister company's network as well as our own. Currently when they log in, they can only see our 10.X.X.X network. Our sister company's network is 192.168.X.X.....

In the Policy Manager for the Firebox, I set the mobile vpn settings for IPSEC to allow access to 192.168.131.0/24 in the "Allowed Resources" area. Also, on the VPN client software (Watchguard Mobile VPN for IPSEC) I added the 192.168.131.0/24 network to the "Remote Networks" section of the profile. There seems to be something I am missing, because no matter what I do I can't ping any device on the 192.168.131.0 network.

At first I thought maybe it was a policy denying access, but I've tried seemingly everything to allow the traffic through. Interestingly, as I said, communication between the networks is fine when not connected through the VPN.

Please help! :)

View the Solution FREE for 30 Days

Related Solutions

Keywords: How do I get my Watchguard VPN clien…

	Title
1	VPN with WatchGuard
2	Watchguard Mobile VPN users connect…
3	Watchguard x5 VPN step by step
4	VPN connection to watchguard firewal…
5	Watchguard X550e
6	Manual VPNs with Firebox

Loading Advertisement...

20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. dpk_wal219,025
2. ljones_cna22,732
3. jmlamb12,700
4. RobWill6,000
5. arnold5,250
6. bzumwalt3,500
6. Rick_O_...3,500
8. Qlemo3,002
9. jodylemoine3,000
10. FrankThe...2,668
11. ahoffmann2,500
11. MikeKane2,500
13. ikalmar2,250
14. Mestha2,200
15. uetian17072,100
16. Gns2,000
16. htam2,000
16. SysExpert2,000
16. ged3252,000
16. Akhater2,000
16. Pber2,000
16. mutahir2,000
16. Bembi2,000
16. dalesit2,000
16. dpetr002,000
16. Sembee2,000
16. MrMander...2,000
16. aZLAn2...2,000
16. StephenJD2,000
16. quinnjudge2,000
16. itsmein2,000
16. SheaDigital2,000
16. ngailfus2,000
16. GTPD222,000
16. thaug2,000
16. hodgeyohn2,000
16. tdd972,000
16. andeporter2,000
16. bignewf2,000
16. Kaffiend2,000
16. blue-scr...2,000
16. thetmanvn2,000
16. EndureKona2,000
16. Phateon2,000
16. 172pilot...2,000
16. uayneb2,000
16. supermarko2,000

1. dpk_wal588,015
2. RobWill46,150
3. hstiles31,400
4. ljones_cna22,732
5. supportsoft15,550
6. jmlamb12,700
7. cv790...11,550
8. mcrossland10,272
9. Zenat10,200
10. bzumwalt10,000
11. arnold9,750
12. lrmoore8,565
13. Sembee8,500
14. fendermb48,175
15. tim_holman7,920
16. tmehmet7,850
17. samccarthy7,200
18. NetAdmin...6,552
19. giltjr6,250
20. keith_ala...6,000
20. MrHusy6,000
22. uetian17075,575
23. charan_j...5,000
24. from_exp4,975
25. Phil_Agc...4,750

How do I get my Watchguard VPN clients to see the two distinct networks attached to my trusted interfaces? They can only access the one.

Asked by GreatSlaveIT in Watchguard Firewall, Virtual Private Networking (VPN), IPSec Security Protocol

Tags: watchguard, vpn, ipsec, core, x750e, remote networks, access, subnet, trusted interface, gateway

About this solution