The problem is after you install NW Client 4.9. Sometimes it does not like the / in the script. Replace your / with \ in your login scripts and it will work. I had MAP ROOT M:=Servername_DATA.:HOME/%1 and changed it to MAP ROOT M:=Servername_DATA.:HOME\%1 and now it works. By the way...
To be able to restore GW to a completely rebuilt system you will need the Domain and PO directories of each domain and po in your system. If you only have one Domain and PO, then you will only need the Domain and PO directories and their entire contents. If you want to get technical, you could...
I use Netshield from McAfee and GWAVA together quite well. A trick that I learned is not to use Spam heuristics. Use SBL-XBL.SPAMHAUS.ORG as your RBL list. I don't get false positives, and everyone is very happy now. ;)
When you say "Once the process in Console One sucessfully completes," are you refering to the installation of C1 and the GroupWise snapins?
Are you making a fresh install of GW6.5, or is this an upgrade?
Thank you Terri.
All appeared to go well, until I tried to delete a PO that was still in the primary wpdomain.db. This PO was a backup, and was not in use at all. I kicked myself for not doing so before blowing away the servers.
I found out that even after repeated installs of GW Administration...
Thank you. I misspelled the switch. Your right, its /dsremove. To be sure that I had a backup of NDS, I used harware upgrade option in NWCONFIG '/noswitch' to make a backup of it. This locked DS, so I unloaded and reloaded DS.NLM with -ndb switch. Then went to NWCONFIG without a switch to...
I tried to use NWCONFIG /NDSREMOVE so as to disassociate the 2 GW servers that we use from the tree that it was in so as to run NWCONFIG to install NDS into another tree. It failed. I reinstalled NW6 and service packed them both to SP4. Copied the domain and post office directories from backup...
Are you using an Apache web server, or is Webaccess running on NetWare Enterprise Web Server? I ran Webaccess for a while on a NetWare (Netscape) Enterprise Web Server for a while with the same issue - 5 minute timeouts even though 60 minute timeouts were set on the application in NDS view in...
Webaccess is made up of 2 parts - the agent and the application. The application is the part that generates problems most of the time. Generally a reinstall of the application will fix most issues, but you might as well reinstall both parts at the same time, so that they are both fresh.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.