Knowledge Base

Windows TCP/IP Registry Entries

Article ID: 158474

Article Last Modified on 3/27/2007


APPLIES TO


This article was previously published under Q158474
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

The value entries that are described in this article do not normally exist in the Windows registry; they must be added to the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP

Values

This section describes variables for subkeys that appear in the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\ServiceProvider

The following keys describe the order used to resolve host names. A lower number sets a higher priority for name resolution. These settings are used for 16-bit Windows Sockets, which need to rely on the resolvers that are expected to take the least time. The numbers indicate the default values specified in Windows.

Note that the below values apply to Windows Sockets 1.1, and are not used if Windows Sockets 2.0 is installed (this is the default for Windows 98, and is an option for Windows 95).

LocalPriority = 499
HostsPriority = 500
DNSPriority = 2000
NetbtPriority = 2001

For additional information about this functionality, click the article number below to view the article in the Microsoft Knowledge Base:

170619 Windows 95 ServiceProvider Priority Values Not Applied

The entries in this section must be added to the following registry key, where n represents the particular TCP/IP-to-network adapter binding.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\netTrans\000n

MaxMTU = 16-bit integer
Data Type: String

This specifies the maximum size datagram IP that can pass to a media driver. SNAP and source routing headers (if used on the media) are not included in this value. For example, on an Ethernet network, MaxMTU will default to 1500. The actual value used will be the minimum of the value specified with this parameter and the size reported by the media driver. The default is the size reported by the media driver.

For additional information about obtaining RFC documents, click the article number below to view the article in the Microsoft Knowledge Base:

185262 How to Obtain Request for Comments Documents from the Internet

Keywords: kbenv kbinfo kbnetwork KB158474