Check KB28278: Support for OS X Mavericks (OS X v10.9) and Safari 7 as a client operating system and client browserSupport for OS X Mavericks (OS X v10.9) and Safari 7 as a client operating system and client browser   http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB28278 ... View more

Are you sure you did the following?   1. Java Applets blocked by default: On OSX 10.9 (Mavericks), Safari 7's default action for Java applets is to block them. This prevents Pulse, Host Checker and JSAM from launching when accessed via Safari (912652, 922721) To work around this problem, do the following steps: Use Safari to browse to the SA or IC. Log in and attempt to deploy Host Checker or JSAM. (this will not work). Open Safari Preferences, click the Security tab and choose "Manage Website Settings..." next to the Internet Plug-ins checkbox. Click on Java and find the SA/IC URL listed on the right columnChange the pulldown for that listing to "Run in unsafe mode"   Did you install JuniperSetupClientInstaller.dmg as a standalone application instead of letting it install with NC and/or JSAM via Safari browser?  If so, I would recommend removing the setup client and letting it install with NC or JSAM.  If your browser security settings are set properly it should work.       ... View more

You can also use the following URL to download the Juniper Setup Client directly from the device if the normal Web delivery method is not working.     https://<SA-Host-Name>/dana-cached/sc/JuniperSetupClientInstaller.exe     ... View more

Good to know about Windows 8 Home users.  We haven't tried replicating it with Windows 8 Home yet but I plan to next.   Are Windows 8 Home users seeing the problem with wired connections as well as wireless? ... View more

Chris,   I am a Juniper Technical Support Engineer and am aware of multiple customers reporting this issue with Windows 8, however, we have not been able to replicate the issue in-house, except over wireless when the signal is weak, which I believe is a false positive.  One thing that may be different about the Win 8 laptop we have tried replicating this with (using both Win 8 Pro and Win 8 Enterprise) is that it was not upgraded from a previous version of Windows as was posted by another user in this thread who seemed think this might be the problem.  Can you confirm if the same is true in your case?  Are these machines running Win 8 as a fresh install or have they been upgraded from a previous version of Windows?   Also, it is possible that this issue is not specifically a Juniper issue and that the problem exists in the Win 8 OS itself.  I have read some blogs about Win 8 users seeing this issue using the native built-in RDP client in Windows.  Can you test this to see if the native Win 8 RDP client exhibits the same disconnecting/reconnecting behavior as it does using the Juniper WTS client?   Thanks,   -Karen     ... View more

Actually, this does not guarantee 100% of the time that the system will use the native RDP client to launch the session. I'm having mixed results after further testing. It seems that if the ActiveX control with the Setup Client gets installed that we always try and download and install the Juniper Terminal Services Client without trying to launch the native RDP client and that it does work sometimes if you use Java as the fallback delivery method, but it is not consistent. I would have to test this further and have more consistent results before confirming that enabling the Remote Desktop Launcher actually invokes the native RDP client. You'd be better off using Network Connect to have it secure traffic to your remote desktops because then, you could launch mstsc.exe yourself and this would guarantee you'd be using the native RDP client every time. ... View more

If you enable "Remote Desktop Launcher" in the Terminal Services options on the user role, this enables an RDP browsing bar at the topmost section of the Terminal Services bookmarks in the User's Bookmark Page and if you launch your RDP sessions from this launcher by typing in the IP or host name of the host you are connecting to, the connection will be launched via the native mstsc.exe process instead of the Juniper Terminal Services client which is used for any Terminal Services bookmarks. Be sure that you have a Terminal Services Access Policy that allows access to multiple hosts, if necessary, by defining an ACL that allows access to all hosts in the entire subnet such as 192.168.0.0/24. ... View more

Just wanted to confirm what jbaustert already posted that the max number of drivers for the reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters is 14. ... View more

JTAC worked with another customer experiencing this same issue where Sophos Firewall client could not be installed in conjunction with JUNOS Pulse. Issue was occurring on Windows 7 32-bit with Sophos 10 and JUNOS Pulse 2.x. The symptoms of incomplete installation of JUNOS Pulse can show up in the Pulse client having no connections listed when it is launched. Pulse will appear to have been installed successfully but it's only the Pulse client UI that is getting successfully installed and the necessary services to run Pulse are missing. In C:\Windows\Temp\Sophos client firewall driverhelper log.txt we found an exception error when trying to install scfndis which reported NDISDriverInstaller::InstallDriver: Failed to instal SOPHOS_scfndis JUNOS Pulse also has several services that bind to NDIS drivers so it made sense that the problem could be related to the conflict between the two apps. Upon doing a search for this error on the Sophos Community Board we found an article that provided the cause and resolution for this issue. The article is at http://www.sophos.com/support/knowledgebase/article/113328.html and we were able to resolve the problem with the second resolution mentioned at the end of the article: increase the maximum number of network filter drivers allowed on the computer by editing the Windows registry. This option could be considered on virtual machines which may have many extra network filter drivers installed by the virtualization software. The registry key to edit is: HKLM/SYSTEM/CurrentControlSet/Cotnrol/Network/MaxNumFilters. We increased the NetworkMaxNumFilters from 8 to 16 and this resolved the issue. Sophos FW successfully installed with JUNOS Pulse. Hope this helps. ... View more

