Article
Suchen
Shameless Plugs
Recent comments
Most Popular
Top Contributors
| Benutzer | Points |
|---|---|
| geoffc | 161,300 |
| dlythgoe | 27,470 |
| mfaris01 | 19,630 |
| mbluteau | 19,240 |
| DamianMyerscough | 18,220 |
| aburgemeister | 17,805 |
| mbluteau2 | 16,505 |
| davesimons | 15,300 |
| gchilders | 12,540 |
| dgersic | 11,505 |
Who's online
Online users
User login
3151
Solving Login Errors with the Treo 680
Problem
A Forum reader recently asked:
"We have a user who has a Treo 680 Cingular. He is not using GMS, but uses Versamail and cradle sync with Nexic to access our network. He's using WebAccess also but can't log in now. He keeps getting a "login not current" error message. Is there a known fix for that login error?"
And here's the response from Jim Michael ...
Solution
The most likely reason for the "login not current" problem in WebAccess is that the Treo is going through a bank of HTTP proxies for browsing. When the client's IP address changes between requests, WebAccess gets confused.
1. Edit the webacc.cfg file.
2. Change "Security.UseClientIP.enabled=true" to "Security.UseClientIP.enabled=false".
3. Restart Tomcat.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 3151 reads
0