> Your screen shot is from a mobile app. [...]
Looks to me as if the "a mobile app" is a web browser. Have you ever
seen a web browser on an Android phone? Have you ever seen some
different kind of app which displays a URL that way?
> [...] Have you tried a browser?
Read it again?
> [...] this has happened all 3 different computers running 2 different
> browsers and amobile phone with the exact same results.
Back in the real world, I don't know what's causing this problem, but
I'd guess some kind of firmware corruption. The broken-image-link icon
(as well as the general failure) hints at some fundamental confusion.
> [...] had some problems [...]
Elaborate?
Assuming that your current firmware is corrupt (for some unknown
reason), then I'd want to load some firmware into the thing again, and
hope that that solves the problem (until whatever corrupted it the first
time recurs). Sadly, if the management web server files are corrupt,
I'm not sure how to do that in any elementary way. The TFTP recovery
scheme might be good, _if_ you can get the thing into a receptive mode,
but I don't know how to do that if the thing thinks that it's working
properly. Some lower-level technique, like a serial-port interface,
might be needed in a case like this.
You might try specifying some specific web pages (in your browser)
instead of that "BRS_index.htm", like, say:
adv_index.htm
UPG_upgrade.htm
(I'm not sure how much those names might change from one firmware
version to the next. I got those from "V1.0.1.74_1.0.1". Any idea
which version yours has?)
Of course, if the NVRAM is becoming VRAM, then I'd expect similar
problems in the future (with increasing frequency), even if you can find
a way to stand it up now. But, without running the experiment, that's
just more speculation.
Any chance of a bad power adapter?
