How to enable the Routing and Remote Access Service RRS feed

  • Question

  • When I try to start the Routing and Remote Access service on POSReady 7, I get:

    The Routing and Remote Access service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

    .. the Event Viewer is decidedly unhelpful as to cause; I just get:

    "The Routing and Remote Access Service terminated with service-specific error The request is not supported.."

    I've read elsewhere that ICS will provide similar functionality, but it won't start either.  How do I get RRAS started on POSReady 7?

    Tuesday, April 23, 2013 5:24 PM

All replies

  • I have faced similar issue with Windows 7 embedded system (custom configuration)

    I started debugging this issue and eventually found out that disabling WAN Miniport (IP) adapter will allow me to enable Routing and Remote Access service.

    Wan Miniport (IP) adapter is only visible in device manager when you enable Show hidden devices option in View menu inside device manager.

    If this also works for you then you may proceed further with steps below.

    In order to fix it properly I did following:

    A) Find location of WAN Miniport IP adapter. In my case it was located at following location in my target registry


    B) Set the Upperbind value to DNE

    I just noticed that in my Windows 7 laptop the UpperBind value inside Linkage Subkey was set to DNE (Should probably be Do Not Enable) while in target it was set to something else.

    I updated the UpperBind key to DNE and committed and restarted the system (since C:\ is EWF protected). It worked like charm.  

    Let me know if it helps!

    • Proposed as answer by Aagosh Thursday, May 23, 2013 11:39 AM
    Thursday, May 23, 2013 11:39 AM
  • Did you resolve this? I encountered the exact same problem on POSReady 7, but not on Windows 7 Professional...
    Monday, October 3, 2016 6:57 PM
  • I followed your steps. I did stop getting the error message, but Windows still stops the service a few seconds after it's started. So kind of helped, but didn't solve the underlying issue for me. Thanks anyways.
    Thursday, June 8, 2017 12:35 AM