Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
Hi all!
The above mentioned problem topic has already been discussed many times here on EcoStruxure IT. An excellent example of this problem can be the topic of ieslmarketing I.e., if the NetBotz-4.x appliance is in DCE private LAN, then full access to its web-GUI is impossible: the reasons for this problem are discussed in the above topic.
I also encountered this problem many times. But as a result of experiments with the web-GUI NetBotz-4.x appliance (firmware v.4.6.2), I found an excellent workaround - instead of using the standard web-address http://your_netbotz_address it is necessary to use the "hidden" web-page http://your_netbotz_address/pages/index.html. On my screenshot, for example, is presented NetBotz-4.x Advanced View GUI via DCE privateproxy (HTTPS):
As you can clearly see from the screenshot, in an external browser we got an analogue of the Advanced View GUI. This interface is somewhat limited in functionality compared to the standard APC Advanced View software. But all the main tabs, important for monitoring (i.e., except for the Setup tab) are fully accessible and work normally. The only thing I could not verify is the surveillance on the Cameras tab, since I do not have cameras. But I think that this will also work.
I would like to remind you that, for example, in the latest version of DCE-7.5.0, the launch of the web-GUI NetBotz-4.x appliance is possible only through an external browser, rather than an internal DCE browser:
I hope this tip will be useful to many in the work 😀.
With respect.
Link copied. Please paste this link to share this article on your social media post.
Hi spezialist,
What firmware revision are you using on the 450? Yes, older firmware on the v# NetBotz did use that older V2 style web page and it had no issues with the private proxy. I tested your suggestion directly on a NetBotz 570 using http://your_netbotz_address/pages/index.html. and all I see is a 404 error.
Please note that "570-1" is in my hosts file pointing to the correct address for that unit.
When I hit the web page as usual (http or https) it shows the newer page as expected so I know it is on-line:
That specific appliance is running version 4.6.1. It's possible that it was inadvertently enabled in a specific version but I don't believe it is supposed to be the case. I'd like to double-check.
Steve
Link copied. Please paste this link to share this article on your social media post.
Hi Steven Marchetti,
Perhaps this depends on the hardware revision of a particular NetBotz-4.x appliance model.
Specifically, in my case, everything works fine, for example, see two screenshots of the same device:
With respect.
Link copied. Please paste this link to share this article on your social media post.
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.