Newly installed windows robot. Getting the following error in Nimsoft. (Unable to reach controller: communication error). This error is a popup that occurs when I try to open the controller for that particular robot.
That usually means a firewall (on the network or on the host itself) is blocking connections to the controller, which normally listens on TCP 48000.
If the robot is on the other side of a tunnel, the connections to TCP 48000 should be coming from the hub.
If the robot is not on the other side of a tunnel, the connections to TCP 48000 should be coming from the host running the Infrastructure Manager.
You can test access to TCP 48000 by using the telnet command.
Thx again, was a firewall on the host (on the other side of the tunnel)
I've the same problem.
I already done the actions below:
1. turn off firewall;
2. there is no other application using 48000 port, just Nimsoft Controller;
3. telnet command and it works.
4. restart all the probes
5. validate the probes
I also check the logs and there is no errors, just on controller:
Aug 26 01:05:47:346  Controller: hub ALS-NIM-MONS1hub(192........) NO CONTACT (communication error)
Aug 26 01:05:48:360  Controller: hub ALS-NIM-MONS1hub(192........) NO CONTACT (communication error)
Aug 26 01:05:49:374  Controller: hub ALS-NIM-MONS1hub(192........) NO CONTACT (communication error)
Aug 26 01:05:50:388  Controller: hub ALS-NIM-MONS1hub(192........) NO CONTACT (communication error)
Aug 26 01:05:51:402  Controller: Hub ALS-NIM-MONS1hub(192........) contact established
Aug 26 01:05:51:402  Controller: primary hub changed name to ALS-NIM-MONS1dom/ALS-NIM-MONS1hub/als-nim-mons1
Aug 26 01:05:51:402  Controller: temp hub changed name to ALS-NIM-MONS1dom/ALS-NIM-MONS1hub/als-nim-mons1
Aug 26 05:06:02:764  Controller: Hub ALS-NIM-MONS1hub(192........) contact established
Do you have any suggestion with more actions to do?
In your case I'd start with a reinstall of the robot. If it is accessible from the hub, you could just drag robot_update there. The original thread was about firewall issues, so if you can't access it from your hub, I'd check firewall / nat settings
I already try to deploy robot_update and gives me this error:
'unable to connect...'
The firewall is already offline.
Do you have any suggestion?
we have the same problem,
i deployed the robot to a server and sometimes he gets answer, so in the infra manager i see him with a red bullet.
a telnet connection from the server to de nimsoftserver does'nt work, a telnetsession from the nimsoft to the server works fine.
Controller: hub HUBWSB01(10.40.10.67) NO CONTACT (communication error)
someone any idea?
One other thing to check is the IP address assigned to the robot , if you have multiple IP's on the server and you have done a automatic deployment the robot might pick any of the IP addresses . Check if it is the same IP assigned to the robot which you have used during the discovery of the server, update the robot.cfg in case its different and restart the robot
Also check the firewalls on both sides
Your issue might be different but this helped me in some cases when I faced similar error
I was having same problem and followed the steps suggested by Phani Devulapalli.
Had a look at route table and picked the appropriate IP, restarted robot.
This fixed the issue.
Thank you all.
The port 48000 - 480*
Must be available on Client and Server UIM, because when you send some probe to client or open setting some probe, the Infrastrucutre Manager will try connect on port 48000 of client, if this port isn't available on client you will receive the error "Unable to reach controller"
Unable to reach controller,
error message: communication error
What is the solution for this error ?
Issac08 As noted in earlier posts the error might arise because of multiple reasons . It could be because of the Firewall or Ports or the IP address assigned to the robot during the install . Do you still see the issue after verifying the Firewall settings , ports and IP addresses ?
Yes the above are verified and still the same error.
Try http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec000004085.aspx this helped me in most of the cases
You can also try deleting the niscache folder on the robot and try restarting the services ( this too was helpful in certain cases )
You can try the below TEC docs also
Try adding the robot's IP and name to the hosts file.