Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 28

POA Starts Unwanted TCP/IP Thread
POA Fails to Deliver Messages
Possible Cause: The post office is closed.
Possible Cause: Message file processing has been turned off.
POA Fails to Respond to MTP Configuration Changes in ConsoleOne
28 GroupWise 7 Troubleshooting 2: Solutions to Common Problems
TCP/IP connection failure (8908)
TCP/IP disconnected (890F)
TCP/IP read timeout (8912)
Action: See also "POA Fails to Respond to MTP Configuration Changes in
ConsoleOne" on page
Problem: Even though you have started the POA using the /notcpip startup switch or
disabled the Enable TCP/IP option in the POA Agent Settings page in
ConsoleOne, the POA still starts a TCP/IP thread.
Explanation: When you select Client/Server Only or Client/Server and Direct as the access
mode for a post office and use the
POA does not accept incoming client/server connections from GroupWise
clients. However, it still starts a single TCP/IP handler thread if TCP/IP is
configured on the server. The purpose of this TCP/IP thread is to notify any
GroupWise clients connecting to another POA in the post office via TCP/IP
they should reread the database because a new message has been delivered by
a POA that is not using TCP/IP.
Action: To totally disable TCP/IP processing in a post office, set the access mode for
the post office to Direct Only and start all POAs servicing that post office with
the /notcpip switch, or deselect Enable TCP/IP in the Agent Settings page in
ConsoleOne.
Problem: The POA is running but no messages are being delivered.
Action: From the MTA console, check the status of the post office from the point of
view of the domain. See
the MTA" in the
closed, messages are not arriving in the post office. Correct the problem with
the MTA. See
Action: Make sure that message file processing for the POA has not been turned off
using the /nomf, /nomfhigh, or
Problem: You change a POA link configuration or network address setting in
ConsoleOne, but the POA does not respond to the change. For example, you
change from a mapped or UNC link to a TCP/IP link between the POA and the
MTA, or you move the POA to a different server and change its IP address. If
the configuration change does not replicate successfully to the post office
database, the MTA link to the post office becomes closed.
Action: If you do not want to stop and restart the POA to open a closed post office link,
change the configuration information back to what it was before you tried to
change it. The MTA should then be able to open the post office link again.
28.
/notcpip
"Displaying MTA Status
GroupWise 7 Administration
"MTA Status Box Shows a Closed Location" on page
/nomflow
switch when starting a POA, that
Information" in "Monitoring
Guide. If the post office is
switches.
36.