https://localhost:1131

Secure socket port.

sorry https://locahost:1311

dislexic typsit

Thanks Grasshopper62, but it goes beyond that.  Perhaps I should have been more specific.

With HTTPS, I then receive the accept certificate screen, which I respond yes to, I then get the login prompt.  I enter the locally defined user/password with adminstrator rights, and submit.

The servlet runs (or attempts to) and comes back with 'Login Failed'.

Here's the last URL, after all the redirection:  https://localhost:1311/servlet/OMSALogin?msgStatus=false

It never authenticates.  Anyway to log, trace, debug?

Please reread the original post for background.

Again, Thanks.

Sorry, tester25.  No, I haven't figured out the root cause.  It does not work on the OMSA Mgmt. Svr., which is a Windows Server 2003 Std. Ed. with SP1 system.  IE 6.0 SP1 using Enhanced Security.

But, I am able to access and use the product when I connect from another machine.  It is a WinXP Pro 2002 SP2 system, with IE 6.0 SP2.

So, my working theory is that it has something to do with the IE version on the Win2k3 system; more specifically IE Enhanced Security.

Since I can access and it works, just not on the OMSA Server, I'll just let this issue drop.

Hopefully, the tidbit of information about Internet Explorer and/or Win2k3 will help others in the future.