SAP Note 605795 Windows Terminal Server connection in remote support Note Language: English
Version: 11 Validity:
Valid Since 06.04.2005
Summary Symptom You require a Windows Terminal Server connection for your system so that you can benefit from support sessions.
Other terms Windows Terminal Server, Remote Connection, STFK
Reason and Prerequisites o
You already have set up a SAProuter connection to SAP (SAPserv X).
o
The relevant Windows Terminal Server (WTS) application is available on your server or PC. This note provides no information about setting up the SAProuter connection 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 the service 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 is maintained!
Setting up your SAProuter: o
Check the route permission table (saprouttab) with which the SAProuter is working. In the relevant table, create an entry in the form: P 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" 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 wild card (*) releases only ports 3200 to 3299. Save the changed file. 28.11.2012
Page 1 of
5
SAP Note 605795 Windows Terminal Server connection in remote support 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 address or, 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 service connection 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 service name.
o
Select a contact person. You can also implement a port that differs from the standard here. If you are using the standard application port, select 'Standard port'.
o
Copy the selection using the 'Transfer' button at the end of the list.
o
Use the 'Back' button to return to the 'Service connection XXX' screen.
System
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 that entries are needed for the additional SAProuter only if two SAProuters have to be used in series (one after the other) on your page.
o
Save the entries.
Opening the service connection:
28.11.2012
Page 2 of
5
SAP Note 605795 Windows Terminal Server connection in remote support o
Click the 'Maintain connections' button (at the bottom of the page).
o
You can open the relevant service connection by clicking the icon in front of the service. Select the required opening times (the default value is eight hours). You can maintain the contact person manually or by using the list of registered persons.
Setting up the service, maintaining the system data and opening the service connection 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 to the installation selection.
o
Access the list of systems by double-clicking the installation number.
o
Access the system ID by double-clicking the relevant system. The system now displays a list of active services and the servers that are 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 which you can select the contact person. You can also implement a port that differs from the standard here select the port you require.
o
Expand the list of contact persons by clicking the icon on the right, and select the contact person by double-clicking.
o
Activate the service by saving it (disk icon). The service now appears 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 that entries are needed for the additional SAProuter only if two SAProuters have to be used in series (one after the other) on your page.
28.11.2012
Page 3 of
5
SAP Note 605795 Windows Terminal Server connection in remote support 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 the list 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 the set-up connection, open a customer message under the component XX-SER-NET-HTL.
Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: SAP to Customer system
Released for Customer 06.04.2005 13:28:34 German Recommendations/additional info Installation information XX-SER-NET-HTL Problems with remote access from
Secondary Components: XX-SER-NET Network connection
The Note is release-independent
Related Notes Number 1768122 1723672 1635304 1634757 1624510 1522293
28.11.2012
Short Text Portal upgrade failed with OpenSQLException SAP Enterprise Portal 5.0 - Specific Component Note Central note for HANA support connections Guided Self Service 'Performance Optimization' Portal Web Dynpro Integration - Component-specific Note Navigation - Specific Component Note
Page 4 of
5
SAP Note 605795 Windows Terminal Server connection in remote support Number 1498779 1486692 1415371 1399580 1398273 1380993 1265687 1262169 1178684 1178631 1178628 1178624 1178546 1127799 1038511 1029476 1019929 984434 882316 769478 752505 692114 655502 494980 35010
28.11.2012
Short Text Preparing Java-based systems for Support Services Prerequisites for messages opened in the EP-KM* components REACH: Setting up service connections for SAP Support MDM 7.1: Information required for ABAP API issues Federated Portal Network (FPN) - Specific Component Note SAP NetWeaver Portal - Specific Component Note Application Integration - Specific Component Note Requirements for error analysis in NW WPC No service connection:"SNC processing failed" No service connection: "connection to partner broken" No service connection: "internal error" No service connection: "Partner not reached" (sapserv#) No service connection: "route permission denied" Central Note:WebDynpro for Visual Composer: NetWeaver 7.1 CE Error Analysis for NW Visual Composer 7.0 MDM 55: Information required for ABAP API issues SAP Java Upgrade Problems How to speed up customer message processing We need further information to analyze your problem Remote connection with XI systems SAP System Installation Problems WTS with STFK - tscstart.exe is missing Windows Terminal Server - required applications for support Remote Support for an Enterprise Portal Service connections: Composite note (overview)
Page 5 of
5
