How to Use a Modem with Terminal Services (270857)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server

This article was previously published under Q270857

SUMMARY

This article describes how to use a modem with Windows 2000 Terminal Services or Windows Terminal Server 4.0.

MORE INFORMATION

Terminal Server clients and Terminal Server console sessions can access modems that are directly connected to the Terminal server. Terminal Server clients can use the Network and Dialup Connections tool or Routing and Remote Access Service (RRAS) to use modems that are connected to the Terminal server.

Network and Dialup Connections

Modem sessions that are initiated with the Network and Dialup Connections tool are determined by the user who has dialed in. When the user logs off, the modem disconnects all connections including any other Terminal Server clients that are using the same connection. This behavior occurs while the user is at the console, or in a Terminal Server client session.

Routing and Remote Access Service (RRAS)

Modem sessions that are initiated from a RRAS connection are based only on traffic. Users may log off without affecting the modem connection. A demand-dial interface can be created in the RRAS with a static route. The static route assigned to the demand-dial connection instructs RRAS to dial when traffic that is destined for this remote network is detected.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

178993 How to Use Static Routes with Routing and Remote Access Service

NOTE: When you establish a dial-up connection from the Terminal server, routing is affected for clients as well as the Terminal server. This behavior occurs because the default gateway is changed.

Modification Type:MinorLast Reviewed:1/26/2006
Keywords:kbHardware kbinfo kbTermServ KB270857