Please Note: DNTU’s RAS View only supports RAS not RRAS (Routing and Remote Access service). Beginning with Windows 2000, Microsoft combined both routing and remote access into a single service (RRAS).
DameWare NT Utilities provides two levels of Port statistics from within the Remote Access Service (RAS) Administration View - Port Status and Port Performance Data. The Port Status data displays information such as Port statistics, Connection Statistics, Device errors and Remote Workstation information. The Port Performance Data actually connects to the Performance counters that are tracked by the operating system. The Port Performance Data contains more detailed information related to bytes, frames, compression, device errors and timeouts. The refresh delay for the RAS Administration window view is customizable from within the property sheet.
You must have administrator privilege or server operator and account operator privileges for the domain or server you select to administer.
Dial-Up Networking is the client version of Windows NT Remote Access Service (RAS). Dial-Up Networking allows remote users on the following systems to work as if they were connected directly to the network: Windows NT, Windows for Workgroups, MS-DOS version 3.1 or later (RAS version 1.1a) and MS OS/2 version 3.1 (RAS version 1.1). Microsoft does not support access to Macintosh volumes and AppleTalk printers over dial-in lines. A Windows NT RAS configuration includes the following components:
Dial-Up Networking clients Windows NT, Windows for Workgroups, MS-DOS (with Microsoft network client software installed) and LAN Manager RAS clients can all connect to a Windows NT RAS server. Clients can also be any non-Microsoft PPP client.
RAS Servers The Windows NT Server RAS permits up to 256 remote clients to dial in. Windows NT Workstation permits one remote client to dial in. The RAS server can be configured to provide access to an entire network or restrict access to the RAS server only.
LAN protocols LAN protocols transport packets across a local-area network (LAN) whereas remote access protocols control the transmission of data over the wide-area network (WAN). Windows NT supports LAN protocols such as TCP/IP and RAS, IPX and RAS and NetBEUI and RAS, which enable access to the Internet and to NetWare and UNIX servers. Windows Sockets applications over TCP/IP or IPX, named pipes, Remote Procedure Call (RPC) and the LAN Manager API are supported.
Remote Access Protocols Windows NT supports Remote Access Protocols such as PPP, SLIP on RAS clients and the Microsoft RAS Protocol.
WAN options Clients can dial in using standard telephone lines and a modem or modem pool. Faster links are possible using ISDN. You can also connect RAS clients to RAS servers using X.25, an RS-232C null modem or using the Point-to-Point Tunneling Protocol (PPTP).
Security features Clients can dial in using standard telephone lines and a modem or modem pool. Faster links are possible using ISDN. You can also connect RAS clients to RAS servers using X.25, an RS-232C null modem or using the Point-to-Point Tunneling Protocol (PPTP).
Internet support RAS enables Windows NT to provide complete service to the Internet. A Windows NT Server computer can be configured as an Internet Service Provider, offering dial up Internet connections to a PPP client. A computer running Windows NT Workstation can dial into an Internet connected computer running Windows NT Server 3.5 or later or to any one of a variety of industry standard PPP or SLIP-based Internet servers.
RAS Servers Windows NT Server administrators use the Remote Access Admin program to control the RAS server, view users, grant permissions and monitor remote access traffic. For more information about using the Remote Access Admin program see Rasadmin.hlp.
The server must have a multi-port adapter or modems (9600 baud or above is recommended for acceptable performance), analog telephone lines or other WAN connections and the RAS software installed. If the server will provide access to the network, a separate network adapter card must be installed and connected for each network the server will provide access.
RAS servers are configured during initial RAS setup. You must specify whether access will be to the entire network or to the RAS server only. You must also select the protocols to use on the LAN (IPX, TCP/IP and NetBEUI) and an authentication encryption option.
Ports on RAS servers are configured individually. Each port can be set to Dial Out Only, Receive Calls Only or Dial Out and Receive Calls. These settings affect only the port specified, not all ports. For example, your RAS server can be configured to receive calls and COM2 can be configured for dial out and receive. A remote user can call in on either COM port but a local user can use only COM2 for outbound RAS calls.
Events and errors are recorded in Event Viewer on Windows NT/2000 RAS clients and servers. Evaluating the log in the Event Viewer can help you determine the source of problems. The Windows NT Server RAS permits up to 256 remote clients to dial in. The RAS server can be configured to provide access to an entire network or restrict access to resources on the RAS server only.
Using Windows NT Server to Provide Internet Access In conjunction with a router and Internet service provider, Windows NT Server acts as a gateway to the Internet for remote clients. Up to 256 clients can dial into the RAS server using standard telephone lines, ISDN lines, X.25 or PPTP. The clients then use any PPP compliant software or Windows NT computer together with Internet browsing tools to access the Internet.
The Internet Connection The Internet connection to your site will typically be made through a leased line to a router located on your network. Thus data travels over the Internet, over a leased line to a router, through the router, over you local network, to the RAS server and then to remote clients.