Check the following:
Using telnet utility on the host where IM is running, test connectivity to controller port on robot. For example:
telnet 192.168.2.4 48000
If the telnet succeeds:
Check the Messages section in IM for a timeout related to getting the probe configuration. If there is a timeout message, increase the Probe Request-> Timeout Value in IM Tools from the Options menu. Set the value to a slightly higher value, and retest the failing operation. Repeat if necessary.
If the telnet fails:
Check to see if there is a firewall between the robot and the machine where IM is running and/or a firewall on the robot host.
If there is any NAT'ing involved, meaning the registered robot IP is not reachable directly but only through a NAT'ed interface, add the following parameters to your robot.cfg file for the robot where you are unable to reach the probes.
robotip_alias = <NAT'ed IP through which Robot can be reached>
robotip = <Robot's Local IP address>
robotip = 192.168.2.4 <= Local IP of the robot host
robotip_alias = 172.16.1.4 <= NAT'ed IP of robot host