Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Best practices for NWLink

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Best practices for NWLink

If you do not know what value to use for the internal network number, accept the default value of 00000000.

  • You can determine what internal network number your routers are using by typing ipxroute config at a command prompt.

  • For more information about setting the internal network number, see Configure NWLink.

Use automatic frame type detection.

  • You should choose to have the frame type automatically detected rather than setting this value manually. If you must use manual frame type detection, determine what type of frame type you should use before you start configuring the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol (NWLink) by typing ipxroute config at a command prompt. In addition, verify that all the server computers on your network that use IPX/SPX are using the same frame type.

  • For more information, see Configure NWLink.

Specify the order that Windows accesses network providers and protocols.

  • By changing your provider order, and by changing the order of protocols bound to those providers, you can improve performance. For example, if your LAN connection is enabled to access NetWare and Microsoft Windows networks and uses TCP/IP and IPX, but your primary connection is to a NetWare network, you can move NetWare or Compatible Network to the top of the Network providers list on the Provider Order tab, and move NWLink IPX/SPX/NetBIOS Compatible Transport Protocol to the top of the File and Printer Sharing for Microsoft Networks binding on the Adapters and Bindings tab.

  • For more information about modifying the order of network providers, see Modify the network provider order. For more information about modifying protocol bindings, see Modify the protocol bindings order.

Only install and enable the network protocols that you need.

  • Limiting the number of protocols on your computer enhances network performance and reduces network traffic.

  • If Windows encounters a problem with network connectivity, it attempts to establish connectivity by using every network protocol that is installed. By only installing and enabling the protocols that your system can use, Windows does not attempt to connect with protocols it cannot use, and returns status information to you more efficiently.

When using direct hosting, if you cannot access a server computer running Windows 95 or Windows 98 from a server running Windows Server 2003 , you must enable NetBIOS over IPX/SPX on the computer running Windows 95 or Windows 98.

  • For more information about enabling NetBIOS, see the Windows 95 or Windows 98 documentation.

When you use NWLink to connect computers running Windows that use Windows-based networking, ensure that NetBIOS broadcast propagation (type 20 packets) is enabled on all the router interfaces that connect the computers running Windows.

  • You can enable NetBIOS broadcast propagation by using Routing and Remote Access. NetBIOS broadcast propagation is enabled by default.


  • Client Service for NetWare is not available on 64-bit versions of Windows Server 2003 and Windows XP.

  • Gateway Service for NetWare is included in Windows 2000 Server. It is not included in the Windows Server 2003 family.

  • Computers running operating systems in the Windows Server 2003 family cannot be IPX routers.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft