>Frank,
>
>Since when you attempted to go directly to a page and it took you to the Login form, this would suggest that the session variable used to determine that someone is logged on is not being maintained and/or discarded. This would also explain why you just stay at the login page as you mentioned previously as you are just continually looping back because the application does not 'think' you are logged in.
>
>Not sure what to check for on this, but maybe this information will help you resolve this.
>
>Bob
>
>>I was hoping this was it, but unfortunately no. I tried manually entering a page to go to after the login, but it just brought back up the login page.
>>
>>I also tried changing my redirect code in the userlogin to use the tilde, but that didn't work either and now I am getting errors when trying to run it. I just copied the changed dll and pdb to the bin folder. Is there anything more than that when updating a web application?

I don't know enough about the comments you mention so not suggesting those are not the problem. It is one possibility for sure.

I am pretty sure his application has every page including the default with this.RequiresSecurity = true; at least the last time I saw it. This would mean just navigating to www.hisdomain.com would try to resolve to default.aspx and be re-directed automagically to the login page first. If he has set the login page as the startup page, then he is probably trying to do a Response.Redirect("/mainpage.aspx") after successful login. If that is the case, then he may have to add a "~" before the / in the url. It definately will work differently when remote as I have discovered the hard way.

I think if he just sets the Default as the startup page and then protects it the login redirection would work as is.
Tim