About aeckensweiler

aeckensweiler · ‎02-14-2019

Hi there, Wondering what you have all done to get around this - I'm seeing quite a few users reporting that when they connect to their 9.0r3 client (and previous versions) Windows 10 classifies the connection as a Public network, no internal traffic is permitted (Outlook, internal resources etc). We are using split-tunneling, which I wonder may play a factor in - but if any of you have had this I'd like to hear how you were able to resolve it (if you have).

aeckensweiler · ‎02-14-2019

Hi there, If it's not available in your My.PulseSecure.net download portal you may need to ask PS support for the download. For me at least, if I extend the Recent Files view to 90 days I can still see 9.0R2.1 They're currently on 9.0r3 I believe. Hope that helps

aeckensweiler · ‎12-20-2018

I know this is kind of a stupid question - but is there anywhere I can find the minimum client supported by a specific PCS version? Currently I'm running 8.3R4, and I'd like to possibly move to 9.X track, however I don't know what version of Win/Mac PC Clients I should be raising them to. I'm trying to avoid user clients from having to force a client update upon connection when I update the appliance, by pushing out the update before hand via SCCM. Right now I'm split between 9.0R2.1 for my Win 10 and Mac clients, 5.3 R5.2 for Win 7 clients.

aeckensweiler · ‎11-15-2018

I've configuring IKEv2 to work with our Win10 and Win7 clients - first time dealing with IKE implementation, and I was wondering on the Certificates for machine Authentication. Should the client certificate CN contain the full FQDN (MyVPN.MyDomain.com) of the VPN appliance? or just the hostname (MyVPN) As for the internal and external port certificates - do these need to match the certificate that I want to use on the clients? I have the CA for client and server installed on both my clients, and my PCS - however the clients are still coming up with Authentication creds are unacceptable.

aeckensweiler · ‎10-15-2018

sweet - I'll wait for the client to be released (5.3R7), I do find that 9.0R2.1 is working well - no disabling of services upon connection

aeckensweiler · ‎10-09-2018

Nothing from the support guys as of yet - there is however a newer release 9.0R2.1 (im not deploying this track) which looks to address the missing wireless icon and networks. PRS-363544 Summary: DNS access may fail for 2 minutes when the VPN tunnel is created. PRS-368115 Summary: Users may not be able to change Wi-Fi networks from the system tray on Windows 10 <— please check this. I don’t understand why this was marked as a duplicate of PRS-363544. PRS-368112 Summary: The Wi-FI selector is not available on Windows 10. I'm going to try and deploy this to myself and see how it goes.

aeckensweiler · ‎09-21-2018

hey everyone, just an update on this. I reached out to the support team, and they informed me that they are aware of the issue and will be rolling out a fix shortly. the fix will essentially revert the NLA service restart functionality. We should be seeing PS 5.3.6.1 and 9.0.2.1 coming hopefully shortly, which "should" fix that issue.

aeckensweiler · ‎08-16-2018

I just recently pushed out an update to my clients running 5.3.5 to 5.3.6, and since then I've noticed that many of them are reporting mobile broadband (Cellular) connection drops when securing a connection. I then noticed that when connected to Wifi, it removes the available wireless networks from a Win 7 and Win 10 (1703) client. Further investigating i found that the Network List service (NetProFM) was switching to disabled - thus cutting off any wifi connections and cellular connections. I did see that in 5.3.6 PS introduced a fix to Domain profile assignment (https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB43776) which restarts the Network Location Awareness service- that the NLS is dependent on. Unfortunately this renders the VPN client essentially useless for my on the road sales and tech users, has anyone else found a way to supress this or stop the NLA/NLS services from shutting off? Right now the only fix I have is removing 5.3.6 and installing 5.3.5 Thanks!

Windows clients and Public network profile

Re: PS 5.3.6 and Network List service

PS Client updates post PCS update

Stupid IKEv2 Questions

Re: PS 5.3.6 and Network List service

Re: PS 5.3.6 and Network List service

Re: PS 5.3.6 and Network List service

PS 5.3.6 and Network List service