Troubleshooting the Gateway
Troubleshooting any software program requires that you to break down the process into its components, isolating each component to narrow down possible causes of the problem and thereby determine a solution.
One way to isolate the problem is to use gateway logging. The log information tracks message movements and can help you isolate breakdowns in the message routing process. Problems in the Async Gateway most often occur in either in an Async connection you have defined (to another Async Gateway or to a GroupWise Windows client in Remote mode), or in a modem or port.
Connection Suggestions
If you isolate the problem to a specific connection, try the following strategies:
Port and Modem Suggestions
If you isolate the problem to a particular port or modem, try the following strategies:
- Make sure the modem's initialization string is set to a fixed DTE rate.
- Make sure the port is set to CTS/RTS flow control, and make sure the modem initialization string contains the correct commands to set the modem to CTS/RTS flow control. Check your modem documentation for more information.
- If the modems at the two sites do not synchronize, reduce the baud rates at both sites to a lower rate.
- Reset the port, turn the modem off, then turn it back on.
- Isolate the port or the modem causing the problem. For example, you might try the modem with another port.
- If your computer or port is hanging or the modem is not initializing, check the IO port address conflict for an IRQ conflict with another board.
- If your connection is slow compared to the modem capability, check to see if the baud rate configured for port is greater than the maximum baud rate supported by the aiocomx.nlm port driver. A warning is recorded in the log file if this occurs. If you want to configure a higher baud rate for the port, reload the aiocomx.nlm with the maxrate option.
For general assistance with modem configuration, see Gathering Modem Information and Gathering I/O Port Driver Information for NetWare.