Cisco VPN problem

[GunsNRoses]

Hello All,

We are trying to configure our Cisco VPN client to allow for remote connectivity to our 3300 controller. The route statements appear to be correct in the VPN. We can ping the E2T, but can't ping the controller. Obviously, if we can't even ping the controller, we can't connect through ESM. Is there anything on the controller that possibly might not be configured correctly? I ask because we just changed the IP address scheme of the whole network, including the 3300 controller, E2T, etc. The Microsoft VPN works fine.

 

[paterson]

When you say that you can ping the E2T but not the controller, do you mean via the local network or the when you are using the VPN?

Is it possible that the controller IP was not changed or the change not enabled? You do have to reboot the machine after making that change.

To check, unplug the machine from the network and connect a laptop or PC directly to the 3300 LAN port and try the old IP address. You can also use this method to check the new IP address. If you can ping or connect to the ESM there, then the problem would be in your network.

 

[GunsNRoses]

I did reboot the controller after the IP address change. The IP address change had to take affect since I can connect to ESM on the local network. I can ping the E2T through the VPN client. Any more ideas?

 

[paterson]

The problem will most definitely be in your network or VPN setup. There are no settings that the 3300 will provide to help with a VPN connection. If you can get to the 3300 controller from the local network then the Mitel is good to go.

I do not know much about the Cisco VPN client, so I will not be much help with that. The only thing I would suggest is to check the settings/route statements for the entry for the E2T and duplicate it for the 3300 IP address. Other than that, you may want to try another forum for the Cisco VPN.

 

[GunsNRoses]

Thanks Paterson!