Forum Replies Created
-
Posts
-
The immediate crisis is over, so thanks for your input. But as an FYI, That is the same document I have had all along.
We have a fix! added CAGAuthMethod=LDAP to the pnliteserver line, then discovered Citrix support had changed the plugin type to Java, which I changed back to Windows/Mac O/S- those two item fixed it!
Well, Scratch that idea – setup a new LDAP policy to use sAMAccountName, set the Website to accept it, got the same result: a web browser logon triggers the session policy and displays the config.xml, the thin client does not hit a session policy- I have 2 session polices bound, one is the REQ.HTTP.HEADER User-Agent CONTAINS WTOS/1.0 , the other is ns_true || ns_false, which should cover pretty much anything!
We are setup to support multiple AD domains, and the netscaler is configure to accept usernames in UPN format, do I need to set anything on the client side for that? I have been entering the user logon as a UPN
I started monitoring nsconmsg -d -g pol_hits – I never see the Wyse terminal hit a session policy – Logging in through a browser I do see the a session policy fire.
After entering logon, I do get a message “loading profile” that stays up for 10-15 seconds, then it changes to “Connecting” before I get the sign-on failed message.
if you mean http://www.freewysemonkeys.com/products/1000/NS105_and_ThinOS.pdf
I already had a copy.
One problem with it is that we are using Web Interface, not Storefront, and the document only addresses storefront. I am beginning to suspect that the WI config may be the issue – we are pulling the config.xml, but not connecting to the farm.
