Cisco ASA anyconnect 2nd connection profile not using correct DHCPpool

[Havensteder]

Hi im hoping someone can give me the golden tip to where im going wrong.

I have a existing and working anyconnect connection profile but i want to expand on this with a extra support profile. I have got so far that the clients are making a connection with there own new anyconnect profile but they are still using the default IP Pool. I have defined in the anyconnect connection profile to use the new IP pool but the clients are still receiving a IP from the existing pool.

Any tips are welcome

[Havensteder · Accepted solution]

Problem has been resolved 

[Mohammed al Baqari]

Hi,

Check from ASA a connected client to see which tunnel-group/group-policy is
used (show webvpn anyconnect username). Ensure that this policy is having
the right pool. If you are landing at the wrong group, check your
configuration for anyconnect profile.

**** please remember to rate useful posts