NMC2 not responding to HTTP

[BillP]

Just setup our SURTA3000RMXL3U last night with one add'l battery pack.
Put a 9630 NMC2 in it as well.
I can, without issue, Telnet into it and do anything I want in Telnet. It can ping anything within Telnet.
APC Firmware Upgrade Tool can see it.
I can configure it via ARP as well.

But nomatter what, nomatter which free IP I assign to it, I cannot access the UPS via HTTP and it is driving me out of my mind. I can ping it just fine but when it comes to the web admin page - nothing.

I flashed its FW from 5.0.1 to 5.0.3 which made no behavioral difference.

I ONCE - on the very first attempt - logged in via HTTP and was using it just great, but after I ran a Self Test I have yet to see a single response on HTTP at all.

I've thrice fully powered=off the UPS, I've tried using the NMC2's Reset button (which AFAIK is only for Password resetting, not a full factory default restoration?), I've reseated the NMC2 into the unit twice and nothing I'm doing is making any difference to the behavior.

With all that said I feel very unknowledgeable about UPS's so please assume nothing if you're so king to respond.
...but what am I overlooking in my shooting-in-the-dark troubleshooting process? Is this a UPS issue and not a NMC2 issue somehow?

[voidstar_apc · Accepted solution]

As a first step for troubleshooting, I would use FTP to download the config.ini file and the event log and then post them here.

What error message does your browser give when attempting to access the NMC? What happens if you try a different browser?

Additionally, using the CLI you may want to check to make sure the NMC's HTTP server is not disabled or set to HTTPS, and that it is set to use port 80.

[BillP]

Thanks for the fast reply. Now I can try something new. I'm standing in a grocery store right now but when I get him I'll VPN in and try this out. The only thing I can say immediately is that FF/IE simply give a page cannot be displayed style error-and quickly too. No timing out, it spits that out fairly quickly.

[BillP]

Awesome stuff Voidstar:
Telnet's web command showed that I had changed the HTTP port to 8080. Working late in the night helped me misunderstand exactly what I was doing: seems pretty dumb of me in hindsight but I was thinking the admin page was asking me what port to use to GET TO the web. Never did I wonder WHY a UPS would need to get to the web (maybe for firmware update notifications?) but I immediately plugged-in my proxy's port 8080 and went along my way.

What a relief - this was really irritating me!

[voidstar_apc]

I'm glad we could get it working.

Not so dumb, eventually we may need to have proxy settings on the NMC.