problem with cookies using response.redirect
I have a website with some secured pages in it. When a user enters his username and password they are checked in a database and a session id, session profile and session timeout are created independently for every user. My institute uses microsoft box as a server which they upgraded recently. With the earlier server I used response.redirect once the user was authenticated and the cookie carried all the information about the session, but since the upgrade I need to enter the username and password atleast 3 to 4 times before the cookie carries the information to the next page. So I started using server.transfer instead, but as my secured pages are in different directories (but on the same server) it losses the session information if I tried to access any pages in other directories and have to enter authentication information again. The problem came about when we changed to the latest microsoft server. Can anyone please let me know why the response.redirect is not working and is there a way around it or can I make some changes to my code to keep using server.transfer.