An optional Microsoft Windows NT networking service that provides remote access for remote clients. A machine running Windows NT on which Remote Access Service (RAS) is installed is called a RAS server.
RAS allows remote clients to connect through a telephone line or other wide area network (WAN) link to the RAS server; from there RAS allows those clients to access resources on the network. Remote users can access network resources as though they were logged on to a machine directly connected to the network. To allow a user to connect remotely to the RAS server, use the administrative tool User Manager for Domains and grant the user dialin permission. You can set three forms of dialin permission:
RAS on Windows NT provides both dial-in and dial-out capability, supporting up to 256 simultaneous inbound connections on Windows NT Server but only one inbound connection on Windows NT Workstation. Clients that want to connect to a RAS server must have dial-up networking or a similar application installed. RAS is fully integrated into the Windows NT security model and supports encrypted authentication, auditing, callback, and intermediary hardware security hosts. Users can be restricted to access to the RAS server only, or to access through the RAS server to all resources on the network.
Windows NT RAS supports clients connecting over the following media:
You can establish RAS connections with Windows NT by using any common local area network (LAN) transport protocol and the following WAN protocols:
An optionally available Windows NT 4 component called Routing and Remote Access Service (RRAS) replaces the existing RAS on Windows NT and provides additional Internet Protocol (IP) routing functionality.
On Windows 2000 Server, remote access functionality is provided by Routing and Remote Access, which supports both dial-up networking and virtual private networks.
You install RAS on a Windows NT server by using the Services tab of the Network utility in Control Panel.