Pulse not reachable after a while

Deadline
1

Hello,
we have a ongoing problem with Pulse for the last months. At first I thought it was network or server related, but we excluded all possible failures like firewalls etc.

If Pulse is started fresh everything is working fine. After a few hours it is not reachable anymore from the clients:

Connecting to render43...

RemoteLog: Will try to connect indirectly (using Pulse hostname, instead of IP address): SRV07

RemoteLog: Still-indirect? True. Connecting to machine 'SRV07' which resolved to 'correct IP here' port 5056

Making a connection to 'correct IP here' port 5056

RemoteLog exception: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. CorrectIPHere:5056

Remote command indirection is enabled, please ensure that your Primary Pulse is running and reachable.

Port is correct, same Problem if it is random or fixed port. Pulse is running on a Win Server 2016 VM only running Pulse atm. Redundant Pulse in physical machine same problem. Client Version is 10.1.19.4 Release (d9d0c59e3).

Restarting Pulse solves the problem for the next few hours.

Any ideas here?

Thank you,
sven

2

does it run out or RAM or disk after a while?

I recently had an oddity with Pulse when running a license forwarded (they use the same ports!) but it sounds like you’re just running pulse

3

I’m using now the Linux client for pulse and it seems to work now. Thank you

1 Like