On a site, we installed Data Center Expert 7.8.0. We discovered devices using SNMPv1 and Modbus TCP.
Devices and DCE are all located on the same VLAN (and there is no private interface on DCE).
We noticed the following behaviour when launching the web interface of the modbus discovered devices :
- Launching device web interface from a web browser with its IP address : OK
- Launching device web interface from DCE rich client : OK
- Launching device web interface from DCE web client : NOK -> an HTML code or error is displayed instead of the device web page
Launching the web interface of SNMP discovered devices (APC and 3rd part devices) works OK in all cases.
The three modbus TCP discovered devices in this case are :
- a LOYTEC controller (cooling control)
- A genset
- Uniflair chillers
Please note that for uniflair devices, there is something more :
- chillers with the default carel web interface behave like the genset and the LOYTEC controller
- chillers with the SCHNEIDER web interface do however work properly
Could you please help understanding and troubleshooting this issue ? In the zip file attached, you will find screen shots detailing the issue. Server logs are available on request if needed.
Alternatively, is there a mean to configure DCE to bypass the privateproxy that seems to be the issue here ?
My assumption is that this is a physical appliance and that the public and private networks have similar IP schemes, which may be having DCE use its private proxy for connection. If this is a physical appliance, please provide the IP schemes of the public and private from within the DCE desktop client under: System > Server Administration Settings > Network Settings. Provide a screen capture of Public (LAN1) and Private (LAN2) [both Network A and Network B tabs].
The DCE privateproxy does not allow certain code types through such as activeX, and therefore some interfaces may not load properly, which may be the case here. The first step though is finding out why DCE is using a private proxy.
If there is no Private LAN2 tab, then the private proxy should not be used at all and you will need to work through local escalation to log and troubleshoot the issue. Also if there is a Private LAN2 tab, but it is on a different network scheme such as a 10.X.X.X network, then you will need to work with local esclation as well, as the private proxy should not be used to connect to the 192.168.X.X network, especially if those devices are connected to the GB1 (Public LAN1) port on the server.
I have also seen where customers try to use the Private LAN2 tab as the Public LAN, which can cause issues such as this. If there is no Private network the GB1 port on the server should be the only port being used. If virtual, there should not even be a 2nd NIC added to the VM, and therefore no Private LAN2 tab displayed within the Desktop Client.
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!