Re: How do I configure RFCs for SNC communication?

Hello Filipe,

Thank you for your response.  I had seen that page before and, while it may have helped with determining the format for SNC names, it doesn't say anything about certificates and whether or not it is necessary to loadcertsfrom other systems that each system will be communicating with.  Does that mean that loading these other certificates isn't necessary?

I stated in my original post that I attempted to load thecerts for SBX into SD2 and loaded thecerts for SD2 into SBX.  This morning, after following the link you provided, I decided to go into SNC0 and define all systems and servers for our environment.  For systems with more than just the Central Instance, I defined all of the app servers for that system there.  They were all defined using the same format that I mentioned before:

p:CN=<FQDN>,OU=<SAP Customer ID>,OU=<Long Company Name>,O=<Short Company Name>,L=<City>,SP=<State>,C=<Country>

I then went back to SM59 and tested the connection again.  This time the error was slightly different:

So, now, instead of "A221021F:Server refuses certif", I'm receiving "A2200202:Actual server name di" which, when not cut off, is "A2200202:Actual server name differs fromrequested one.".  I don't understand whichnames it's talking about.  I assume one is the SNC Partner name I gave after I clicked on the SNC button, but what is it comparing itwith?  Do I need to change the format for the SNC Partner name, whatever it's comparing it with, or both?

Any help you can provide is, of course, muchappriciated.

Thanks,

Jeff