![]() ![]() User-SRXGateway: run show chassis routing-engineĬPU temperature 59 degrees C / 138 degrees F Next, we will show the Juniper commands the JTAC engineer ran on the SRX in config mode Juniper's JTAC team investigated the SRX300 Gateway, where Pulse Secure VPN client suppose to connect, while the VPN connectivity was failing and found out that it was caused by an over-utilization of its Routing Engine. To the best of your knowledge should we dismiss this as a Pulse Secure related issue and focus on the SRX or Pulse Secure client may be also part of it ? We called Pulse Secure tech support but the moment we tell them we're VPN out to a Juniper hardware product they immediately point us to Juniper tech support. We are actively troubleshooting the problem on the Juniper side but we would like to bounce this issue to Pulse Secure Community, just in case someone else has experienced something similar and has an advise/ recommendation how to resolve it. When we restart the SRX gateway error 1453 goes away but it comes back about 12-15 hrs later. ![]() ![]() We downloaded a copy of it from Pulse Secure's site and we use it with a license that comes by default with the purchase of an SRX 300. The Pulse secure VPN client installed on the Win10 machines is v. Our desktops/laptops are running Win (OS Build 17134.590). We're newcomers in the Pulse Secure/Juniper Community and technology as well seeking assistance for a resolution of a problem summarized in the subject of this post. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |