S
Strange Cat
Hi everyone!
I have a weird problem with FormsAuthentication.
I have an app that works just fine with FormsAuthentication.
The user requests the homepage, he is redirected to login page, then enters
valid username and password that are checked versus a db table, if the info
is ok i execute SetAuthCookie(xxx, False) then i open a new window which
displays the home page, all is working fine...
The problem occurs on a machine named PIPPO_PC ONLY if I login in WinXP
using user PIPPO, so the situation is:
Computer Name: PIPPO_XP
WinXP User Name: PIPPO
After logging in Windows with user name PIPPO, if I try to login on my app
after opening the new window with the home page, the LOGIN page of my app is
display instead of the home page, even though the login procedure on my APP
goes ok... now this is weird...
Looks like that ASP.NET cannot set the cookie if the computer name and user
name are similar...
Does any one have a similar problem???
Thanx in advance
ASC
I have a weird problem with FormsAuthentication.
I have an app that works just fine with FormsAuthentication.
The user requests the homepage, he is redirected to login page, then enters
valid username and password that are checked versus a db table, if the info
is ok i execute SetAuthCookie(xxx, False) then i open a new window which
displays the home page, all is working fine...
The problem occurs on a machine named PIPPO_PC ONLY if I login in WinXP
using user PIPPO, so the situation is:
Computer Name: PIPPO_XP
WinXP User Name: PIPPO
After logging in Windows with user name PIPPO, if I try to login on my app
after opening the new window with the home page, the LOGIN page of my app is
display instead of the home page, even though the login procedure on my APP
goes ok... now this is weird...
Looks like that ASP.NET cannot set the cookie if the computer name and user
name are similar...
Does any one have a similar problem???
Thanx in advance
ASC