Article
Search
Shameless Plugs
Act Now!
Recent comments
Most Popular
Top Contributors
| User | Points |
|---|---|
| geoffc | 160,650 |
| dlythgoe | 21,925 |
| 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
4897
Solving Communications Problems with the GroupWise WebAccess Agent
Problem
A Forum reader recently asked:
"I am using SLES 10, eDirectory 8, ConsoleOne 1.3.6f, and GroupWise 7.01. I configured this for WebAccess, but when I tested with a browser (http://my_server_ip:8080/gw/) I could not log in to Web mail (the error said, "Unable communicate with GroupWise Web Access Agent"). How can I fix this problem"
And here's the response from Jim Michael ...
Solution
Try adding this to your webacc.cfg file, then restart Tomcat:
Provider.GWAP.Default.address.1=[private IP of webaccess agent]:7205
Also, if your WebAccess is running slowly, check your webacc.cfg file and look for a setting similar to this:
Provider.GWAP.Default.address.1=[some I address]:7205
Check to see if [some IP address] is a bad/old IP. It should be the IP of the WebAccess agent.
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
- 4897 reads
0