Pulse Secure - New Install quick questions

[jjones]

Hi folks,

New to Pulse Secure, just installed my Pulse VM (Hyper-V) with an internal, external, and management IP.  All three IPs are internal range 192.168.32.211,212,213. 

I can login from the admin page (.211) using local admin user I defined during setup, but unable to login to the standard sign-in page with same admin user.  Says invalid username or password.  Why could that be?

After successfully logging into the admin page, I joined my domain successfully, made exceptions through my firewall for this external NIC IP (all ports open) and NAT a public IP to the external NIC IP (212).  

Now I try connecting with a valid domain user from the Pulse Client, right away it says credentials invalid, but getting the Error: 1319 Authenticaton rejected by server when I try again.  I can see authentication failure in the admin page and in the access log:

2020/04/10 07:24:34 - Primary authentication failed for jjones/System Local from 96.68.102.141

That .141 is the external IP I am connecting from.

Any thoughts to get me going?

[[email protected] · Accepted solution]

Hi @jjones,

You're trying to authenticate against the System Local database instead of Administrators database which is causing the auth. to fail when using your admin username and password to login to std. login URL /. To fix it, please navigate to Authentication >> Auth servers >> System Local >> Users >> Add and add the user account and try to login.

For the domain account login part, you need to change the Auth server used by the default users realm from system local to AD server, b ygoing to user realms >> users >> Authentication server list >> choose AD instance name >> save changes.

Thank you,

Ray.

[jjones]

Thank you!  I also had to create a connection profile and add my DHCP server.  I got connected with a user, got an IP from my DHCP server, but unable to communicate (or ping) anything on my network.  Still working on it.  

Any comments?

[[email protected]]

Is the IP address assigned to the user and Internal port IP address of the VPN server in same subnet? If not, please make sure there is routing in-place on the default gateway of the VPN server to return the user subnet traffic back to the Internal IP address of the VPN server.

[jjones]

Yea, it's on the same subnet, which makes me wonder why it's not working.

It's getting a good IP correctly.