cancel
Showing results for 
Search instead for 
Did you mean: 

Connection to SAP

odysseas_spyroglou
Participant
0 Kudos

Hello,

We are trying to configure a Solution manager for our company but we have stack with a problem. We cannot create the remote connection to SAP!

The steps that we have followed are:

We have successfully installed Solution manager 4.0 sr2, Kernel patch number: 179.

We have send the remote connection data sheet to SAP through service.sap message and we have received the answer.

We have downloaded and install the sapcrypto library and the appropriate certificate.

We have successfully started the saprouter as a service following the steps of the 525751 SAP note.

We have created the saprouttab file with the following entries:

KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *

KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.18 3200

KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.18 3389

KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.18 23

P 192.168.1.18 194.39.131.34 3299

D * * *

We can ping and telnet 194.39.131.34 from our saprouter server.

We have changed the technical parameters of the transaction OSS1 with our saprouter internal name and IP (instance no 99)

When we are trying to logon we must choose one group from a list of

availiable groups: "1_public, 2_Japanese, do_not_use, EWA, REPL, SPACE"

Whatever we select, we get the folowing error " sapserver2a route permission denied (our_public_IP to 147.204.100.55, sapdp01)

When we are trying to test the SAPOSS connection from transaction sm59 the attempt is successful.

Can someone help us?

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

You are done.

You can´t "logon" any more to the OSS system, this was switched off years ago. That access is only via RFC, if the SM59 test connection works you´re fine.

Markus

Answers (0)