Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

enter image description here

In the image above, we use the SonicWALL NSA 3500 at our gateway and handle VPN with its SSL-VPN. Our Layer 3 Cisco switch is our core network switch and handles about a dozen VLANs. Most VLANs are 192.168.x.x/24 variants, so the SonicWALL actually sees the rest of the network underneath it as 192.168.0.0/16 (we are "supernetting"). The Cisco does the actual routing (inter-VLAN routing).

But now I've created a VLAN on the Cisco of 10.200.200.x/24 where I have set up a XenServer. Both with and without the ACL (see image) applied, I can communicate just fine from my work PC but cannot ping the device from my Home PC through the VPN.

I have allowed 10.200.200.0/24 as a Client Route in the SSL-VPN settings, and attempted different routing table configs to get it to work, but have so far been unsuccessful.

How do I get communication between the SSL-VPN clients (192.168.203.x/24) and Cisco's VLAN 111 (10.200.200.x/24)?

Errors in picture: Called the server an ESXi host instead of XenServer host, and from Home PC it fails to XenServer, not to "Virtual Server."

share|improve this question
    
Can you ping your Work PC from the VPN? Also, can you show your routes and ACL's regarding 192.168.203.0 and 10.200.200.0 – David Houde Apr 5 '14 at 1:56
    
Yes I can ping the Work PC from Home PC. Can retrieve the ACL and route info tomorrow. – armani Apr 5 '14 at 5:03

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.