SA/NA Integration Failure - Connection refused to host

  • KM1313079
  • 10-Jan-2012
  • 14-May-2013


The article treats a problem with the integration of Network Automation with Server Automation, the error "Connection refused to host:" is seen.


When trying to integrate Network Automation (NA) with Server Automation (SA), the following error message is seen in the twist logfiles on the SA core when the NA server tries to connect to it.

2011-12-09 05:09:10,424 SEVERE Thread-37 [com.opsware.nas.impl.NasSession] [open] NAS Communication Error: Could not connect to server:<IP address of SA CORE>, LoginException: javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host:; nested exception is: Connection refused]


When the NA server attempts to connect to the SA server, the SA server will attempt to connect back to the NA server based on the NA server name.  In this instance, a incorrect entry in /etc/hosts on the SA server was resolving the NA server name to "".  However, any incorrect name resolution result could cause this error.


Ensure that the name resolution of the NA server points to the correct IP address for the NA server used for SA/NA communications.