WTS Note

24.01.2010 Page 1 of 5

SAP Note 605795 - Windows Terminal Server connection inremote support

Note Language: English Version: 11 Validity: Valid Since 06.04.2005

Summary

SymptomYou require a Windows Terminal Server connection for your system so thatyou can benefit from support sessions.

More TermsWindows Terminal Server, Remote Connection, STFK

Cause and Prerequisites

o You already have set up a SAProuter connection to SAP (SAPserv X).

o The relevant Windows Terminal Server (WTS) application is availableon your server or PC.

This note provides no information about setting up the SAProuterconnection or the WTS application.

Solution

Setting up the WTS connection is done in two parts:

1. Setting up the SAProuter

2. Setting up the service, maintaining the system data and opening theservice connection on the SAP Service Marketplace or the SAP front end(formerly OSS)

Note that SAP employees can log on only to servers whose system data ismaintained!

Setting up your SAProuter:

o Check the route permission table (saprouttab) with which theSAProuter is working.

In the relevant table, create an entry in the form:P <IP Address SAP-SR> <IP Server> 3389

For example:P 147.204.2.5 10.10.10.10 3389

or for SNC encryption (SAPserv2):KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <IP Server> 3389

For example:KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.10.10.10 3389

A generic entry in the form P * * * is insufficient since the wildcard (*) releases only ports 3200 to 3299. Save the changed file.

24.01.2010 Page 2 of 5


o Import the changed table into the SAProuter using the saprouter -n' command, or restart the SAProuter.

o Check whether the SAProuter can access the target host (IP addressor, if necessary, host name) on the corresponding application port.If not, set up the network accordingly.

Note that all services support only the current SAProuter software.Update your SAProuter software if necessary.

Setting up the service, maintaining the system data and opening the serviceconnection on the SAP Service Marketplace:

o Log on to the Service Marketplace using the alias'serviceconnection' (URL:http://service.sap.com/serviceconnection).

o Click 'Maintain Connections'.

o Select the required system by clicking the system ID.

Setting up the service:

o Select 'Maintain Services'.

o Select the WTS service by clicking the icon in front of the servicename.

o Select a contact person. You can also implement a port that differsfrom the standard here. If you are using the standard applicationport, select 'Standard port'.

o Copy the selection using the 'Transfer' button at the end of thelist.

o Use the 'Back' button to return to the 'Service connection SystemXXX' screen.

Maintaining system data:

o Click 'Display system data' (at the bottom of the page).

o Select the 'DB Server', 'Appl. Server' or 'Other Servers' tab.

o If necessary, click the 'Create server' button.

o Enter the required data (in particular, the IP address). Note thatentries are needed for the additional SAProuter only if twoSAProuters have to be used in series (one after the other) on yourpage.

o Save the entries.

Opening the service connection:

24.01.2010 Page 3 of 5


o Click the 'Maintain connections' button (at the bottom of thepage).

o You can open the relevant service connection by clicking the iconin front of the service. Select the required opening times (thedefault value is eight hours). You can maintain the contact personmanually or by using the list of registered persons.

Setting up the service, maintaining the system data and opening the serviceconnection in the SAP R/3 front end

o Log on to the SAP R/3 front end.

o Use the 'Service' and 'Service connections' buttons to navigate tothe installation selection.

o Access the list of systems by double-clicking the installationnumber.

o Access the system ID by double-clicking the relevant system. Thesystem now displays a list of active services and the servers thatare maintained for this system.

Setting up the service:

o Expand the 'Service selection' entry.

o When you double-click the WTS service, a window opens from whichyou can select the contact person. You can also implement a portthat differs from the standard here select the port you require.

o Expand the list of contact persons by clicking the icon on theright, and select the contact person by double-clicking.

o Activate the service by saving it (disk icon). The service nowappears in the list of connections (above).

Maintaining system data:

o Click the 'System data' button above.

o Select the 'DB Server', 'Appl. Server' or 'Other Servers' tab.

o Click the 'Create/Change' button (pencil icon).

o If necessary, click the 'Create server' button (blank page icon)and select 'Create server'.

o Enter the required data (in particular, the IP address). Note thatentries are needed for the additional SAProuter only if twoSAProuters have to be used in series (one after the other) on yourpage.

24.01.2010 Page 4 of 5


o Save the entries (disk icon).

Opening the service connection:

o Double-click the required service.

o Enter the required opening times and the contact person (from thelist of fields).

o Save the entries (disk icon).

o The system now displays the WTS connection as 'Open'.

If you have any questions about setting up the connection of testing theset-up connection, open a customer message under the componentXX-SER-NET-HTL.

Header Data

Release Status: Released for CustomerReleased on: 06.04.2005 13:28:34Master Language: GermanPriority: Recommendations/additional infoCategory: Installation informationPrimary Component XX-SER-NET-HTL Problems with remote access fromSAP to Customer system

Additional Components:XX-SER-NET Network connection

The Note is release-independent

Related Notes

Number Short Text

1415371 REACH: Setting up service connections for SAP Support

1399580 MDM 7.1: Information required for ABAP API issues

1398273 Federated Portal Network (FPN) - Specific Component Note

1380993 SAP NetWeaver Portal - Specific Component Note

1265687 Application Integration - Specific Component Note

1262169 Requirements for error analysis in NW WPC

24.01.2010 Page 5 of 5


Number Short Text

1178684 No service connection:"SNC processing failed"

1178631 No service connection: "connection to partner broken"

1178628 No service connection: "internal error"

1178624 No service connection: "Partner not reached" (sapserv#)

1178546 No service connection: "route permission denied"

1127799 Central Note:WebDynpro for Visual Composer: NetWeaver 7.1 CE

1038511 Error Analysis for NW Visual Composer 7.0

1029476 MDM 55: Information required for ABAP API issues

1019929 SAP Java Upgrade Problems

984434 How to speed up customer message processing

882316 We need further information to analyze your problem

769478 Remote connection with XI systems

752505 SAP System Installation Problems

655502 Windows Terminal Server - required applications for support

494980 Remote Support for an Enterprise Portal

35010 Service connections: Composite note (overview)

Documents

WTS Note