All probes except controller on one robot show inactive or not running when opened

book

Article ID: 34408

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Issue:

All probes except controller on one robot show inactive or not running when opened.

Environment:

Robot/Controller

Cause:

Firewall rules were blocking the port for probe communication

Resolution:

Firewall rules that were in place were specifically for the nimbus.exe program (robot) and not "All Programs."

Once the Windows Firewall rule was changed on the Primary hub to "All Programs" not just the robot (nimbus.exe), the probes opened without displaying "inactive" or "not running."

Noting that not all of the robots were using first probe port of 48000 also changed the setting in the controller->Advanced to use first probe port number of 48004 for the remaining robots to keep the range more consistent/manageable.


Environment

Release:
Component: CAUIM