terminal server

By default Terminal Server and Windows 2000 Terminal Services uses TCP port 3389 for client connections. Microsoft does not recommend that this value be changed. However, if it becomes necessary to change this port, follow these instructions (Note: additional ports used by win2000 services is 445).

By default, local printers with COM, LPT, or USB ports will be redirected when a TS RDP 5 client logs on to a TS session. However, when clients connect to a TS session and the clients have network printers configured, the client's network printers are not redirected. If TS users need to print to a network printer, they may have two options. 1) The client may set up the network printer on the TS computer through the Add Printer Wizard and enable users to select and print to that printer. 2) Map a local port (LPT#) on the client side to the network path and install a printer driver on the TS computer.

If TS doesn't redirect the client printers, check the following:
1. Make sure the TS has the printer driver. If not, install it.
2. If the server does not find a matching driver name from those drivers that are currently installed, you may need to add the drive name into ntprint.inf. ntprint.inf is located in the %systemroot%inf.
3. We find some multifunction printer can't be redirected, especially if it uses DOT4 port. In this case, you may try to keep the DOT4 printer and create another printer (load printer drive only) on LPT1.
4. If you want to redirect a network printer, you cam map it by using net use lpt# \\servername\printername /persistent:yes command.

If the TS server you are connecting to has Windows Printer Mapping disabled, you can map your client LPT ports manually. To do this, go to TS Start>Settings>Printers>Add Printer>Local printer, lear the Automatically detect and install my Plug and Play printer check box, and then click Next. Under Port Selection, you see several ports named TSxxx. These are client mapped ports. Click the port that corresponds to your client computer's name and port, and then click Next. Continue to follow the instructions on your screen to complete the printer installation.

To display a list of sessions and their session IDs, type query user at the command line on the server, and then press ENTER. The following output is displayed.

To initiate a Remote Control session: run a Terminal Server Client session to the Terminal Server. When the session is running, start Terminal Services Manager. Connect to the server on which the user is logged on. Right-click the user's name, and then click Remote Control. By default, the user is prompted to accept the Remote Control session. When the user accepts your request you can interact with the user's environment.

How to switch applications between TS and local

When running full screen, you can use 1) Ctrl+Esc to show icons bar and then pick up the local application; 2) Alt+Tab to select application you want to; 3) Ctrl+Alt+Pause to part screen or full screen

How to Switch TS Mode

If you want to switch Remote Administration Mode to Application Mode, you must remove and reinstall Terminal Services using Add/Remove Programs.

Still need help, contact consultant Your feedback and contributions to this web site

How to use shadow command to remote monitor and control another's session

You can use the shadow command to view or actively control an active session of another user. If you actively control a user's session, you can input keyboard and mouse actions for that session. Shadow command syntax: shadow {session_name | session_id} [/server:server_name] [/v]

For example, to shadow session ID 2, type shadow 2. To shadow the session rdp-tcp#3, type shadow rdp-tcp#3.

I can't reconnect after disconnecting

By default, the TS timeout settings are 120 minutes for Connection, 10 minutes for Disconnection, and 30 minutes for Idle. If a client disconnects (rather than logging off), the session is not terminated. Rather, it is held in memory so that the client can't reconnect and re-establish the session. To fix this problem, you need to change timeout settings in TS Connection Configuration.

Client can't logon

SYMPTOMS: After a TS client loses the connection to a Terminal Server, the client can't logon the Terminal Server and the TS shows the client still connects to the server. Resolution: Open Terminal Services Configuration in Administrative Tools, double-click RDP-Tcp in the Connections folder and click the Sessions tab. Click to select Override user settings and check Disconnect from session, and select 5 minutes or so.

How disable changing display

To disable Display, you have two choices. One is the Win 2000 regular way, Local Computer Policy>User Configuration>Administrative Templates>Control Panel>Display. Two, Run TS Configuration>Connections>RDP-Tcp>Properties>Environment>Client Wallpaper, check Disable Wallpaper.

"The local policy of this system does not permit you to logon interactively."

Also, you will not receive this message when you logon member and stand-alone servers since they have the users group included in the "Log on Locally" user right.

Resolutions:This issue occurs because the W2K domain controller running Terminal Services does not have the Users, Authenticated Users, or Everyone global group added to the Group Policy Object for the "Log on Locally" user right. "Log on Locally" is a required user right in Microsoft Windows NT 4.0, Terminal Server Edition and Windows 2000 Terminal Services. To modify the Group Policy Object for the domain controller, go to Administrative Tools>Domain Controller Security Policy>Security Settings>Local Policies>User Rights Assignment>Policy>Log on Locally>Add>Browse, click the appropriate group, and then click Add. After modifying the Group Policy, type secedit /refreshpolicy machine_policy /enforce at a command prompt, press ENTER, and then press ENTER.

"You do not have access to logon to this Session"

Symptoms: When trying to connect to a W2K server running Terminal Services with the Remote Administration, you may receive "You do not have access to logon to this Session" message.

Resolutions: this issue occurs because W2K server running Terminal Services with the Remote Administration mode do not permit users to logon by the default. Only two concurrent administrator accounts for server management can connect to a W2K domain controller running Terminal Services configured to use Remote Administration mode.

Resolution: use Active Directory Users and Computers to modify this setting. To do this, open Active Directory Users and Computers, check "Allow Logon to terminal server" box under the Terminal Services Profile tab of the user account.

Resolution: the server has reached its connection limit. note: Terminal Servers in Remote Administration mode allow a maximum of 2 concurrent sessions. Disconnect unused session..

Resolution: this issue occurs because the administrator has disabled logon by issuing the CHANGE LOGON /DISABLE command. In order to to enable logon, use the CHANGE LOGON /ENABLE command.

Resolution: this issue occurs because the administrator has specified a maximum connection limit, and the limit has been reached. To modify the limit, go to MMC>Terminal Services Configuration>Connections, double-click a connection, i.e. RDP-TC, then select the Network Adapter tab. At the bottom of this tab, change Unlimited connections and Maximum connections.

Resolution: this issue occurs because the administrator has disabled one or more connections. To modify this, go to MMC>Terminal Services Configuration>Connections, right-click a connection, i.e. RDP-TCP, and select All Tasks. If Enable Connection is an option, the connection is currently disabled. There will also be a red X over the icon for the specified connection when disabled.