ip pool problem

[cammy]

Hi

We have recently found that new machines running cisco vpn client have not been able to get an ip address from the 506E (unlimited users). Existing machines which have previously connected have no problems.

The new machines can connect and authenticate ok but fail at the stage when the virtual adapter would come to life and an ip is issued.

We extended the ip pool range to rule out a lack of ip addresses but the PIX is still logging the following for new machines:

404101: ISAKMP Failed to allocate address for client from pool.

Has anyone come across this before?

Cheers

Cammy

 

[NetworkGhost]

What version of code for client and PIX?

http://www.wr-mem.com

 

[cammy]

Hi

I've discovered that it's a profile issue in the VPN client. Profiles which don't work include the line relating to ISP dial up which must be added automatically when you create a new profile:

ISPPhonebook=C:\Documents and Settings\All Users\Application Data\Microsoft\Network\Connections\Pbk\rasphone.pbk

After removing the C:\Documents and Settings\All Users\Application Data\Microsoft\Network\Connections\Pbk\rasphone.pbk part and restarting the cisco vpn service I was able to get an ip address and the connection worked.

This was happening for us on new Dell Laptops with a 3G mobile broadband card in them.

Cheers

Cammy