Pulse Secure, now sold under the Ivanti Connect Secure name, is a corporate VPN client that staff use to reach a work network from home. When it stops passing traffic, the screen often still reads connected, which makes the fault hard to place. The steps below work through the local causes first, then point to the employer-side checks that only an IT team can complete.
When Pulse Secure shows connected but no internet, the cause is usually DNS, a stalled network adapter, or a full-tunnel routing rule rather than a broken link. Flush the DNS cache, disable and re-enable the adapter, confirm the tunnel type, and reinstall the client if needed. If those steps fail, the fault is often employer-side, so send the exact error to IT rather than guessing at more home settings.
Key Takeaways
- Pulse Secure is a corporate VPN, now sold as Ivanti Connect Secure, so a lasting fix often needs the employer IT team rather than home tinkering.
- A connected but no internet state usually points to DNS or a stalled network adapter, both of which reset in a few commands.
- Full-tunnel routing sends all traffic through the work network, so a slow or blocked site can be a policy choice rather than a fault.
- Flushing DNS, re-enabling the adapter, and reinstalling the client clear the majority of local Pulse Secure connection failures.
- A provider-wide or employer-side outage looks identical to a local fault, so confirming service status early saves wasted effort.
Confirm Whether the Fault Is Local or an Outage
Before changing any settings, rule out a problem that no amount of home troubleshooting will fix. Pulse Secure depends on a gateway that the employer runs, so if that gateway or the wider corporate network is down, every user fails at the same time. Check a work chat channel, an internal status page, or a colleague on the same VPN to see whether the outage is shared.
A fault at the home broadband level produces the same symptom, so confirm that ordinary sites load with the VPN switched off. If the internet only drops once the tunnel comes up, the connection is reaching the gateway but something in the session is broken, and the walkthrough on the internet not working after connecting to Pulse Secure covers that specific pattern in more detail.
Flush and Change the DNS Settings
A Pulse Secure session that reports connected but shows no internet is very often a DNS problem. The tunnel carries packets fine, but the device cannot turn site names into addresses, so pages hang or time out. On Windows, open Command Prompt as an administrator and run ipconfig /flushdns to clear the stale cache, then release and renew the address with ipconfig /release followed by ipconfig /renew. On macOS, the equivalent is sudo dscacheutil -flushcache.
If names still fail to resolve, set the adapter to a public resolver such as 1.1.1.1 or 8.8.8.8 as a test to prove whether DNS is the blocker. Restore the automatic setting once the work session ends so the corporate DNS rules apply again, because some internal resources only resolve through the employer's own servers.
Reset the Network Adapter
A stalled virtual adapter is the next most common cause. Pulse Secure installs its own network adapter, and it can hold a broken state even after the client says it has reconnected. Open Network Connections, find the Pulse Secure or Juniper adapter, disable it, wait a few seconds, then enable it again. Doing the same for the physical Wi-Fi or Ethernet adapter clears a wider set of faults where the underlying link itself has hung.
A full device restart achieves the same reset across every adapter at once and is worth trying when a single toggle does not restore traffic. It also clears the client processes cleanly, which matters when the application has been left running through sleep or a network change.
A work VPN client depends on both the tunnel and the local adapter behaving.
Rule Out Firewall and Antivirus Conflicts
Security software on the home device can block the parts of the connection the VPN needs. A firewall or antivirus suite that treats the Pulse Secure adapter as unknown may drop its traffic silently, which reads as connected but no internet. As a short diagnostic, disable third-party firewall or antivirus protection, test the connection, then switch it straight back on regardless of the result, since leaving protection off is not a fix.
If turning the software off restores traffic, the answer is a rule rather than a permanent exception: allow the Pulse Secure or Ivanti application through the firewall instead of disabling protection. On a managed work laptop this is often locked down, which is another reason the IT team may need to make the change centrally.
Full-Tunnel and Split-Tunnel Behaviour Shapes What Works
How the VPN routes traffic changes what a failure looks like. In full-tunnel mode, every request travels through the work network, so a blocked or slow site can be a deliberate policy rather than a fault, and general browsing may feel sluggish because it takes a longer path. In split-tunnel mode, only work traffic uses the tunnel while everything else goes straight out through the home connection.
That difference is a useful test. If a site fails while connected but loads the moment the VPN is off, the tunnel or its routing is the issue rather than the broadband. If a specific internal resource is the only thing failing, the problem is narrower and usually a policy or address matter. Only the IT team can change this routing, so the value in knowing the mode is deciding whether a blocked page is a bug to chase or a rule to accept.
Uninstall and Reinstall the Pulse Secure Client
When the settings look right but nothing connects, a clean reinstall clears corrupted files and leftover adapter entries that a simple restart leaves behind. Uninstall the client from Programs and Features on Windows or from the Applications folder on macOS, restart the device, then install the current version.
Because the product is now Ivanti Connect Secure, the newest build may carry Ivanti branding even where the saved login profile still reads Pulse Secure. Download it only from the employer's own portal or a link the IT team provides, never a third-party mirror, since a tampered VPN client is a serious security risk. Reapply the connection profile exactly as specified, because a wrong server address or realm stops the tunnel before it starts.
Contact the IT Administrator for a Corporate Client
Pulse Secure is enterprise software tied to one organisation's network, so several fixes sit entirely on the employer's side: expired certificates, changed gateway addresses, account or licence problems, and firewall rules all need administrator access. Once the local checks above are done, the fastest route is to send IT the exact error message, the client version number, and the steps already tried.
Pulse Secure exists to reach a specific work network, and no consumer product replaces that. If the need is personal secure browsing rather than corporate network access, a consumer VPN such as NordVPN is the more dependable tool for that separate job. That distinction also matters for privacy at home, where questions such as whether an ISP router can see your history sit entirely apart from the work VPN and are worth understanding on their own terms.