Richard, We see that intermittently in our environment as well. Our issues usually happen after a WUT crash when the user attempts to log back in. We have found in most cases that the aruser executable is still running in the background of the person's machine and until you kill the process, attempting to login again returns the error saying the authentication has failed. Obviously, this may not be your issue but it's worth looking at. Thanks
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Richard Copits Sent: Thursday, June 09, 2011 4:00 PM To: [email protected] Subject: Remedy desktop client situation ** We have a strange situation where a user is using the "fat" client to access an AR Server on the network. They seem to be getting an error box that indicates that they are not able to be authenticated by the domain. Is there anything about the "fat"client that could cause it to fail on authentication to the server? They are able to do most anything else with other programs with no problem. We're on 7.x and it's an XP machine. ________________________________ Portions of this message may be confidential under an exemption to Ohio's public records law or under a legal privilege. If you have received this message in error or due to an unauthorized transmission or interception, please delete all copies from your system without disclosing, copying, or transmitting this message. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This email is subject to certain disclaimers, which may be reviewed via the following link. http://compass-usa.com/Pages/Disclaimer.aspx _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
