This question was originally posted on DCIM Support by mark.higgs on 2018-04-10
I am able to ping my 4 netbotz 355 but i am not able to login.
What could be causing this?
Solved! Go to Solution.
This answer was originally posted on DCIM Support by Steven Marchetti on 2018-04-10
There could be a number of reasons for this. Someone could have changed the port on the device. They could have disabled HTTP in favor of HTTPS. There could be an IP conflict where you're actually pinging something else. Could be blocked by a firewall. There are too many possibilities and not enough info to give you an exact answer.
First, try accessing the device using a browser. If you can't, what I would then suggest is have someone on-site using a cross-over cable attempt to access the device. Try both using the Advanced View application and a web browser. If they can, then it's network. If not, you may want to reset the configuration on the device using k-base FA158175. This will cause loss of any configuration. Using a short (they seem to work better) USB cable, follow the document to configreset the device. Then follow k-base FA308010 and set the IP of the device again. I suggest using Configuration Option 3 - Terminal Emulation.
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!