troubleshooting Question
VPN User Cannot Contact Voice Mail Server
asked on
I'm not too swift wtih my terminology, but here goes...
We've moved our voice and data traffic onto separate VLANs within our network. Our voice mail server (we have a ShoreTel system) along with all of our phone gear now resides on the 192.168.205.X/24 subnet.
All other devices are on a single subnet that ranges from 192.168.200.X -- 192.168.203.X.
We have a SonicWALL NSA 3500 as our firewall. Our VPN users come in through the SonicWALL and get a DHCP address (from our DHCP server, not the firewall) on our main subnet (above).
The problem we're now seeing is that our VPN users are unable to contact the voice mail server, and thus can no longer use their soft phones.
For example, one user connects via VPN and is assigned 192.168.202.40 as her IP address. The voice server is at 192.168.205.2. I need a way to enable communication between her and the voice server.
We have a static route set up on the SonicWALL that allows the regular LAN users to connect to the voice server just fine, but that does not seem to pertain to the VPN users, even though they are issued IP addresses within the same subnet.
That route is configured on the SonicWALL as follows:
Source: Any
Destination: 192.168.205.X Subnet (192.168.205.0 / 255.255.255.0)
Service: Any
Gateway: HP VLAN Switch (192.168.200.254 / 255.255.255.255)
Interface: X0 (this is our LAN)
As stated before, this route does the trick for devices that are on our LAN. But I'm missing something on the VPN side.
VPN users come in through the WAN, interface X1. Please let me know what additional information I can provide.
Any thoughts?
Thanks!
Jody
We've moved our voice and data traffic onto separate VLANs within our network. Our voice mail server (we have a ShoreTel system) along with all of our phone gear now resides on the 192.168.205.X/24 subnet.
All other devices are on a single subnet that ranges from 192.168.200.X -- 192.168.203.X.
We have a SonicWALL NSA 3500 as our firewall. Our VPN users come in through the SonicWALL and get a DHCP address (from our DHCP server, not the firewall) on our main subnet (above).
The problem we're now seeing is that our VPN users are unable to contact the voice mail server, and thus can no longer use their soft phones.
For example, one user connects via VPN and is assigned 192.168.202.40 as her IP address. The voice server is at 192.168.205.2. I need a way to enable communication between her and the voice server.
We have a static route set up on the SonicWALL that allows the regular LAN users to connect to the voice server just fine, but that does not seem to pertain to the VPN users, even though they are issued IP addresses within the same subnet.
That route is configured on the SonicWALL as follows:
Source: Any
Destination: 192.168.205.X Subnet (192.168.205.0 / 255.255.255.0)
Service: Any
Gateway: HP VLAN Switch (192.168.200.254 / 255.255.255.255)
Interface: X0 (this is our LAN)
As stated before, this route does the trick for devices that are on our LAN. But I'm missing something on the VPN side.
VPN users come in through the WAN, interface X1. Please let me know what additional information I can provide.
Any thoughts?
Thanks!
Jody
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 10 Comments.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 10 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.