- Pulse Secure Community
- :
- About kita
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
10-26-2017
kita
Regular Contributor
208
Posts
31
Kudos
3
Solutions
12-04-2020
09:18:AM
What version of 8.1RX are you running. In general, I would advise upgrade to the latest patch version as previous versions of 8.1RX are vulnerable to the following security issue.
... View more
12-04-2020
09:12:AM
1 Kudo
Wow, this is very good feedback. I don't think this is documented anywhere, but I'll put this onto the forums for everyone else. Yes, the keep alive is handled by tcp port 443 which is a control channel while data is sent over UDP 4500. If there is a NAT involved, then it is likely the keep alive is responded by the NAT and never reaching the PCS device. If this is correct, then the PCS device has its own keep alive. The logic is the following: After 300 seconds (5 minutes), PCS will send a keep alive to the client. If not response is received it will send a keep alive every 75 seconds up to 9 times for a total of 675 seconds. If no response is received after 300 + 675 = 975 seconds, then the PCS device will drop the connection.
... View more
12-04-2020
08:57:AM
This sounds like the FQDN restore problem which has been reported to Pulse Secure. https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44429/ You'll want to check your DNS setting remaing the Tunnel DNS or not.
... View more
12-04-2020
08:50:AM
1 Kudo
Hello Raf,
This should be fine. You'll want to install the intermediate ca on the PCS device using the following steps:
https://docs.pulsesecure.net/WebHelp/PCS/8.3R1/Home.htm#PCS/PCS_AdminGuide_8.3/Importing_Intermediate_CA.htm?Highlight=intermediate%20certificate
Also, you can use a third-party site to check if the CA chain is proper after the installation using:
https://www.ssllabs.com/ssltest/
... View more
11-27-2020
08:34:AM
Yes, we are aware this problem is still occurring even with the latest Pulse Desktop Client. The current scenario is known and working towards a fix: End users disconnect the tunnel and the DNS setting should be restored properly. End users reboot or wake from sleep, then the DNS settings are changed to the VPN Tunnel DNS setting. We are still performing additional analysis of the issue, but it would be helpful to understand the steps taken by end-users when they see the problem.
... View more
11-21-2020
09:43:AM
1 Kudo
This should remain to work unless traffic enforcement is enabled on the device. There were recent changes in traffic enforcement from kernel extensions to system extensions in macOS. This was done as kernel extensions are no longer supported after macOS 11.0 and above. Check the debuglog.log and see if traffic enforcement is enabled: Enforcement IPV4=0 Enforcement IPV6=0 If it is set to 0x1, then it would be enabled and potentially blocking traffic that does not comply with the policy set by the admin.
... View more
11-20-2020
06:54:AM
This will depend on the configuration pushed by the administrator. The admin can enforce either full tunnel or split tunnel. If you are trying to reach a local subnet and it is going through the tunnel, it is likely enforced by the administrator to not allow access to the local subnet. To confirm this scenario, you can run a "route print" and see where the 192.168.1.x route is pointed to. If it is not mentioned, then it will fall under 0.0.0.0 which is likely pointed to the tunnel interface. If local subnet is required, then discussion with the admin would be needed to see if an exception can be made.
... View more
11-18-2020
06:05:AM
It is likely due to the administrator performing a compliance check for Big Sur OS. This has been reported to Pulse Secure and we are working on resolve this asap.
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44629
This would require some software changes by the admin. I would notify your admin or help desk to reach out to us on the recommend steps to resolve this issue.
... View more
11-18-2020
06:00:AM
The admin can disable manual connection by unchecking the option for "Allows user to create connections via the Pulse UI." This would be pushed down when the end user connects for the first time or via the preconfig.
... View more
11-17-2020
11:33:AM
The main changes in the later client is support for system extension for traffic enforcement. the previous release used kernel extension which is no longer supported in macOS 11.0 (big sur). Is the crashing happening on Catalina and below or Big Sur?
... View more
11-14-2020
08:31:AM
Could you please provide more details on the failure to install 9.1.9 on Big Sur?
... View more
01-31-2020
11:41:AM
Hello All,
We work very closely with Juniper Networks on compatibility with SRX. Please contact Juniper Networks to open a ticket to obtain the proper software version for the Pulse Desktop Client.
... View more
01-22-2020
09:36:AM
Thank you for your response. Pulse Mobile 9.0.1 will fix this issue and should be released soon as we are waiting for Apple to approve the app to the App Store.
... View more
01-08-2019
09:40:AM
1 Kudo
Thank you for the feedback. We are aware of the problem and working an a fix as quickly as possible. Once the fix is available, we will post information on the following thread.
... View more
12-26-2018
12:53:PM
Here is a list of supported AV with ESAP 3.3.4:
Windows OS
Antivirus Products
Bitdefender Internet Security (23.x)
ESET NOD32 Antivirus (12.x)
FireEye Endpoint Agent (27.x)
McAfee Total Protection (22.x)
PS-PROFILER McAfee Endpoint Security (10.x)
ウイルスバスター クラウド (15.x)
Antispyware Products
Bitdefender Internet Security (23.x)
ESET NOD32 Antivirus (12.x)
FireEye Endpoint Agent (27.x)
McAfee Total Protection (22.x)
PS-PROFILER McAfee Endpoint Security (10.x)
ウイルスバスター クラウド (15.x)
Bitdefender Internet Security (23.x)
McAfee Total Protection (22.x)
PS-PROFILER McAfee Endpoint Security (10.x)
HardDisk Encryption
Bitdefender Internet Security (23.x)
macOS
Antispyware Products
FireEye Endpoint Agent (27.x)
Antivirus Products
FireEye Endpoint Agent (27.x)
Release notes are available at the techpubs site.
... View more
12-26-2018
12:33:PM
For historical purpose, the issue was resolved with ESAP3.3.0.
https://www.pulsesecure.net/download/techpubs/current/1393/pulse-connect-secure/esap/3.3.x/ps-esap-3.3.0-supportedproducts-v4sdk.pdf
... View more
12-26-2018
12:29:PM
Hello Janar,
The SOH (Statement of Health) messages can be ignored. To get details about OPSWAT, you'll need to increase the log level to Detailed within the Pulse client. This should give more details in level 4 and 5 about the AV detected and the results.
Are you only detecting for Windows Defender?
... View more
12-26-2018
12:26:PM
Hello DrMudd,
The latest version of Pulse Desktop Client 9.0R3 is 64-bit compatible. From our understanding, Apple has not made any final decisions to block 32-bit client and providing the message as a warning to end users.
... View more
12-26-2018
12:23:PM
The log message is stating the captive portal feature is not enabled. This is not a critical error message but meant for troubleshooting for support.
The captive portal feature was built to ensure end users were properly notified to accept the agreement to public hotspot, hotels, etc before connecting with the Pulse client.
... View more
12-26-2018
12:21:PM
Hello Evan,
The issue was related to a bug in the drivers related to Pulse SAM connections. This issue should be resolved in Pulse Desktop Client 9.0R3.
... View more
12-26-2018
12:14:PM
If you are not able to find the file itself, you may be able to still run the command. Run the command to see if any output occurs:
sudo sysctl -a kern.ipc.maxsockbuf
It should output the value of 8388608. If not, try the following command:
sudo sysctl -w kern.ipc.maxsockbuf=8388608
... View more
11-30-2018
05:56:AM
Hello All,
Pulse Secure is aware of the problem state we are actively discussion potential solutions for the issue. If there are possible known workaround, we will share this as soon as possible.
... View more
11-20-2018
02:07:PM
Hello Dennis,
Thank you for the feedback. I was not aware of the following website, but taking a deeper look how it works is a very good idea.
We can provide this feedback to our product marketing team.
... View more
11-20-2018
02:04:PM
This seems very odd. If there was no valid certificate, then it should state "missing/invalid certificate" from the Pulse client. If you have other problems, please let us know as we can take a deeper look.
Overall, I am glad it is working again though :)
... View more
11-20-2018
01:59:PM
Hey Akuvar,
Could you provide a few lines before and after the log entry you are referring to?
... View more
11-20-2018
01:58:PM
Hello All,
Thank you for the feedback. We will provide this feedback back to the product teams about a compatibility matrix.
As a general rule of thumb, it will depend if the new feature has any server dependencies or not. In the case with the embedded browser, the option to turn on/off is dependent on the server. However, any supportability type issues like Windows 1803 or Mojave support (macOS) are mainly client-side components and you can simply upgrade the PSD client software without the need to upgrade the server (PCS) software.
For MAG hardware, 8.3RX will be the last software version. Pulse Secure will continue to provide "best-effort" for critical security patches until the end of the hardware.
... View more
11-20-2018
01:37:PM
Hello RossM,
Apologies for the confusion. Both KBs have been updated to properly state the fix is available in 8.3R5 and above. macOS10.13 is fully support in Pulse Connect Secure 8.3R3 and Pulse Secure Desktop client 5.3R3.
... View more
11-20-2018
01:32:PM
Hello Akuvar,
The pulse log (debuglog.log in C:\ProgramData\Pulse Secure\Logs directory) should give some information about where the connection if failing. It would either fail in two places:
Pulse client cannot make a successful tcp connection to the PCS device
Pulse client cannot make a successful ssl connection to the PCS device
If you see the following entry "Received server certificate", then you are getting past both scenarios as it is able to retrieve the device certificate.
... View more
10-26-2018
03:56:PM
Hello Mohandas,
Pulse Secure does offer terminal services connectivity through the web browser using the WTS (Windows Terminal Service) proxy. If you are clicking on a web link, you may see a prompt stating "Launching WTS".
If this is correct, then it is an active-x control which is proxying the RDP connection. Here is a short technical document about the feature:
https://docs.pulsesecure.net/WebHelp/PCS/8.3R1/Content/PCS/PCS_AdminGuide_8.3/Terminal_Services_Execution.htm
... View more
Kudos from
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
