I need help with the security and I am not an expert. I had everything running fine on my development machine. To keep it simple, my dev machine points to the production database for validation. If I run the configuration utility, I see a single user in a role. As I said, all was groovy on the dev machine, I could run the app, log in, and have the logged in routine redirect to the proper directory. I deployed to the host server and cannot log in. Remember, the web.config is identical because the database being used is the same one. I figure somethings messed up on the host, so I'll keep working on the dev machine and figure out the security problem on the host later. Well, now, I can't log in on the dev machine either! I have a routine to route the user when they are logged in, if I set a break point in that routine it never gets called. It's like my machine forgot how to log in. The web.config is unchanged (as far as I know), and the configuration application still shows the one user in the one role. So the configuration utility can find the user database, but the login control cannot.

I don't want to be a security expert, I just want it to work. Can anyone help? I am so frustrated with this security model and how touchy it is, but it is all I got to use.

Thanks. 

Ok, I solved one problem. I can now log on to the dev machine. I deleted the Login control and recreated it and all works on the dev machine. However, I still cannot log on the deployed site. Any ideas why I can't log on when the site is copied to the host? The web.config doesn't change, the database reference doesn't change.