Unable To Connect SQL Server Using NWLink

 Last reviewed: September 9, 1996
Article ID: Q130014
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5
  • Microsoft Windows for Workgroups version 3.11

SYMPTOMS

When you use the IPX/SPX compatible transport protocol (NWLink) in Windows NT or Windows for Workgroups, it may not connect to a Microsoft SQL Server.

CAUSE

When SQL Server starts listening on SPX, it registers itself with the bindery on a NetWare server. Clients attempting to connect read from the bindery to make the connection to the SQL Server computer. This process fails if no NetWare server exists on the network.

RESOLUTION

To correct this problem, use the following format to connect to a SQL server: 

   isql -Usa -P -S<MAC address>,<IPX port number>,<Network number>
NOTE: The default IPX port number for a SQL server is 33854. A network number is not required if the SQL server is on the same segment.

KBCategory: kbnetwork
KBSubcategory: ntinterop ntprotocol
Additional reference words: prodnt 3.10 3.11 3.50 nwfp ncp



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.