I agree with Britta. I would edit the robot.cfg as described with the correct information, and set the controller loglevel to 5 and logsize to 5000, but also clear out the niscache folder of all content, then stop the robot, then start it. Check the log on startup.
Steve
------------------------------
[Designation]
[City]
------------------------------
Original Message:
Sent: 07-13-2019 07:47 AM
From: Britta Hoffner
Subject: Robot can't connect to the hub
Hello John, it is controlled in the Nimsoft\robot\robot.cfg file name and ipaddress is has. You may have to look at this values and adjust if necessary.
robotname
hubip
robotip
hubrobotname
Kind regards,
Britta
Original Message:
Sent: 07-12-2019 03:43 PM
From: John Paolo Santos
Subject: Robot can't connect to the hub
Hey Guys,
Newbie here, just want to ask this one. Should the server installed with robot be able to reach the hub via its domain name? The server w/ robot had some changes in its DNS settings and now can't connect to the hub. What you guys think?
Thanks