One of my users got this (see pic) on an older client; a V10L (with firmware: 7.1_207). As a result the client is now “locked” and it can’t be used. I have never seen in before on any clients and I’m wondering why? Any suggestions – do you know whats happening…?
I believe there has to be another reason for this and neither of the above. I have a few thousand users with the same wnos.ini and this is the only one with this problem. The only “change” I’m aware of just before this occured, was a breach in the line(s)/cable in to the branch office. Any other suggestions?
Well, the reasons I’m not to sure about – I think maybe stranger things has happened in the “World Of Thin Clients :). In my wnos I have the Signon=No and the broker is browserip=aaa.bbb.no. Doing the checks you recommended tells me the same. As mentioned I have thousands using wnos with these settings and this is the only one with the SignOn prompt (I have not seen it before either). I still don’t know the answer to this but I have arranged with the user to have it shipped to me for further investigation.