Member server in a domain

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Member server in a domain

For a server running Routing and Remote Access that is a member server in a domain, four accounts databases are available:

  1. Local.

  2. Windows NT 4.0 domain.

  3. Windows 2000 mixed domain.

  4. Windows 2000 native or Windows Server 2003 domain.

The following table describes the management of user dial-in properties for each accounts database.

Accounts database User dial-in properties

Local

Administered by using Local Users and Groups.

Windows NT 4.0 domain

Administered by using the Windows NT 4.0 User Manager for Domains administrative tool.

Windows 2000 mixed domain

Administered by using either Active Directory Users and Computers or the Windows NT 4.0 User Manager for Domains administrative tool.

Windows 2000 native domain

Administered by using Active Directory Users and Computers.

Note

  • In order for the remote access server to access user account dial-in properties stored in Active Directory, the Routing and Remote Access service must run in the security context of a computer account that is a member of the RAS and IAS Servers security group. When you run the Routing and Remote Access Server Setup Wizard to configure Routing and Remote Access in a domain, the computer account of the remote access server is automatically added to the RAS and IAS Servers security group. If the remote access server needs to access user dial-in properties in other domains, you must manually add the computer account to the RAS and IAS Servers security group of the other domains either through Active Directory Users and Computers or by typing netsh ras add registeredserver at a command prompt. For more information, see Netsh commands for remote access and Remote Access Troubleshooting.