We have a Symantec 200R Firewall/VPN Appliance and are having a lot of problems getting the VPN to talk to our network. We run our own dhcp server and so do not use the appliance built-in dhcp server.
Our environment is as follows:
External IP is a range of Class C addresses of which one has been assigned to the appliance. Internal IPs are 10.2.x.x with a class B subnet. Our servers and workstations are on 10.2.1.x and the VPN is at 10.2.254.100.
When making a tunnel connection you can ping 10.2.254.100 but nothing else on the 10.2.x.x network. For example, you can't ping 10.2.1.214. I have tried this with both RIP enabled and disabled. The firewall on this device is not used so that isn't a factor. It would be nice if you were able to ping from this device but unfortunately this feature has been left out of the design. Maybe next time.
Another weird configuration issue is that even though you tell the appliance to not enable dhcp it forces you to put in a range of addresses to serve out.
There are also some issues with the VPN Enterprise Client whereby if you install it on a Windows XP Pro workstation with Remote Desktop running then after the install you can no longer connect to this workstation using Remote Desktop client. It seems the VPN software disables Remote Desktop capabilities. Note that we are running 7.01 version of the VPN software.
Any ideas to resolve any of these issues would be very appreciated.
Thanks in advance for everyone's time.
Malcolm Copland
Network Support Specialist
PVNC Catholic District School Board
Our environment is as follows:
External IP is a range of Class C addresses of which one has been assigned to the appliance. Internal IPs are 10.2.x.x with a class B subnet. Our servers and workstations are on 10.2.1.x and the VPN is at 10.2.254.100.
When making a tunnel connection you can ping 10.2.254.100 but nothing else on the 10.2.x.x network. For example, you can't ping 10.2.1.214. I have tried this with both RIP enabled and disabled. The firewall on this device is not used so that isn't a factor. It would be nice if you were able to ping from this device but unfortunately this feature has been left out of the design. Maybe next time.
Another weird configuration issue is that even though you tell the appliance to not enable dhcp it forces you to put in a range of addresses to serve out.
There are also some issues with the VPN Enterprise Client whereby if you install it on a Windows XP Pro workstation with Remote Desktop running then after the install you can no longer connect to this workstation using Remote Desktop client. It seems the VPN software disables Remote Desktop capabilities. Note that we are running 7.01 version of the VPN software.
Any ideas to resolve any of these issues would be very appreciated.
Thanks in advance for everyone's time.
Malcolm Copland
Network Support Specialist
PVNC Catholic District School Board