Microsoft KB Archive/112713

{|
 * width="100%"|

INF: Verify Registration of SQL Servers in NetWare Binderies

 * }

Q112713

-

The information in this article applies to:


 * Microsoft SQL Server version 4.2x

-

SUMMARY
Microsoft SQL Server for Windows NT with NWlink support and Network Integration Kit for NetWare (NIK) on OS/2 will register itself in the NetWare bindery upon start up in a NetWare environment. For a client to connect to SQL Server using SPX/IPX sockets, it first scans the bindery of the NetWare file server to which it is attached. If the client fails to connect, you need to verify whether or not the SQL Server service is registered successfully in the binderies.

MORE INFORMATION
In general, you can use the NetWare utility NLIST that is shipped with NetWare 4.x to view or search objects in NetWare binderies. SQL Server or NIK is also registered as an object, and its object type is 62723. However, since NLIST can not search on an object type of more than four digits long, you need to search on the SQL Server service name, as specified when you setup the SQL Server or NIK. For example, to verify whether or not your SQL Server MYSQLSERVER is registered, you can execute:

"NLIST /OT=* where name = MYSQLSERVER /DYN"

In addition, you can also use the option /B=MY_OTHER_FILE_SERVER to check if the bindery contents are propagated to other file servers.

For named pipes servers, you can also use NLIST to help diagnose connection problems. For example, the following command will list all the named pipes servers active on the network:

"NLIST /OT=154 /DYN"

Although file servers are not necessary for named pipes applications, you can use this to verify if a named pipes server is actively broadcasting its presence on the network.

If NLIST is not available, you can always use the console command DISPLAY SERVERS to view the NIK or SQL Server for Windows NT with NWLink. You can use this command either from the server console, or from a remote console (RCONSOLE).

Additional query words: 4.20 bindery Windows NT

Keywords : kb3rdparty kbinterop

Issue type :

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ420OS2