AOL 7 causes failure in WebAccess 1

[1oldfoxman]

Remote users using AOL v7.0 cannot get beyond the login screen of WebAccess. Instead of displaying the mailbox screen, it flips back to the login. We're running GW6 and just upgraded to WebAccess6. I've seen references to security settings in an earlier post. Does anybody know of the details of a fix for this?

 

[donnadee]

Here's what I found on the Novell website.

Althought the AOL client is not a supported browser for WebAccess, the following procedure has worked for some customers:

1. On the server with the web server edit SYS:\NOVELL\WEBACCESS\WEBACC.CFG.
2. Change the line Security.UseClientIP.enable=true to Security.UseClientIP.enable=false.
3. Restart the WebAccess and web server.

Another solution that works just as well and doesn't compromise the security settings as listed above, is to connect using AOL, then minimize the AOL portal or browser window. Then launch a copy of Internet Explorer and browse to Web Access using this new browser window. This should allow the user to login without any errors.

 

[1oldfoxman]

The IE session idea works fine, although it's less than ideal for users to understand/remember. Network managers don't like the idea of turning off that security feature so I'm teaching users to open the IE session after connecting via AOL.

Thanks for your help. If anyone else has other ideas, I'm still open to other thoughts.

 

[FarOut]

I was told by another GW admin that the AOL 7.x Client, sent out on CD, had some type of corruption to it. And by downloading it from AOL seemed to fix the problem for a majority of her AOL users. I can not validate this as being true or not. I like probably many others have my end-users logging into AOL like they are accustom to, and then having them use either Netscape or IE to access the GW WebAccess Servers. Like I said I don't know if this is true or belongs with the other Urban Legends. I will probably test AOL's new 8.0 Client to see if the problem persists.

I do remember though that AOL was stating that the problem was solely a Novell issue. This was relayed to me by more than one of my customers after they had contacted AOL when we were first investigating the problem. Just another reason to not recommend AOL. I do know that they lost quite a few subcriptions due to this, just from our GW users. FarOut
V-Peace-V