COPY *.MNU

Newsletter of the Melbourne Novell Users Group

February 1998

GroupWise Handy Tips

Supplied by: David Hancock

When GroupWise is started it checks your archive databases. You can delete the archive databases to get into GroupWise without further hassle.

But if the archive is important then you can run the maintenance tools over it.

Download the latest maintenance tool (gwchck32.exe). This is a 32 bit tool that looks identical to the Mailbox/Library database Maintenance tool. Download gwchk918.exe from www.novell.com and run it in a local directory to expand out to gwchk32.exe. Execute gwchk32.exe and select the archive/remote radio button and provide the complete path to your archive directory such as:

f:\gw\archives\ofdaharc

dah is the user FID

You can use this tool to repair your remote databases too.

The gateway now supports dial up capacity according to a schedule such as every 2 hours, only when 5 messages are queued etc. You require the MPR which is supplied free with Intranetware but cannot run on the Small Business system!!! It cannot provide enough resources and Novell receive many complaints. If you have a small Business system and want a dial up GW SMTP gateway, upgrade to Intranetware or install the GWIA onto a NT box and use Network Dial-up.

I have the MPR and GWIA working well. Your ISP will need to store your mail and poll every minute to see when you are connected to download the mail.

Another hitch I found was the GWIA must run on the same machine as the MPR. Otherwise the MPR did not see the packets. You may need to do this to run the modem that connects to the ISP on a different server to the one that stores the Domain. It is tricky getting the GWIA to run as a runtime. Files will need to be loaded to the other server including the GWIA.CFG file which is updated on line by nwadmn95.exe. You will need to copy this file to the runtime server after changes are made!

I would be happy to hear from anyone that knows if the GWIA can work with the MPR running on a different server (tree), Novell support did not show much interest since it is unlikely customers will want to run a "runtime" MPR.

Early this year I solved a syncing problem by changing the Case of the System name. This in fact was the fix. Synchronization of the System is not case sensitive. When Ext sync is setup up between two systems, a message is passed between them and the system name, domain name is verified and a validation is passed back to say "everything is okay". If there is a problem then synchronization does not work. By entering (creating) the sync record again this dialogue was restarted and worked! The original message may not have been received due to incorrect links etc.

Therefore if sync is not working but the links and therefore messages between the two systems are going through, delete the external sync and recreate it again!