Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Data Center Expert : Error when launching the web interface of modbus discovered devices from DCE web client

EcoStruxure IT forum

Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure IT
  • EcoStruxure IT forum
  • Data Center Expert : Error when launching the web interface of modbus discovered devices from DCE web client
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
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.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Cory_McDonald
Admiral Cory_McDonald Admiral
124
Jef
Admiral Jef Admiral
108
gsterling
Captain gsterling Captain
71
APC_Steve
Captain APC_Steve Captain
62
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to EcoStruxure IT forum
Anonymous user
Not applicable

Posted: ‎2020-09-07 01:07 AM

0 Likes
1
1066
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-09-07 01:07 AM

Data Center Expert : Error when launching the web interface of modbus discovered devices from DCE web client

Hi team, 

 

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 ?

 

Thanks, 

 

François

Attachments
Screenshots.zip
Labels
  • Labels:
  • Data Center Expert
  • Tags:
  • english
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic
Reply 1
Cory_McDonald
Admiral Cory_McDonald Admiral
Admiral

Posted: ‎2020-09-11 05:52 AM

0 Likes
0
1036
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2020-09-11 05:52 AM

@Anonymous user,

 

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.

 

Kind Regards,

Cory

  • Tags:
  • english
Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

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.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of