You need to remember that ASP.NET is inherently a "StateLess" environment.

There are few ways to accomplish this.

1. Use ViewState.  Add a Property to the Default page - UserIP - that gets/saves the IP in the Viewstate, and add code to actually get the Users IP if the Viewstate is Nothing.

2. Use a Cookie.  Look in DNNMembership to see how the roles are "stored" in a "portalroles" cookie, so they do not have to be retrieved from the Database on every page request, but only on being authenticated, and then save the value in the context so it is available to all controls during this Request's Lifetime.

---

Charles Nurse Chief Architect Evoq Content Team Lead, DNN Corp. Want to contribute to the Platform project? - See here

MVP (ASP.NET) and ASPInsiders Member

We have our own database tables with ipaddresses that grant the user certain permissions within the application (assign to roles). So the app grabs the ipaddress and authenticates against it if it is on our database list. I found out that I hadn't deleted one of the cookies after all and that was causing the problem. cheers