Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey
Netbotz 750 congelado
EcoStruxure IT Forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
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 InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-07-2807:28 PM
Netbotz 750 congelado
Instale a un cliente 2 equipos Netbotz 750 y los equipos se congelan cada determinado tiempo y no envían notificaciones; lo que se realizo un reseteo a valores de fábrica esto se realizo el 11 de junio y hoy volvió a congelarse el equipo. Sucedió lo mismo que en la primer ocasión; lo que hay que hacer es apagar y encender de energía el equipo.
Hay algo que pueda hacer para validar la operación? Que debo hacer para que trabaje de forma continua?
I installed 2 Netbotz 750 and the equipment is froze and did not send notifications, it was determined to send to factory values and reconfigure, this was done on June 11 and today it froze and no longer responds. This same thing happened previously and what is done is to turn it off and on, but this is not something that should happen normally. Is there anything I can do to validate the operation? The installed firmware versions are 5.2.4.15