About RD

RD · ‎06-12-2020

Hi, I have this same problem since last week for 3 of my users. I opened a new topic for that. https://community.pulsesecure.net/t5/Pulse-Connect-Secure/Pulse-hangs-on-waiting-to-connect/td-p/43143/jump-to/first-unread-message Please help if anyone got any idea about this.

RD · ‎06-12-2020

Hi, Yes this is possible. There are 3 things here to configure. 1. Configure a Scope on the DHCP service on a windows server. The scope should be in the same network as the PSA internal port IP. 2. In the PSA device under Users->Resource Policies->VPN Tunneling Connection Profiles you will find a default profile. In the DHCP Servers box enter the IP of the DHCP server where you configured the scope. 3. Most important is that you router/firewall should support and be configured for DHCP relay. That means when the request comes from the PSA Internal port the router should relay the DHCP request to the DHCP server. Check this in your router/firewall OEM support documentation.

RD · ‎06-12-2020

hi, Recently I have 3 users who are facing this issue. The Pulse Secure Connect Desktop client just simply gets stuck on the Waiting to Connect dialog. No error, nothing. If I do forget saved settings then the login box appears. After entering the credentials once it again stay in waiting to connect. Nothing happens. Client: Pulse Secure Desktop Client (various versions 9.0.1, 9.1.2 and even the latest version). OS: WIndows 10 Build 2004, 1903 and 1909. I have the Juniper SRX240 to which it connects and has xauth configured for AD authentication. This started suddenly. No config changes were made to the firewall. Tshooting steps tried: 1. Unsinstalling Pulse. Deleting residue folders of Pulse and Juniper from ProgramData, Program filesx86, user app data (local and roaming), deleted the jnpra files from system32\drivers also. Also manually removed registry entries on one system. No joy. 2. I upgraded 1 user from 1903 who was having this issue to 2004 build. It started working. But then stopped after a day with the same error. 3. Tried changing ISP (wifi, lan, mobile data hotspot). Nothing works. 4. Other user credentials also do not work. Same issue. That means its not a user related issue. That user can login to Pulse from another system. 5. If after clicking forget saved settings if the user enters his credentials incorrectly the Pulse client gives an error that credentials rejected by firewall. This means that the problem is post authentication. But I do not see any entries in the KMD-logs file on the firewall for the problem user or the IP of his system. 6. Also unisntalled and re-installed network drivers (LAN and wifi). Tried older drivers as well. No help. Can someone help in this? I know there are topics from 2017 in this forum but no solution yet.

Re: Pulse hangs on 'waiting to connect'

Re: PCS - DHCP Relay

Pulse hangs on waiting to connect