Do not allow network-based issues to fool you into thinking that NAVCE is the cause of a particular problem. Unless indications point strongly to local issues (for example, those having to do with NAVCE operations), remember that in a managed NAVCE environment, network factors can produce problems that seem to be caused by NAVCE.

Always look to your server log files, as well as those generated by NAVCE. They will inform you concerning DNS issues, as well as failed services that may have caused problems for your environment.

Remember the specific ports used by NAVCE, including the PDS (UDP port 38293), RTVScan (2967 for UDP in IP-based systems, and 33345 in IPX-based systems), and roaming clients (UDP port 1056).

You must have a primary NAVCE server. If, for some reason, all servers think they are secondary servers, take the necessary steps to promote one.

Clients and servers can easily begin to ignore each other if the keepalive packet values are not properly set for your particular environment. To ensure that clients remain in the SSC, take the necessary steps to change the keepalive packet value. Also, if communication problems persist, you may have to choose a preferred protocol on your NAVCE servers and export the updated grc.dat files to clients.

When working with 16- and 32-bit clients, make sure that you understand that if you combine these clients, only the 16-bit options will be available to you. Finally, remain aware of various bugs...