Share via

Administration tools in mixed environments

  • Article

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

Administration tools in mixed environments

A mixed environment contains a combination of at least two of the following: servers running Windows NT 4.0 with Remote Access Service (RAS), servers running Windows NT 4.0 with Routing and Remote Access Service (RRAS), servers running Windows 2000 and Routing and Remote Access, and servers running members of the Windows Server 2003 family and Routing and Remote Access.

The platforms use different administration tools, as follows:

  • With Windows 2000 and the Windows Server 2003 family, you use Routing and Remote Access or the Netsh command-line utility.

  • With servers running Windows NT 4.0 with RRAS, you use the Routing and RAS Admin administrative tool.

  • With servers running Windows NT 4.0 with RAS, you use the Remote Access Admin administrative tool.

The following sections describe the capabilities and behavior of each of these administrative tools when they are used to administer a platform for which they were not designed.

Using Routing and Remote Access to administer a server running Windows NT 4.0 with RRAS

You can use Routing and Remote Access to administer a server acting as a router and running Windows NT 4.0 with RRAS. However, due to the differences in configuration and features, you cannot do the following:

  • Configure the remote access properties. On Windows NT 4.0, you must configure these properties on the server running Windows NT 4.0 with RRAS through Network in Control Panel.

  • Install or remove the Routing and Remote Access service.

  • Run Telnet.

  • Configure remote access policies.

  • Configure logging.

  • Configure dial-in hours.

  • Configure demand-dial filters.

  • Install IGMP or network address translation (NAT) routing protocols.

  • Obtain multicast statistics.

  • Configure TCP/IP or IPX settings.

Notes

  • IPX routing is not supported on servers running the Windows Server 2003 family version of Routing and Remote Access.

  • The IPX/SPX protocol is not available on Windows XP 64-bit Edition (Itanium) and the 64-bit versions of the Windows Server 2003 family.

Using Routing and Remote Access to administer a server running Windows NT 4.0 with RAS

You cannot use Routing and Remote Access to manage a server running Windows NT 4.0 with RAS. When you select a server running Windows NT 4.0 with RAS, the Remote Access Admin administrative tool is started.

Using Netsh to administer a server running Windows NT 4.0 with RAS or a server running Windows NT 4.0 with RRAS

You cannot use the Netsh command-line utility to manage a server running Windows NT 4.0 with RAS or a server acting as a router and running Windows NT 4.0 with RRAS.

Using Routing and RAS Admin to administer a server running Routing and Remote Access

You cannot use Routing and RAS Admin to manage the routing components of Routing and Remote Access. When you select a server running Routing and Remote Access configured as a router, the router is displayed. However, there are no routing nodes and you cannot configure the routing components.

Using Routing and RAS Admin to administer a server running Windows NT 4.0 with RAS

You cannot use Routing and RAS Admin to manage a server running Windows NT 4.0 with RAS. When you select a server running Windows NT 4.0 with RAS, the Remote Access Admin administrative tool is started.

Using Remote Access Admin to administer a server running Windows NT 4.0 with RRAS or a server running Routing and Remote Access

You cannot use Remote Access Admin to manage a server acting as a router and running Windows NT 4.0 with RRAS or the routing components of Routing and Remote Access. When you select a server acting as a router and running Windows NT 4.0 with RRAS or a server running Routing and Remote Access, Remote Access Admin displays the "Remote Access Service is not started on the selected server" message.