Nah, I think the answer has to be using a supported browser. These enterprise systems are so picky about their browsers, it's like they live in the 90s or something.
Wait, are we sure it's not just a matter of using the correct port? I mean, who would design a web interface that doesn't work on the standard HTTPS port? That's just asking for trouble.
Hmm, I bet the answer is to load a third-party certificate. Cisco gear always needs some special certificates, right? It's like they don't trust the built-in ones.
Bethanie
6 days agoLilli
10 days agoLanie
15 days agoGeorgeanna
16 days agoVirgina
18 days agoGeorgeanna
22 days ago