One of our pain points with over 1500 robots is what seems to be the unstable behaivour of the robot reporting an IP address as 127.0.0.1 (seems to have increased in frequency since robot ver 5.52) . On Windows servers this requires the restart of the robot AT the server not via the Infrastructure Manager. Nimsoft support indicates best practice is to hard code the IP address but this is unworkable in our environment. (hmm never seen this documented!) Right now we are required to manually review the IM searching for robots reporting IP address 127.0.0.1 as the status shows okay and no alarms occur. We are unable to communicate to the robot from the IM when in this condition. We could write a script to scan the HUBs looking for this condition but why not fix the issue? Anyone else see this issue?