Nothing new from my ticket.  The support rep was unable to replicate the problem, and I don't have the time to un-install/re-install various versions of AVG to see where it starts to break down, so at this point my ticket will get closed/unresolved.   The only thing I was able to determine is that if you start with a clean slate as far as AVG is concerned, it seems to work..  My desktop had version AVG 8 to the present installed at some point and some of the remains of all those version were in the registry.  Once I removed all those registry entries and re-installed 2015 it worked just fine...  Too bad that's not something I can tell my end users to do...   -Stephen ... View more

OPSWAT maintains a list of supported Mac AVs at http://www.opswat.com/products/oesis-framework/supported-applications#!product=firewall&os=mac   Presence on the list does not necessarily mean that all APIs OPSWAT exposes for antivirus applications generally are implemented for each of the listed AV. ... View more

Not sure how you are completing the login through the Network Connect application as it expects to make a VPN tunnel; however, it is theoretically possible to work. what is the behavior you see when you connect through the browser on these failing machines? ... View more

Can you try reinstalling it again, before uninstalling? Sometimes that helps. ... View more

Hi Stephen,   Thanks for your update, I am gald that your issue resolved by changing the computer name in AD instance on one of the IC in cluster.   You can monitor the progress and revert for any issues   Regards, Kannan ... View more

HI Stephen,   Please refer http://kb.pulsesecure.net/KB17972 for the solution   The solution is to make sure that the option "Unwritten pages open in new window" is not checked for all the roles that the user is assigned to; this is configured under the Role > Web > Options > View Advanced Options.   Please mark this as an accepted solution if this resolves your query, a kudo woould be nice   Regards, Jay ... View more

You are welcome; thank you for the update. I am sorry it is not a perfect solution, by far, but at least you have something that allows successful access at this time. ... View more

@ruc wrote: I doubt that is the case as HC should allow any client with newer definitions than its own (it only blocks clients with older def versions).   Do you have a cluster? And does the issue start immediately after a virus definition download by one of the SA nodes and goes away after the subsequent virus definition  download?   The initial report was for when the client has newer versions of the definition files; it is resolved at the next definition update on the IVE. We have received reports of this in JTAC but have not been able to replicate ourselves for investigation to confirm which behavior is correct. ... View more

Hi, I must say I totally agree with rswinter. We were waiting for the official AD2008R2 support in UAC too long. I believe that majority of Junipers UAC installations are based on Windows domain environment so support for the latest Windows AD version is especially important. The retail availability of Windows Server 2008 R2 was October 2009. Juniper released the UAC 4.2R1 version on march 2012, so we had to wait 1.5 years. So it really took too long to solve this issue. We should wait no more than few months. Some features on NAC are critical, and I think the support for the latest Windows Server version should be amongst them. ... View more

We at OPSWAT are aware that consumption of OESIS Framework updates by Juniper (and other partners) for inclusion in Hostchecker features released to end customers can be painful for Juniper and for its customers.    We are committed to releasing OESIS more frequently (currently weekly, with a goal of daily updates by end of 2014) and to make it easier for Juniper to validate OESIS releases and incorporate into their packages.   In addition, OPSWAT recently released a configurable client, GEARS, which auto-updates OESIS and stores endpoint device compliance status in the Windows Registry or Mac OS p-list. The Host Checker can access and use this information through implementing either a (1) the  default Antivirus Rule or (2)  a  custom process / registry checks. A Hostchecker-GEARS configuration guide is posted at http://files.cdn.opswat.com/www.opswat.com/files/g ears-integration/integrate-juniper-ssl-vpn-opswat- ...   Using GEARS together with Hostchecker should reduce the number of issues you encounter with your end users being blocked due to their running an unrecognized endpoint security application. Attachments: integrate-juniper-ssl-vpn-opswat-gears.pdf ‏1003 KB ... View more

Yes, I have tried to both ways, with and without the Domain. to me, it does look like a version issue. In the TDP dump, I see the SA sending with XenDesktop 5.0 and the citrix servers responding with XenDesktop 5.1 Error. -S ... View more

Dear cbarcellos, I think I got the problem that look likes that you discuss here. logon with iPhone 4.3.2 works fine I push the same profile to the iPad and it doesn't work. every time i start the junos puls client I got enable - that's confusing. - not normally configuration is avalable and checked again and again error message on SA Box - no certificate error message on iPad missing certificate error message in logs from iPad - pppcontroller_sendmsg returns error -1 other messages in log thats confusing me info LoginManager::Redirected from https://ip_of_gw/dana-na/auth/url_7/login.cgi?realm=iPhone to https://194.191.40.5/dana-na/auth/url_7/welcome.cgi?p=no-cert why no-cert ??' Error>: VPN Controller: cannot find VPN Bundle 'net.juniper.sslvpn' for service = BF3B3DB8-196D-4C91-BFFD-FFF0E244787C <Error>: SCNC Controller::vpn_ipc_send cannot find plugin for net.juniper.sslvpn VPNConfigurationSendMessage failed for type 10: Error Domain=com.apple.SystemConfiguration Code=0 "The operation couldnt be completed what other steps could be helpful to find the problem Regards dirk If necessary I could provide you the whole log - it is i our lab ... View more

Did get it to work using the WSAM. It was a Java problem on the remote PC... Thanks. ... View more

Since the ProperJavaRDP is configured as a Web Application, I did not have anything in the TerminalServices configured, checking these two boxes didn't seem to help... -Stephen ... View more

As mentioned by @haas, this will need to be added to the ESAP definition file. To help make sure this gets done, I would recommend opening a JTAC case and provide the information requested by them in order to have this worked on/confirmed it is being looked at for adding to be supported. ... View more

Along with the IVE configurations given above, You can also try to extend the idle time out on the SSH client. It could be disconnecting because you do not have the keepalive setting enabled (this activity will keep the connection from timing out).   In Putty this is found under "Connection --> seconds between keepalives (0 to turn off)" set this to something around 45 seconds if you are being disconnected after 60 seconds. I've also seen this issue with certain firewall configurations too.   Hope this helps ... View more

Ok.. Thanks. The WYSE boxes we have are Citrix specific, not a real OS... We have tested with Embedded and WinCE and both worked Ok for RDP... ... View more

You cannot specify a host name for a Network Connect resource policy. You can only specify an IP address. Pls ref admin guide for "Resource Policy Components - page :_ 139" for more details. < please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus J thanks > ... View more

Thank you for the information on what is happening; unfortunately, it is not something I have heard of on that either. If you connect using the applet directly, rather than through the IVE, does the same thing happen? ... View more

That is correct, it is not a supported OS. It may be possible to have it work, depending on what you are trying, but there is no guaranteed support for it from Juniper (best effort may be possible, depending on the issue). Please see the supported platforms list for the OS you are using; for example here is the list for 7.0 Secure Access Supported Platforms. What item specifically was the user trying to use? ... View more

Our EX switches don't display this issue... ;-) ... View more

You can minimize the impact of this issue by having 2 different FQDN's like you indicated in your earlier post. ssl-vendor.companyX.com and ssl.companyX.com and to avoid the certificate warning you can associate the new FQDN with an IP on a Virtual port  ... View more

We've had a couple users test and it looks like 1.6.0 DOES fix the issue... ... View more