topic NAC Server NAM Communication Problem in Network Security

NAC Server NAM Communication Problem

guillermo.rojas — Fri, 21 Feb 2020 12:12:04 GMT

I have this issue:

- From CAM y can configure de CAS

- The CAS and CAM have correct certificates

- In the CAM /perfigo/access/tomcat/logs/nac_access_log:

2010-12-27 16:50:02.934 -0500 ERROR com.perfigo.wlan.common.HttpClientResource - Post to:https://10.255.254.70/wlan/jmx/autoconnect.jsp

j avax.net.ssl.SSLException: HelloRequest followed by an unexpected handshake message

at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) [na:1.6]

- I have other NAS in the same NAM with no problems.

Someone has had a similar problem?

Guillermo

Re: NAC Server NAM Communication Problem

guillermo.rojas — Wed, 29 Dec 2010 20:37:55 GMT

- Logs CAM in /perfigo/control/tomcat/logs/nac_manager.log:

2010-12-29 14:58:51.493 -0500 ERROR com.perfigo.wlan.web.admin.ConnectorClient - Communication Exception : Could not connect to the Clean Access Server

java.rmi.ConnectException: Connection refused to host: 10.1.220.240; nested exception is:

java.net.ConnectException: Connection refused

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) [na:1.6.0_12]

at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) [na:1.6.0_12]

at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) [na:1.6.0_12]

at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) [na:1.6.0_12]

at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) [na:1.6.0_12]

- Los CAS in /perfigo/access/tomcat/logs/nac_server.log

2010-12-29 15:24:22.741 -0500 ERROR com.perfigo.wlan.common.HttpClientResource - Post to:https://10.255.254.70/wlan/jmx/autoconnect.jsp

java.net.ConnectException: Connection refused

at java.net.PlainSocketImpl.socketConnect(Native Method) [na:1.6.0_20]

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [na:1.6.0_20]

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) [na:1.6.0_20]

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) [na:1.6.0_20]

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) [na:1.6.0_20]

at java.net.Socket.connect(Socket.java:529) [na:1.6.0_20]

at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550) [na:1.6]

at com.perfigo.wlan.common.HttpClientUtil$SSLProtocolSocketFactory.createSocket(HttpClientUtil.java:49) [perfigo.jar:na]

at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) [commons-httpclient-3.1.jar:na]

at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361) [commons-httpclient-3.1.jar:na]

Version CAM: Clean Access Manager 4.7.2 2010/02/05

Version CAS: Clean Access Server 4.7.3 2010/09/15

Re: NAC Server NAM Communication Problem

Tiago Antunes — Thu, 30 Dec 2010 13:50:21 GMT

Hi,

It looks like you are trying to manage a CAS running a different version than the CAM:

Version CAM: Clean Access Manager 4.7.2 2010/02/05

Version CAS: Clean Access Server 4.7.3 2010/09/15

Please make sure that both CAM and CAS are running the same version.

HTH,
Tiago

If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.