Pulse 5/SA 8.0 running on Windows 7. There are many users who have installed Pulse just fine but when they start Pulse it connects then almost immediately disconnects. The server logs show a successful connection with an IP assigned.
I found the following in the Pulse client log;
" netmon' IP address xxx.xxx.xxx.xxx is no longer present" (xxx.xxx.xxx.xxx is the user's local LAN IP address)
It's basically saying the users interface no longer has an IP assigned. Pulse then reconnects and then disconnects again. The same log message gets logged again, and this repeats itself over and over. It seems like something is shuttng down the users LAN interface everytime Pulse starts and sets up the virtual adapter.
Suppress wireless and route monitor are not enabled. Roaming sessions is enabled.
Anyone seen this before and have any ideas?
I've seen this behavior when Pulse has been deployed via SCCM deployment. This is due to multiple machines have the same machine guid. This value is expected to be unique per each device. You can confirm this by reviewing the user access logs and seeing if when one user logs out, another logs in and continues in a cycle. For more details about this issue, please refer to our kb article:
http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB25581
Thanks but it even occurs when only one person is on the VPN.