Remote Syncronization GroupWise 5.5 - Would think this is EZ

You're talking about the "Hit the Road" feature (Tools|Hit the Road).  This is a feature that lets a user sync his GW mailbox to a remote mailbox on the laptop (while on the LAN).  Then, while off the LAN, the user can compose and read messages.  To send/receive messages, the user dials in to the Async Gateway, connects by VPN, or dials in to the LAN to sync/exchange messages with the post office.

You need to decide how the user will connect to the post office when he's offsite - Async or VPN, or just plain dialup into the LAN.

As ToddS mentioned, the documentation is quite good and it wouldn't be of much use to reprint it here.

If the user does not need to read/generate email while disconnected to the LAN, you may want to consider GroupWise WebAccess.  As long as the user has Internet access, he can read and send messages via web browser.  The downside is that you can't work offline with WebAccess.

For security reasons, we are going to opt for a direct dialup into the Async Gateway.  We have a small number of users that will ever use this feature (less then 10), so the occassional busy signal will not be a problem.

hbueno, Could you clarify, though, what you mean by dialing into the LAN?  Are you talking about straight remote access to a client machine (e.g., pcAnywhere) - if so, we use that now, but since pcAnywhere is transmitting screen data, it is much slower than a direct link to sychronize the files between someone's groupwise remote and main account.

Our I.T. tech is having difficulty with setting up the modem at this point.  She downed the server, attached the modem, but now whenever she attempts to dial in, all she receives is a busy signal.

one comment regarding Hit the Road - if you are running GroupWise 5.5 EP1 or 6 and have the Padlock patch on the server loaded, you must also use the Padlock patched GroupWise clients or the Hit the Road feature will not work.

Dialing into the network with Async gateway means that the laptop modem will dial up the modem attached to the NetWare server running the Async gateway software from the GroupWise client.  The client will then be able to sync it's data with the GroupWise POA.  It's not a pcAnywhere thing.

Other options are to:

GroupWise WebAccess
-or-
NAT a public IP address to your POA and allow the GroupWise clients to attach directly from the Internet.

Well, I didn't know if I had the padlock fix or not, but according to this document:

http://support.novell.com/servlet/tidfinder/10064207

I'm assuming I do (I have a later version of the GWENN3.NLM running as a module on the server and Gwenv1.dll in the c:\WINNT\system32 folder of the client machines).  I do not have a gwenv1a.dll anywhere on the hard drives, including XP machines.  However, we are not running any straight version of Windows NT client or server.

In any case, I could download the client patch, but the server patch wasn't available for download anywhere.  This is kind of a separate issue, but I'm going on the assumption that the software installed on the server and on the workstations included the padlock fix.  SCREAM at me if this isn't a good assumption.

Kevin