The IPv6 connection protocol is not negotiated correctly when you use the Netsh utility to configure the Routing and Remote Access service on a Windows Server 2008-based computer

Article translations Article translations
Article ID: 947042 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

You use the Netsh utility to configure the Routing and Remote Access service for IPv6 routing and for IPv6 remote access on a Windows Server 2008-based computer. After you do this, the IPv6 connection protocol is not negotiated correctly. Therefore, the remote access client can only obtain an IPv4 address.

This issue does not occur when you use the Routing and Remote Access Microsoft Management Console (MMC) snap-in to manually configure the computer.

CAUSE

This issue occurs because the Netsh utility requires two separate commands to fully enable the Routing and Remote Access service for IPv4 or for IPv6.

RESOLUTION

To resolve this issue by using the Netsh utility, type the following commands at a command prompt. Press ENTER after each command.
netsh ras set type ipv4rtrtype=none ipv6rtrtype=lanonly rastype=ipv6
netsh ras ipv6 set negotiation mode=allow

Properties

Article ID: 947042 - Last Review: January 21, 2008 - Revision: 1.2
APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Standard
  • Windows Web Server 2008
Keywords: 
kbtshoot kbprb kbexpertiseinter KB947042

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com