Beginning of this page.
Jump to main content.

Please note that JavaScript and style sheet are used in this website,
Due to unadaptability of the style sheet with the browser used in your computer, pages may not look as original.
Even in such a case, however, the contents can be used safely.

Site menu starts here.
Skip site menu.
End of site menu.
Displaying present location in the site.
End of menu.
Main content starts here.

Support Information:
Considerations for Using Scalable Networking Pack (SNP)
– Supplement –

Published: September 29, 2014

Enabling SNP

You can enable SNP by the following methods. Those differ depending on the operating systems. To enable these features, you must change the network adapter settings to "enabled" according to the operating system settings.

[Important]
The methods include how to change the registry, but changing the registry incorrectly may cause a critical problem. Pay enough attention when you edit the registry. NEC recommends preparing some countermeasures for possible troubles such as making a backup of the registry before editing it just in case. Please note that all manipulation of the registry must be done at your own risk.

Windows Server 2003 Family

SNP is enabled by editing the registry.

[Applicable Operating Systems]
  • Windows Server 2003
  • Windows Server 2003 R2
  • Windows Storage Server 2003
  • Windows Storage Server 2003 R2
[Procedure]
  1. Open the Registry Editor and set the following registry values to "1." If the registries cannot be found, create them and set the values to "1" in like manner.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Name
    Type
    Value    		 : EnableTCPChimney
    : REG_DWORD
    : 1
    Name
    Type
    Value    		 : EnableRSS
    : REG_DWORD
    : 1
    Name
    Type
    Value    		 : EnableTCPA
    : REG_DWORD
    : 1

  2. Restart the operating system.

Windows Server 2008 Family

SNP is enabled by editing a registry and executing the netsh command.

[Applicable Operating Systems]
  • Windows Server 2008
  • Windows Vista
  • Windows Storage 2008 R2
  • Windows 7
[Procedure]
  1. Open the Registry Editor and set the following registry value to "1." If the registry cannot be found, create it and set the value to "1" in like manner.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    Name
    Type
    Value    		 : EnableTCPA
    : REG_DWORD
    : 1
  2. Apply the hotfix provided in [Article ID: 967224] (*1) before executing the netsh command. (This is not required for Windows Server 2008 R2 and Windows 7.)

  3. Open the Command Prompt and set the following settings using the netsh command.
    4. netsh int tcp set global chimney=enabled
    netsh int tcp set global rss=enabled

  4. Restart the operating system.

Windows Server 2012 / Windows Server 2016 Family

SNP is enabled by executing the netsh command.

[Applicable Operating Systems]
  • Windows Server 2012
  • Windows 8
  • Windows Server 2012 R2
  • Windows 8.1
  • Windows Server 2016
  • Windows 10
[Procedure]
  1. Open the Command Prompt and execute the netsh command as follows.
    2. netsh int tcp set global rss=enabled
    netsh int tcp set global chimney=enabled

  2. Restart the operating system.
(*1)About Hotfix provided in [Article ID: 967224]

  • Executing the netsh command on Windows Server 2008 or Window Vista can cause the issue shown in [Article ID: 967224]. As the netsh command is used for disabling/enabling SNP, apply the hotfix provided in [Article ID: 967224] beforehand.
  • As for Windows Vista, the hotfix is applicable to Service Pack1 and later. If any service pack has not been applied to the operating system, apply Service Pack1 before installing the hotfix.
  • The product name for this hotfix is shown as "Windows Vista," but it is also applicable to Windows Server 2008.
  • As the issue shown in [Article ID: 967224] does not occur on Windows Server 2008 R2 or Windows 7, the hotfix is not needed for these operating systems.
[Article ID: 967224]
Some TCP/IP parameters in the registry are changed to incorrect values when you use the netsh command to change TCP/IP global parameters on a computer that is running Windows Server 2008 or Windows Vista.
http://support.microsoft.com/kb/967224
End of main content.
Windows Server is a registered trademark of Microsoft Corporation in United States and other countries.
All other product, brand, or trade names used in this publication are the trademarks or registered trademarks of their respective trademark owners.