Communication problems among servers can generate messages such as Unable to Communicate with Server or messages that a directory partition operation can’t be completed. If DSTRACE is set to On, -625 errors appear in the DSTRACE output because the directory cannot be synchronized among the servers.
Use the following steps to troubleshoot server-to-server communication problems.
Make sure the server is up and can been seen on the network.
If the server is down, restart it.
If the server has abended, troubleshoot the abend. See Resolving Abends.
Make sure the server’s time is synchronized to the network.
To see if server time is synchronized to the network, enter TIME at the System Console prompt.
If time is not synchronized, troubleshoot the time synchronization problem. For general information about time synchronization, see the NW 6.5 SP8: Network Time Synchronization Administration Guide.
Make sure the IPX™ internal network number of the server unique and the IP addresses unique. Make sure all replicas have the correct address for each server.
If all the servers in a replica ring cannot communicate with one of the servers in the ring, there is probably an address problem.
Make sure all addresses are unique. Make sure all replicas have the correct address for each server. Load DSREPAIR, select Advanced Options > Replica and Partition Operations > replica > Display Replica Information.
Make sure all replicas have the correct server name.
Incorrect or duplicate server names in directory replicas make it impossible to communicate with the server. Make sure all replicas have the correct name for each server. Load DSREPAIR, select Advanced Options > Replica and Partition Operations > replica > Display Replica Information.
If names are not correct, contact a Novell Support Provider for assistance in renaming servers.
If the servers share the same cabling system, make sure addresses are unique for each cable segment.
If addresses are not unique, change addresses as necessary.
Make sure all LAN drivers are loaded and protocols are bound. Make sure all LAN adapters and drivers are the latest versions.
Load and bind LAN drivers, if necessary. If drivers are not the latest versions, update the drivers. In addition, search the Novell Knowledgebase for known problems with specific adapters. Replace adapters if necessary.
Make sure the LAN is functioning.
Ping the servers to see if the connection is active. View LAN statistics using Novell Remote Manager or Monitor to make sure packets are being sent and received. Review statistics such as packets received and sent, collisions, and retries.
If the LAN connection is malfunctioning, troubleshoot the physical link between the servers. See Tips for Resolving General Communication Problems.
Make sure the routers have enough memory to handle the increase in packets.
If your servers have just been upgraded from NetWare 3, some routers might not have enough memory to buffer the increase in packets from NetWare 3 to NetWare 4, 5, or 6 servers. Make sure the routers have enough memory.
Remove routing filters.
If the servers are using IPX and the routers are filtering SAP types 004, 26b, and 278 packets, remove the filters.
If you are using IPX, reset the server’s internal IPX router.
Use the RESET ROUTER command at the System Console prompt to reset the server’s internal IPX router. Troubleshoot other routers.
Make sure data can transfer over WAN links.
Are servers separated by 56 KB WAN links?
If yes, this could be the source of the problem. Consider the following:
Is there a guaranteed transfer rate or does the rate decline when network traffic is heavy? If the rate declines, the link might not provide the performance you need to maintain consistent communication.
Are you trying to transfer large files or an entire replica across the link? You might be able to synchronize replicas across a 56 KB link, but not transfer an entire replica.
Do the servers have to traverse more than one 56 KB link?
To solve the problem, you might need to provide faster links.
Make sure server utilization is not high.
Do the affected servers have utilization at or close to 100%?
If yes, take steps to reduce server utilization. See High Utilization Statistics.
Make sure the eDirectory database is not locked.
If DSREPAIR is running, the eDirectory database will be locked. Other applications might also lock the database while writing to it.
If the database is locked, wait for DSREPAIR or other modules to finish using the database or shut down the utility or module.
If the problem still occurs, follow the troubleshooting steps in Using a Troubleshooting Methodology, search the Novell Knowledgebase, and contact a Novell Support Provider.