Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WebAccess Slow Logon/no logon 2

Status
Not open for further replies.

Breezeman

IS-IT--Management
Dec 12, 2001
125
US
Recently I have installed Webaccess on my Novell 5.1 mail server. I am running the agent on this box and running the servlets on a Win2000 server. I am now faced with a very slow log on to Webaccess with a strong connection (T-1,cablemodem,etc) or not connecting at all with 56k modems especially when user is on AOL. The Tid that I always end up going back to says "go to NWADMIN and check the timeout on the servlet". Here is the problem, since the servlets are running on the Win2000 server NWADMIN does not contain this tab. I can find nowhere where Novell addresses this issue. Does the cfg file on the Web server allow the timeout change and effectively allowing the 56k user to attach, if so what is the max time reccomended. Any help is appreciated.
 
Personaly I avoid using M$ boxes for WebAccess, unless I have no other choice.

So you have the servlet (Novell's servlet right?) running on the Win2k box and the GWINTER running on the NetWare box? If this is so, use the NT GWINTER; but I don't think the install gives you the option so I will assume you have GWINTER running as a service on your Win2k box.

Do you have the current NetWare client installed?
What version of 2k? (Server or Advanced server)
What version of GroupWise?

I have setup the WebAccess for GroupWise 6 a few times on Win boxes that got dumped on me. I have always installed DS and given the server a R/W copy of the repica my mail users reside in. I only did it this way because in both installs I did, I needed to have users authenitcate to the local system instead of going across the wire (which could be the cause of your speed issue). Also in both cases the customer did not want to buy a NetWare runtime (I also like to keep GWIA and GWINTER off of the MTA and POA servers, helps dramaticly in large enviroments). Netware 6 changes the licensing rules, so I don't have to deel with the M$ IIS boxes anymore.

For 5.1, a run time usually runs for about $300. This only gives you two user connections, but thats all you need for a web server. If you go to your local Barns and Nobel you can pick up a CNE study guide with a 2 user license of NetWare 5.1 for about $80. I'll stop there.

Also, do a search on using the keywords:groupwise +webaccess +login +slow
There are 19 hits for that search, you may find your answer there. Brent Schmidt CNE, Network +
Senior Network Engineer

Why do user go into a panic when a NetWare server goes down, but accept it as normal when a Windows server goes down?
 
I believe AOL has installed some security updates that prevent users from getting in to WebAccess using the AOL browser without changing some security settings.

The easiest way around is to minimized AOL and use Internet Explorer or Netscape.
 
donnadee, do you know what those security setting changes are? We have begun encountering logon difficulties in WebAccess with those users who have upgraded to AOL 7 in recent weeks (including myself).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top