Microsoft KB Archive/115875

= Problem with Scope ID on Alpha and MIPS Systems =

Article ID: 115875

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Advanced Server 3.1

-



This article was previously published under Q115875



SYMPTOMS
Using a NetBIOS Scope ID that contains more than one character on an Alpha-based or MIPS-based computer causes Scope IDs to function incorrectly. If Intel-based, Alpha-based, and MIPS-based computers are all configured with TCP/IP as the only protocol installed, and all three systems are on the same segment (no routers in- between), and all have the same Scope ID (for example "test") the Intel-based computer generates the following error message when attempting to Net View the Alpha-based computer:

System error 53 has occurred. The network path was not found.

Likewise, the Alpha-based computer returns the same error message when attempting to Net View the Intel-based computer.

If the MIPS-based computer is involved, either Net Viewing one of the other computers or being Net Viewed by one of the other systems, the following STOP message appears:


 * STOP 0x01E (0x80000002,0xFCC3110C,0x0000000,0x8092EEBF)

UNHANDLED KERNEL EXCEPTION 80000002 from FCC3110C (0,8092EEBF)


 * FCC311OC has base at FCC20000 - nbt.sys



CAUSE


STATUS
Microsoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. This problem has been corrected in the latest U.S. Service Pack for Windows NT and Windows NT Advanced Server version 3.1. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: prodnt parameter err msg blue screen

Keywords: kbnetwork KB115875

-

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

© Microsoft Corporation. All rights reserved.