Starting from 9.1R3, Pulse Client was removed since it's hardcoded as enabled, hence it should be working with PDC. Please provide the logs for review.
Pulse Client Logs:
1. Open Pulse Client.
2. File >> Logs >> Annotate >> "any-string"
3. File >> Logs >> Log level >> Detailed.
4. Replicate the issue.
5. File >> Logs >> Save as.
I've test this option on a Pulse 8.3R1 with Pulse Secure client, it's work.
But on the 9.1R4.1, it's doesn't work, I've have already the error message :
Error 53 - Network path not found, Interestingly it only happens with new version of PDC.
Can you please capture a TCP Dump on the VPN server with (if you know the IP address which will be assigned to user) or without filtering the client tunnel IP address and check the communiction between the client and file server?
Since the scipts would be copied while the connection status says "securing connection" on the pulse client, it would be difficult to capture the desired traffic on the client side.
I've make a tcmdum on the server without the ip client.
I see a lot of traffic but none to the server that contains the script
Are you using Full or Split tunneling? Can you please check the split tunnel and ACL policies and see if the traffic to the file server is permitted?
We don't use Split Tunneling on this role.
The IP server is 10.10.6.X and the ACL is 10.0.0.0/8:*
I've make a tcmdump on a Pulse 8.3R1, i've see the traffic to the server who is the script. The ACL / role, is the same. I've export the configuration.
@Mistouf Please open a support ticket with us to debug this issue further.
I had similar problem previously.
I removed my Pulse Secure programs completely. I login Pulse Secure Connect via webpage, and then start Pulse Secure Client. It will install Pulse Secure Applicatoin Launcher and Pulse Secure Client again (via online). And then, the session start script will be loaded without problem.
This worked for me. Not a very elegant solution, but a solution nonetheless.