JTAC has had recent communications with OPSWAT regarding support for McAfee VirusScan v15 and they have confirmed that this has already been included in the OPSWAT package they will be releasing next Thursday which Juniper will then release with ESAP 1.7.4. ESAP 1.7.3 was just released last week and was posted to the support site yesterday, so I would look for ESAP 1.7.4 to be available the last week of July. ... View more

This sounds like a configuration issue on the SSL VPN device. From your description, it would appear that Split Tunneling mode is configured on the SA for your Network Connect access. Otherwise, all of the traffic would be forced through the NC tunnel and your browser would not detect your IP address as the one assigned to your local LAN adapter. It sounds like a configuration issue on the SA where you are getting assigned an IP address from a pool that cannot route traffic to the internal network's DNS servers. If Network Connect cannot ping the DNS servers that have been assigned to your connection then this will cause NC tunneled DNS queries to fail and since your ISP DNS servers cannot locate servers that are within the corporate network, you won't be able to access NC resources because the DNS is going to fail. I would let the helpdesk know specifically that the DNS servers being assigned for the Network Connect connection are not reachable. Maybe they need to assign a different IP address range, or specify different DNS servers. Also, they should check that the server you need access to via NC is defined in the Split Tunneling resource list as well as in the Network Connect ACL list in the Network Connect Connection Profile. ... View more

I'm not sure exactly what problem you are having with the Juniper TS client on Win 8.1 -- whether it's an install problem or a runtime problem, but found a post on: http://social.technet.microsoft.com/Forums/windows /en-US/2bc9615e-68ce-4660-b28e-1f5f6767e31f/vpn-ju ... With a possible solution: I could not use the existing on my 8.1 preview, so I uninstalled Juniper client in order to re-install. Tried to re-install without success multiple times. Upgraded to 8.1 RTM today. When I tried to re-install I found that I had to uncheck "Enable enhanced protected mode*) in Internet Explorer - Tools - Internet Options - Advanced (under "Security". After that, installation of 7.4.0  was like a walk in the park. Tested - WORKS! ... View more

Just learned that the this issue:   In Windows 8.1 not able to launch Windows/Citrix Terminal Services client via IE 11.0 with error "Your browser is not supported" will be fixed in 7.4R6 which is scheduled to be released on or around 10/31/13.  ... View more

You can manually remove the NC virtual adapter by uninstalling it from the Network Adapters in the Device Manager list through the Control Panel--or, if it is not visible here, then you can delete the dsNCAdapt.sys system file from the c:\windows\system32\drivers folder which would be the equivalent of removing it from the Device Manager. On IVE OS 5.5 and up, the virtual adapter is not removed from the client during the uninstallation of NC so you would need to manually delete it if you want to remove it from the machine altogether. ... View more

Does the user ever get connected successfully? Or do they always get the 23792 error when launching NC? Also, how long does it take from the time they actually start Network Connect for the error to pop-up. Is it immediate? Or does it take 20 seconds or so for the 23792 error to pop-up after NC appears to be attempting to establish the connection? Does the user get assigned the same role that other users are able to successfully connect with NC from? If so, you may want to set up a brand new test role with NC configured on it and map this user to this new role and configure a new NC resource policy and NC connection profile that is separate from other users to test whether or not it is a configuration issue or possible corruption in the role. If the user is able to connect with a different role then you may want to recreate the role for everyone. If you find that the user still gets the 23792 error after performing the above test then it might be a good idea to check the machine configuration against a Vista machine that works to see if you can detect anything obviously different. ... View more

There is also another way to achieve this task. You can use the IP restriction feature on the authentication policy of the role or realm to allow or deny users sign-in access based on their source IP address. Just browse to User Realms --> <realmName> --> Authentication Policy --> Source IP or User Roles --> <roleName> --> General --> Restrictions --> Source IP and add the IP addresses you want to allow or deny. Because you only have a small number of IP address that you need to allow or restrict access for, using this policy to do it would also be a good option since it would be easy to setup and maintain. I do not discourage the use of Host Checker, however. It's got some powerful capabilities and should not be overlooked. :) Karen ... View more