- Pulse Secure Community
- :
- About jjones
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
04-10-2020
10-05-2021
jjones
Occasional Contributor
8
Posts
0
Kudos
0
Solutions
01-11-2021
04:44:AM
Hello, I have a good working Pulse VPN client connection, good IP assignment 192.168.32.211, connection profile set to Search Client DNS first then Device, manual DNS setting 192.168.32.200, Policy applies to all role, No Proxy server. After successful connection my local network, I can connect to local resources (RDP, file shares, etc) successfully. However, I am unable to access the internet from my client device after connecting. I did create a Split Tunnel profile and input my local network subnet in the IPv4 resources section 192.168.32.0/24, selected Allow access. Still internet access does not work from local VPN client device. Works fine after I disconnect the Pulse VPN client. Any suggestions for how to get this working? I trying to start with having all internet traffic flow through the VPN connection. Thanks, jjones
... View more
04-30-2020
02:27:PM
Seems like I am getting disconnected from my VPN connection and Pulse Client every hour. Is there some kind of timer or something that I should look at on my Pulse server that controls this?
... View more
04-29-2020
09:36:AM
That was it! Thank you! I have not had a chance to find a good sucinct youtube video for setup.
... View more
04-24-2020
06:41:AM
Just checking if anyone may have a suggestion? I am getting connected from client, a good IP, same subnet, just can't ping anything or connect to anything. I am using the Pulse VM behind my Palo Alto firewall with a NAT rule that translates one of my external IPs to the internal IP assigned to the external interface on the Pulse VM (all ports open). Get's connected, get IP, but can't communicate from there.
... View more
04-20-2020
07:32:AM
Yea, it's on the same subnet, which makes me wonder why it's not working. It's getting a good IP correctly.
... View more
04-14-2020
09:16:AM
Hi folks, I have installed Pulse Secure (Hyper-V) VM. I joined it to my domain, created a connection profile (static IP pool and Manual DNS IP). I am connected using the Pulse client, receiving an IP address from the Pool successfully and the manual DNS IP. However, I can not ping (or communicate) to anything on my internal network. I've also created a Split Tunnel profile and included my internal IPv4 network id: 192.168.32.0/24. But still unable to communicate with anything. Any suggestions?
... View more
04-14-2020
05:54:AM
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?
... View more
04-10-2020
06:30:AM
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?
... View more
Latest Tags
No tags yet
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
