topic users cannot authenticate with vpn client3.5 in Network Access Control

users cannot authenticate with vpn client3.5

rlew — Fri, 21 Feb 2020 17:58:40 GMT

we have w2k/nt network and using pix520 as vpn gateway. users have no problem connecting to pix and pinging hosts by name. but cannot authenticate on member servers except domain controller. any ideas?

Re: users cannot authenticate with vpn client3.5

avi — Thu, 17 Jan 2002 13:40:59 GMT

For the user name try typing DOMAINNAME\USERNAME

Re: users cannot authenticate with vpn client3.5

rlew — Tue, 22 Jan 2002 19:22:53 GMT

We have tried that and it doesn't work. VPN users never receive prompt for network authentication, I think this is the primary reason why the users cannot get access to the network resources.

Re: users cannot authenticate with vpn client3.5

abdul.kokumo — Tue, 30 Apr 2002 11:25:13 GMT

You may want to check the WINS the client are using. Also make sure that Client for Microsoft Networks are enabled on the NIC/PPP adapter which ever you are using for the connection.

Re: users cannot authenticate with vpn client3.5

hchebli — Wed, 10 Jul 2002 02:13:47 GMT

Hi rlew;

I am not sure if you have IAS on w2k running as your AAA server, but I am going to assume that you do.

there are 2 authentications that take place in establishing a VPN between the client and the PIX, the first phase is the group authentication which takes place on the pix, and the second phase is when the client gets prompted with username/password window which the AAA server use to authenticate.

If you are successful in the group authentication and you are not prompted with the client username/password window it is a setting on your PIX. Make sure you have the following command enabled on the PIX

"crypto map map-name client authentication tag-name"

If the first phase is not successful you need to check your group name and password settings on the PIX and your VPN client software.