VPN 3005 Concentrator - IP assignment issue

[nicademuskgd]

I have a strange issue with the VPN Concentrator 3005. I have the Private interface configured with 192.168.3.3/24 as the ip address. For any users I either assign an ip address from the same network 192.168.3.105/24 (for example) or use a ip address pool (192.168.3.100 - 192.168.3.150) the connection will fail and the concentrator will state that it cannot assign an ip address to the client.

However, if I configure the address pool or client user to a different subnet it works and the user get's connected. For example, 192.168.2.105/24. I have the back end hitting a switch and don't really want to have to add a router to talk between subnets.

Am I missing something?

Any help is appreciated!

[ajagadee · Accepted solution]

Alan,

It is recommended that you assign a different pool of IP Addresses for the VPN clients than your internal network.

Eventhough it is not recommended, You should be able to assign an IP Address Pool which is part of the same internal network and this should work. The only thing you have to be aware of is that this range of IP addresses assigned to the clients should not be used on the internal network

Can you post the logs from the VPN3000 when its not able to assign an IP Address to the VPN Client.

Let me know if it helps.

Regards,

Arul

** Please rate all helpful posts **

[nicademuskgd]

I was able to get the ip addressing fixed by changing the private address and the pool to a new subnet. For some reason this works. As you stated this is not going to my internal network, but to a DMZ which is filtered by a Pix Firewall.

Thanks for your help though.

Alan