RAS and Netlogon Services Load Order Changes (121809)

The information in this article applies to:

Microsoft LAN Manager 2.1
Microsoft LAN Manager 2.1a
Microsoft LAN Manager 2.2
Microsoft LAN Manager 2.2a
Microsoft LAN Manager 2.2b

This article was previously published under Q121809

SYMPTOMS

After Remote Access Service (RAS) services are installed on a LAN Manager server, if the server's domain role is changed from standalone to member, backup, or primary, the load order for server services specified on the SRVSERVICES line of the LANMAN.INI file needs to be manually modified. Otherwise, the server service will not start and the following message appears:

NET3062: The sub-service remoteaccess failed to start.

The server's error log will show the following:

NET3113: Server not started because service not started.

CAUSE

When RAS services are installed, the server service REMOTEACCESS is added to the end of the SRVSERVICES line in the [server] section of the LANMAN.INI file. If the server's role is changed to standalone and then to either member, backup or primary, the NETLOGON service is added to the end of the SRVSERVICES line in LANMAN.INI.

RESOLUTION

In order to correct this problem, modify the SRVSERVICES line in the LANMAN.INI file to the following order:

   [server]
      srvservcies = alerter,netlogon,remoteaccess

NOTE: Netlogon must load before Remoteaccess.

MORE INFORMATION

If the server's role is changed to standalone, such as in cases when administrators are having trouble synchronizing a domain, the SRVSERVICES line in LANMAN.INI will be modified to:

   [server]
      srvservices = alerter,remoteaccess

Promoting the server to member, backup, or primary will add the netlogon service to the end of the SRVSERVICES line:

  [server]
     srvservices = alerter,remoteaccess,netlogon

The server service then fails to load, and the above error messages appear.

Modification Type:	Major	Last Reviewed:	9/30/2003
Keywords:	KB121809