This article was previously published under Q179092
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it ifa problem occurs. For information about how to do this, view the "Restoringthe Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"Help topic in Regedt32.exe.
NWLNKIPX sends the broadcast Routing Information Protocol over IPX (RIPX)packet over the network, even if a frame type and network number isselected manually.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
After applying this fix, use the steps below to create a new registryvalue.
WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall Windows. Microsoft cannot guarantee thatproblems resulting from the incorrect use of Registry Editor can be solved.Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys AndValues" online Help topic in Registry Editor (Regedit.exe) or the "Add andDelete Information in the Registry" and "Edit Registry Data" online Helptopics in Regedt32.exe. Note that you should back up the registry beforeyou edit it.
NOTE: The above registry key is one path; it has been wrapped for readability.
On the Edit menu, click Add Value and use the following entry:
Value Name: NoBcastRipRequest Data Type: REG_Dword Value: 0 or 1 Default:
Description: This parameter determines if NWLNKIPX sends the Broadcast RIPX packet during initialization. Set this value to 1, if you do not want to send a Broadcast RIPX packet during initialization.
Close Registry Editor.
Restart the computer for the registry change to take effect.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
When NWLNKIPX starts, Routing Information Protocol over IPX (RIPX)broadcasts are sent to determine the frame type and network number. ThisRIPX packet is needed only if the auto-detect feature of NWLNKIPX isselected.