Advantage Database Server for NetWare Discovery

Networking Issues

The NetWare bindery and NetWare directory are lists of services available on the network. The Advantage Database Server for NetWare uses SAP, Service Advertising Protocol, packets to advertise availability in the NetWare bindery or the dynamic part of the NetWare directory. The entry in the NetWare bindery or directory for the Advantage Database Server for NetWare contains the NetWare server name upon which the Advantage Database Server is located, the Advantage Database Server unique object ID which is pre-defined by Novell, and the network address of the Advantage Database Server for NetWare.

Advantage clients call a NetWare API to find the nearest NetWare bindery or directory. That bindery or directory is then searched to determine whether the Advantage Database Server for NetWare is located on the specified file server. If it is, the network address information of the Advantage Database Server is obtained. The Advantage client can then use this information to connect to the Advantage Database Server for NetWare.

During the NetWare bindery/directory search Advantage clients also send out an IP multicast packet that contains the name of the file server specified for the connection. All Advantage Database Servers running on an IP-enabled machine will receive this multicast packet. Each Advantage Database Server that receives this packet will inspect the packet, comparing its file server name to the name in the packet. If the names match the Advantage Database Server will respond to the client with all of its IP and IPX addresses, which the client can then use to connect to the Advantage Database Server.

If the Advantage Database Server information is not found in the NetWare bindery or directory, and no servers reply to the multicast request, the Advantage Database Server is not available on the specified file server. If the Advantage application has been written to attempt a connection to the Advantage Internet Server as well as the Advantage Database Server, a connection via the Advantage Internet Server will then be attempted. If the connection to the Advantage Internet Server is either not attempted or is not successful, and if the Advantage application has been written to attempt a connection to the Advantage Local Server as well as the Advantage Database Server, a connection via the Advantage Local Server will then be attempted. If all Advantage server connection attempts are unsuccessful, a 6060 "Advantage Server Not Available" error will be generated.