Cannot assign Access Manager IDP configuration to Identity Server

Successfully installed Access Administrator and Identity servers on seperate hardware boxes. The Identity server auto imported successfully.

After creating an identity server configuration, the final task is to assign that configuration to the identity server IP address. Doing so would cause the IDP server health check to fail with the message:

"Configuration to load could not be found in directory"

Make sure that the IDP server can resolve the DNS name of the Access Administrator server and vice versa.

When assigning a configuration to the IDP server, JCC needs to establish a TCP connection from the IDP server to the Access Administrator server. In cases where it cannot resolve the DNS name of the Access Administrator server, or cannot communicate with it, then the above error will occur assigning a configuration to the IDP server.

The JCC log files will also show the following exception prior to displaying the "Configuration to load could not be found in the directory:" error.

Connection refused to host: ; nested exception is:
java.net.ConnectException: Connection refused
java.rmi.ConnectException: Connection refused to host: 192.168.10.60; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
at com.novell.jcc.client.JCCClientImpl$JCCRMIClient_Stub.getServiceName(Unknown Source)
at com.novell.jcc.server.JCCServerImpl.doCommand(y:3369)
at com.novell.jcc.handler.CommandHandler$_A.run(y:3303)