Microsoft KB Archive/270667

= BUG: SQL Server 2000 SPX Named Instance Uses the Same Port as the Default Instance =

Article ID: 270667

Article Last Modified on 11/5/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q270667



BUG #: 235516 (SQLBUG_2000)



SYMPTOMS
Users are unable to connect to a SQL Server 2000 Named SPX Instance, if there is also a SQL Server 2000 default Instance listening on IPX/SPX, or a default Microsoft SQL Server 7.0 Server listening on IPX/SPX. Alternatively, if there are two named instances, both listening on IPX/SPX, they both attempt to listen on the same SPX port 33854. No errors are reported in the SQL Server errorlog even though the Named Instance failed to listen on port 33854.



CAUSE
The default port used for IPX/SPX connections is 33854. The SQL Server Network Utility selects this port for SQL Server SPX named instances as well.



WORKAROUND
Use the SQL Server Network Utility to change the properties of the Named SPX Instance to listen on a port other than 33854.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000.



MORE INFORMATION
SQL Server 2000 continues to use bindery for name resolution by broadcasting Service Advertising Protocol (SAP) packets to register the name in Netware binderies. For named instances, the bindery name is in the form of MYSQL$MYINSTANCE. To see the bindery name, use the SQL Server Network Utility and look at the properties for IPX/SPX. However, when you make connections to the named instance, you continue to specify the instance by using a backslash &quot;\&quot;, for example, MYSQL\MYINSTANCE. The client side network library automatically converts the backslash &quot;\&quot; to dollar sign &quot;$&quot; for name resolution.

Additional query words: Netware Novell IntraNetware

Keywords: kbbug kbpending KB270667

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.