Running 4.0.2 on localhost only. I messed around a bit with my portal aliases on installation and somehow screwed things up. Login didn't work on the Child portal so I added a login module to the home page. In the parent (host) portal, clicking on "Login" or "Register" takes me Ok to the proper User Account/Login or the Registration modules respectively. However, in my Child portal these links just drop me back to the home page (whether I'm already logged in or not).

In the Child portal I temporarily set up a page for registration and dropped a User Account module into it, and tried the same for a login page using an Account Login module, but I can't seem to bridge the gap between the Register/Login features on the initial page and the modules that should automatically come up. (This might be a just a distraction from the real issue.)

Parent portal is http://localhost/DotNetNuke_2 and the Child (in directory Portals/1) is http://localhost/DotNetNuke_2/albigen, which has a Default.aspx file in it. In the Portals directory I have three subdirectories: _default, 0 and 1. The latter two just have image files in them.

In Module Definitions everything appears to be default. One control in the Account Login module and one in the User Account module.

Where am I confused? Thank you.

Yes. Have added a bunch of pages and rearranged them with no problems. I haven't tried all the modules yet, but all the modules I have added, and rearranged on the pages, seem to be working fine. The Login module and the Registration modules work if I put them on a page. The only problem is that the url under the Register and Login "menu" point to the home page, so they go nowhere.