Solved: LMS 3.1 - Cannot Login After Joining Windows OS to Domain

tadams7541 · ‎02-01-2010

I installed LMS 3.1 on a Windows 2003 Enterprise R2 machine before ever joining this machine to the domain. I got it all setup and configured and things were working great. After joining the windows box to the domain I can still reach the login page, but once I type in my credentials I get a "Page cannot be displayed" error in IE. It looks like the initial request gets through, tries to redirect, and then just quits.

I've verified that all of the services LMS requires are running.

I was thinking that maybe something changed after joining it to the domain that may have affected Apache, or caused some configs to no longer matched. I already checked to verify that the hostname was changed to the FQDN due to the domain joining.

Any help with this is very appreciated!

Marvin Rhoads · ‎02-17-2010

A common thing to watch for in both servers and clients that are members of a Windows domain is the Group Policy Objects (GPOs) that are pushed to the server or client behind the scenes. Internet Explorer settings especially are commonly modified by GPOs and often with the effect of restricting functionality of the browser when browsing to sites that are not configured consistent with organizational policy (which may or may not be conveyed to all users).

I have seen this often when browsing to devices with self-signed certificates (which are obviously not from a trusted root CA) and not being able to override IE's objection to such certificates as the policy is GPO-enforced. Of course, installing certificates from trusted third party providers can be another can of worms altogether.... ( I spent over two weeks resolving that issue with my LMS installation recently - and that's WITH TAC support.)

View solution in original post

Joe Clarke · ‎02-01-2010

Try logging in with firefox. Post the error you get there. That will be more helpful than IE.

tadams7541 · ‎02-17-2010

Thsi issue has been resolved. It turns out that after joining to a domain that has FIPS 140-2 enforced, it broke the web piece of LMS. Once this was disabled, normal operations continued.

Marvin Rhoads · ‎02-17-2010

A common thing to watch for in both servers and clients that are members of a Windows domain is the Group Policy Objects (GPOs) that are pushed to the server or client behind the scenes. Internet Explorer settings especially are commonly modified by GPOs and often with the effect of restricting functionality of the browser when browsing to sites that are not configured consistent with organizational policy (which may or may not be conveyed to all users).

I have seen this often when browsing to devices with self-signed certificates (which are obviously not from a trusted root CA) and not being able to override IE's objection to such certificates as the policy is GPO-enforced. Of course, installing certificates from trusted third party providers can be another can of worms altogether.... ( I spent over two weeks resolving that issue with my LMS installation recently - and that's WITH TAC support.)

tadams7541 · ‎02-18-2010

Thanks for the comments, mklemovitch!

I've had my troubles with TAC as well, and I've come to find that this support forum is INCREDIBLY helpful with issues like this