Hosted with PowerDNN.
Domain A, we have a fully functioning portal with Dynamic Login installed (however I don't think we're even using it).
Domain B, is a clone of Domain A. However we cannot login using any registered user, including Host!
PowerDNN tracked it down to be an issue with Dynamic Login.
Response from them
==================================
have investigated the issue and confirmed it is a module issue. It appears to pertain to the Dynamic Login module.
After cloning the site and renaming all portal aliases, Dynamic Login is still trying to set the login cookie for testmyteen.com and not seemysitenow.com. Here is the relevant response trace data:
Set-Cookie: DotNetNukeAnonymous=77af8d1d-xxxx-444b-xxxx-fc1bdbd4f3c6; domain=www.testmyteen.com; expires=Tue, 22-Feb-2011
This cannot happen with the core DNN Login provider as it goes by portal alias. As we are not sure how Dynamic Login determines this, I would suggest contacting the vendor of that module for assistance. ==================================
I'm at a loss, I've looked through the tables, and I haven't seen any setting to tell Dynamic Login what URL to use. However I have found in the table "DataSprings_DynamicLogin_RoleGroup" a URL column, however I have no idea to what table this corresponds.
HELP!