3687014 - SNC error in ABAP RFC "A2200202 - Actual server name differs from requested one"

• The error information can be found in the error trace logs from the CommonCryptolib traces.

*** ERROR => SncPEstablishContext() failed for target='p:CN=<SID_PRD>, O=<Org>, C=<Country>' [/bas/754_R 3637]
*** ERROR => SncPEstablishContext()==SNCERR_GSSAPI [/bas/754_REL/sr 3604]
GSS-API(maj): Miscellaneous failure
GSS-API(min): A2200202: Actual server name differs from requested one.
Unable to establish the security context
target="p:CN=<SID_PRD>, O=<Org>, C=<Country>"
<<- SncProcessInput()==SNCERR_GSSAPI
*** ERROR => ThSncIn: SncProcessInput (SNCERR_GSSAPI) failed [thxxsnc.c 1267]
*** ERROR => ThSncIn: ThSncSend failed (19) [thxxsnc.c 1391]
RFC> ABAP Program: <ABAP Program> (Transaction: <Transaction>)
RFC> User: <User> (Client: <Client>)
RFC> Destination: <DestinationName>
RFC> Called function module: RFC_PING 

• SAP NetWeaver ABAP  
• SAP NetWeaver Application Server for SAP S/4HANA  
• ABAP PLATFORM - Application Server ABAP

error code a2200202, actual server name differs, snc name mismatch, system refresh, gss-api failure, secure network communication, snc identity parameter, rfc connection error, target server name incorrect, sap logon configuration, snc name configuration , KBA , BC-MID-RFC , RFC , BC-IAM-SSO-CCL , CommonCryptoLib , BC-SEC-SNC-CFG , SNC Configuration for ABAP , Problem