Only one of our CASes has SSO enabled - most of campus does not, but my office does. A few of the student Windows computers that come over to me for other problems (malware, hardware repairs, etc.) give the error "Invalid provider name" with a blank provider dropdown in the agent when I try to connect from my office. If I go for a walk, these machines connect fine when talking to a non-SSO CAS. When I come back to the SSO area, the first login attempt will work (though also showing the error), after a reboot, they're back to a blank dropdown and the error. The usual cause for "invalid provider" is two network connections active at once, but that is not the case for these.
For the moment, taking a walk so I know that they will be OK when they take the computer home has been good enough. But the weather isn't always pleasant for that, and more crucially, there is talk of enabling SSO on all CASes. Anybody know of any other causes/solutions to this one, before it becomes a crisis? Agent is 4.1.2.0, servers are 4.1.2. Client is WinXP SP2, at least the one I've got on hand now. Thanks, Anne -- Anne B. Pender Computing Support Analyst, Student Services Information Technology Services, Davidson College [EMAIL PROTECTED]
