The Routing and Remote Access service does not start in Windows 7 or in Windows Server 2008 R2 when there is no network connectivity
On a computer that is running Windows 7 or Windows Server 2008 R2, the Routing and Remote Access service (RRAS) does not start when there is no network connectivity. For example, RRAS does not start when all wired network connectivity is un-plugged or when wireless connectivity is shut off.
Additionally, you cannot create new incoming connections when there is no network connectivity. This is because incoming connections require that RRAS is started.
When RRAS starts, it tries to initialize certain functions in Internet Authentication Service (IAS) for authentication. The IAS initialization fails when there is no network connectivity. Therefore, RRAS does not start. On Windows 7 and on Windows Server 2008 R2, IAS initialization failure is by design when there is no network connectivity. Then, you see the behavior that is mentioned in the "Symptoms" section.
To start RRAS in order to create a new incoming connection, your computer needs to be connected to a network. After RRAS starts, you will still be able to create a new incoming connection after you disconnect from the network.
To check the status of RRAS, check the state of the RemoteAccess service (Routing and Remote Access) under the Services tab in Windows Task Manager.
This behavior is by design.
Incoming Connections depend on the Routing and Remote Access service which was unable to start. For more information, check the system event log. ncpa.cpl New Incoming Connection VPN RRAS creating Incoming connection fails
Article ID: 973990 - Last Review: 01/06/2010 08:41:37 - Revision: 2.0
Windows 7 Enterprise, Windows 7 Home Basic, Windows 7 Home Premium, Windows 7 Professional, Windows 7 Starter, Windows 7 Ultimate, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard
- kbexpertiseinter kbtshoot kbsurveynew kbprb KB973990