EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-10-05 02:16 AM
Hi All I have 2 questions that i could do with assistance:
1. I have a DCE that wont launch to a device that is sat on its Gb2 network. All device launch credentials are correct and i can web browse to the device but DCE fails to launch. I have looked at all the KB articles regarding this but to no avail!
2. When i try to launch to the Botz750 it launches in a new external browser but i get bad gateway. why is it only the 750 that opens an external browser can this be adapted to other devices?
TIA
Mike
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-10-12 09:24 AM . Last Modified: 2022-10-12 10:00 AM
Hi @Mike-Sutton
1: What protocol are you using to launch to the generator? If https, it should launch (even if it doesn't log in).
If HTTP, it may not. Have you verified HTTP is enabled on the DCE server? With 7.9.x, it is disabled by default.
Do you know if the device has any active-X or other controls that need to be launched to view the web page? If so, it won't make it through the proxy and won't work no matter the setting in DCE.
Did you have this working in a prior version of DCE?
Do you have other devices that launch OK?
To troubleshoot this more in-depth, you may want to contact support directly as things like a packet capture (which I would not request on an open forum and may require a remote session) may help with troubleshooting this.
2: You will get this error when launching to a 750 on the private LAN if you don't have the proxy set to TLS 1.2. The bad thing there is that if you have it set to 1.2, older devices that require 1.0 or 1.1 won't work.
As for launching using an external browser, that's an option listed under "File"-->"Client Preferences"-->"Browser Settings"
Thanks,
Steve
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-10-11 11:42 PM . Last Modified: 2022-10-12 09:09 PM
In DCE 7.9.0 and newer, the Launch to Device option does not work for NMC 1 devices that use HTTPS on the DCE private network. Connect a computer to the DCE private network to directly access the device's web user interface. mywakehealth
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-10-12 02:25 AM
Hi It is a 3rd party device (deepsea generator controller) and accessing the private LAN remotely is not possible. I am trying to understand why it doesn't work and is there any settings that can be changed as it seems that where DCE acted as a proxy to access the Private network from the Public side this seems to have stopped
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-10-12 09:24 AM . Last Modified: 2022-10-12 10:00 AM
Hi @Mike-Sutton
1: What protocol are you using to launch to the generator? If https, it should launch (even if it doesn't log in).
If HTTP, it may not. Have you verified HTTP is enabled on the DCE server? With 7.9.x, it is disabled by default.
Do you know if the device has any active-X or other controls that need to be launched to view the web page? If so, it won't make it through the proxy and won't work no matter the setting in DCE.
Did you have this working in a prior version of DCE?
Do you have other devices that launch OK?
To troubleshoot this more in-depth, you may want to contact support directly as things like a packet capture (which I would not request on an open forum and may require a remote session) may help with troubleshooting this.
2: You will get this error when launching to a 750 on the private LAN if you don't have the proxy set to TLS 1.2. The bad thing there is that if you have it set to 1.2, older devices that require 1.0 or 1.1 won't work.
As for launching using an external browser, that's an option listed under "File"-->"Client Preferences"-->"Browser Settings"
Thanks,
Steve
Link copied. Please paste this link to share this article on your social media post.
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.