About Kath_

Kath_ · ‎06-09-2009

Hi, we tried to login to IVS1 with IE and login to IVS2 with FF, but no luck. We haven't tried with different browsers earlier. And I'm not 100% sure if it has ever worked... Regards Kath

KevinW_ · ‎05-28-2009

We run Wsam on 6.3r2 and works fine so far. No problems reported apart from a netbios share mapping issue. So looks like an issue with 6.4

mauriceben_ · ‎06-08-2010

Hi, I may be far in time, but the solution is the checkmark located in the JSAM policy to allow a new port to be added to the client if the client port (ie. 80) is being used. Thanks

Kath_ · ‎12-22-2008

Reason found! I actually missed an access policy for the web URL,, (uh, like the error says, -but I misunderstood it, as I though it was enough having the rewriting policy (passthrough) as this is the one that's auto-generated. When I added the policy under WEB ACL as well, it worked. Thanks for the input anyways.

Kath_ · ‎09-09-2008

JSAM cannot be used to tunnel data towards a Citrix farm that uses a csg-server. So this wasn't a bug or anything, but a matter of non-compatible configurations on Citrix vs Juniper

freddywo_ · ‎06-28-2010

thanks... the problem seem becoz of our AD server has been upgraded to windows 2008. We are using IVE 6.2 which not really support win 2008 server. We are planning to upgrade it to 6.4r1. http://kb.pulsesecure.net/index?page=content&id=KB11716&actp=search&searchid=1277362995149

Re: Problems with NC/WSAM on same node in cluster

Re: DNS problem using WSAM on Vista

Re: JSAM "cannot bind to localport=80"

Re: Exchange activesync - Access blocked after DNS...

Re: SSL err 59 when launching a Citrix app thru JS...

Re: "The server had an internal error" directly af...