Here are my notes on how Windows 2000 server can be accessed remotely using two technologies:
For Network Diagnostics:
Configure outbound connections for domain members.
To grant new user accounts dial-up access, first create a Universal group such as “Dialup Users” and modify the remote access policy to allow dial-up access. Then, add users to the group.
In an NT or Windows 2000 mixed-mode domain, individual accounts are Allowed or Denied access.
In a native Windows 2000 domain, control access using the remote access policy. It is by default set to deny access.
Negotiation mode: allow
Access mode: all
Address request mode: deny
Broadcast name resolution: disabled
Assignment method: auto
To add an entry to the routing table using scriptfilex:
To set time limits for sessions, use the “Routing and Remote Access” MMC console, Properties for the RRAS server, Profile, Dial-in Constraints.
By default, the Windows 2000 system event log only contains RAS errors. To control the level of RRAS data captured ...
RRAS servers that use Windows accounting store authentication events
into log files within folder
To set RRAS to output activity data to trace logs, configure tracing in the registry.
RRAS configured to use one of these formats:
To send multicast audio and video through an intranet, create an IP-in-IP tunnel interface:
To stop PPP logging:
Add, set (update), and delete entries in -alias configuration files.
Modem logs are contained in %systemroot%\Modemlog_model.txt. It is automatically overwritten unless you adjust the logging settings using Control Panel applet “Phone and Modem Options”.
The Terminal Services client software is a “super-thin client”. it sends keystrokes and mouse movements to the Terminal server, which manipulates the data locally and passes back the display. This brings Windows desktops to machines that cannot run Windows, such as legacy desktops including Win16, Macintosh, and Unix.
Terminal Services contains its own methods for licensing clients that log on to Terminal servers. This enables users to simultaneously log on to multiple Terminal Server sessions from different desktops.
The Terminal Services licensing method is separate from the method used for Windows 2000 Server clients.
With Windows 2000, Terminal Services is a built-in feature of Windows 2000 Server.
Terminal Services Licensing includes four primary components:
Terminal Services is enabled in either Remote Administration mode or Application Server mode. Remote Administration allows you to administer a Windows 2000 Server computer remotely over any TCP/IP connection. You can administer file and print sharing, edit the registry, or perform any task as if you were sitting at the console. Remote Administration installs only the remote access components of Terminal Services. It does not install application sharing components, which means you can use Remote Administration with little overhead. Terminal Services allows up to two concurrent Remote Administration connections. No additional licensing is required, and you do not need a license server. In Application Server mode, you can deploy and manage applications from a central location. You can install applications directly on the Terminal server, or you can use remote administration. After an application is deployed in Terminal Services, clients can connect through a remote access connection, a LAN or WAN, and from many types of clients. Client licensing is required when deploying a Terminal server as an application server. Each client computer must have the Terminal Services Client Access License as well as the Windows 2000 Server Client Access License .
The three standard permission levels for Access Control Settings:
There are no group policies to control Terminal Services connections.
Terminal Services uses TCP port 3389, so make sure that's open on your firewalls such as IPCop.
Your first name:
Your family name:
Your location (city, country):
Your Email address:
Top of Page