INF: Verify Registration of SQL Servers in NetWare Binderies |
Q112713
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.
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
NLIST /OT=154 /DYN
Additional query words: 4.20 bindery Windows NT
Keywords : kb3rdparty kbinterop
Issue type :
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ420OS2
|
Last Reviewed: March 19, 1999 © 2001 Microsoft Corporation. All rights reserved. Terms of Use. |