Cannot Login Urgent Help

[johnquebec]

Hi all,

After several days looking for a fix I have run out of ideas on how to fix this problem which supposed to be a very simple one. I have a site that is pwd restricted by a login page. The user must authenticate first in order to get to the site. The login is working perfectly for more than 70% of the users BUT there are a certain number of IE users that cannot login.

The problem they find is that after entering the correct login and password and click submit, the page goes back to the login page and not error is specified. So the actual authentication appears to take place although it just doesn't let the user go in.

To the best of my knowledge it looks like it is a client side problem, cookie related. I found a few similar post online about this problem and the recommendation was to clear the client browser cookies (i.e. http://weblogs.asp.net/rosherove/archive/2004/03/01/81799.aspx) . That DID NOT fix the problem at all. For sure must be something I could do on my code OR in the .js to fix this problem. It just doesn't seems rigth to leave to the client user to handle the clean up of the cookies, etc.. Besides, that didn't work...

What else? well I read about the .NET 1.1. SP1 bug about having a wrong .js file. Although that problem had to do with the button and was not actually the problem I am explaining, I also did follow those instructions and updated my client .js files, (just in case a miracle happens).

So after doing all that the miracle didn't happen yet. Now I am here looking for a charity soul that will enlight me with the answer to my problem.

Thanks

[mmetzger]

The poster in the other thread is right, it's a cookie issue. A few options:

1) If it's XP SP2, try disabling the Windows Firewall. It usually doesn't cause this problem, but I've seen stranger

2) Make sure they're not working Offline

3) Clear the cache as well as the cookies, and completely close all open IE windows

4) Look for any Spyware / Adware / AV / Personal Firewall products. These can do things you wouldn't expect, including stopping cookies.

5) Verify the security settings on the browser. It doesn't need to be low, but medium high / high will block cookies.

6) As a last resort, you can always use cookieless sessions (the session id is written into the url and parsed accordingly) but beware these have some problems of their own.