When connecting to remote system, once again asking user & password details

Question

hi
I created one RFC in R/3 system, with the same logical system name of xi, giving all technical and logon details.
When I click on remote logon to enter into xi system,it is once again asking user logon details. After entering the details it is allowing into the xi system. Directly it is not entering into remote system when I click remote logon button.
I created both sides (in xi and R/3) and checked the same thing. Both sides I am getting the same problem. it is showing client name correctly but user and password name it is displaying the same server information. like if I am connecting from R/3 to XI means it is showing XI client number but R/3 user and password. Once after I change user and password and press enter it is going into remote system.
Could someone please help me on this?
Thanks in advance and best regards,
1234

Answer 1

hi lavanya
Provide the user with the corresponding authorization or avoid using the protected users DDIC and SAP*
check below
Trusting Transaction SMT2                                                    
The trusting transaction SMT2 (or SM59 ® RFC ® Trusting Systems) constructs a list of all trusting systems that have been established for this trusted system. Here, a logon and authorization check for the current user and client is performed, using the destination TRUSTING_SYSTEM@S00 that has been automatically created.      
This basically corresponds to transaction SM51, if you use Remote Login to perform a logon on a different application server.                                                                               
If problems occur while setting the destination TRUSTING_SYSTEM@S00 (such as host name or service information), you either have to create a new destination for your needs, and then enter the host name or service information using SAP router strings, or adjust the network settings of the server. To correct the problem in transaction SMT2, you have to adjust the network configuration of the server. As this transaction is only to be used for test purposes, in this case you could also choose to ignore the error.                                                              
To perform a logon as a different user or client, you have to create a new RFC destination with a trusted option set.                                                                
In this scenario, the following error text in SMT2 can be ignored:
No authorization to log on as a trusted system (Trusted RC=0)
If the host name contains the character '_' (as in "my_host"), then the generation of the related trusting system destination may lead to incorrect settings. This problem can be corrected by implementing Support Package SAPKB46D09 (see below). For earlier releases, the changes required to correct the problem can be made manually.
regards
kummari