|
Home > Archive > IIS Server Security > December 2007 > authenticate with login web control on IIS5 or IIS6
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
authenticate with login web control on IIS5 or IIS6
|
|
| david carpentier 2007-12-11, 7:32 am |
| I develop a web site using VS 2005 in C# using login webcontrol. I have
problem during deployement onto IIS 5, authentication works if I use IP @,
but not with dns name (on internal network) on my local computer (XP PRO).
I've got a simimlar problem with internet network on a server 2003 and IIS6,
but in this case both does not work.
The login status does not get the user name and the login page is always
shown, when use IP@ or localhost the default page is shown and login status
ok.
I use framework 2, anonymous authentication on IIS, aspnet SQL database.
It might be helpfull if someones know what I can do to solve this problem.
David
| |
| David Wang 2007-12-12, 7:31 am |
| On Dec 11, 2:40 am, david carpentier <david
carpent...@discussions.microsoft.com> wrote:
> I develop a web site using VS 2005 in C# using login webcontrol. I have
> problem during deployement onto IIS 5, authentication works if I use IP @,
> but not with dns name (on internal network) on my local computer (XP PRO).
> I've got a simimlar problem with internet network on a server 2003 and IIS6,
> but in this case both does not work.
> The login status does not get the user name and the login page is always
> shown, when use IP@ or localhost the default page is shown and login status
> ok.
>
> I use framework 2, anonymous authentication on IIS, aspnet SQL database.
>
> It might be helpfull if someones know what I can do to solve this problem.
>
> David
It sounds like you have a networking/name related issue with the DNS,
possibly preventing the login control from finding the SQL server,
thus causing all sorts of strange issues. IP or localhost won't go
through DNS and thus appear "fine".
At this point, it looks like a DNS name issue related to your
networking environment. It does not look like an issue related to
authentication, IIS5, IIS6, nor ASP.Net. In fact, you have already
proven that things work if you take network names out of it. Without
specific details, it is difficult to resolve proprietary networking
environment issues.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
| |
| carpentier 2007-12-13, 7:32 am |
| Thank you for your help,
In fact I find another point, using firefox and computer domain name (like
http://COMPUTER1/virtualfolder/default.aspx ), login works
properly, but not with IE. It seems like authentication cookie ".ASPXAUTH"
doesn't work on IE6 or IE7 (I
validate cookie on it) and DNS name.
My SQL server is targeted because I trace the connection, I've test the web
site with VS debugger (using Web deployment project). On a local computer
(using computer domainename) out of a network the problem is still the same.
I am actually searching for authentication problem with the Autodetect
cookie of ASP.NET, something like that, but without any conviction...
David
"David Wang" <w3.4you@gmail.com> a écrit dans le message de news:
688681d5-a014-4f24-b013-b2269fd47e4a@e23g2000prf.googlegroups.com...
> On Dec 11, 2:40 am, david carpentier <david
> carpent...@discussions.microsoft.com> wrote:
>
>
> It sounds like you have a networking/name related issue with the DNS,
> possibly preventing the login control from finding the SQL server,
> thus causing all sorts of strange issues. IP or localhost won't go
> through DNS and thus appear "fine".
>
> At this point, it looks like a DNS name issue related to your
> networking environment. It does not look like an issue related to
> authentication, IIS5, IIS6, nor ASP.Net. In fact, you have already
> proven that things work if you take network names out of it. Without
> specific details, it is difficult to resolve proprietary networking
> environment issues.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
| |
| David Wang 2007-12-13, 7:32 am |
| I would still suggest starting with software configuration of network
names and network name resolution. All your evidence shows that the
issue has nothing to do with web browsers like IE6/IE7/Firefox nor web
servers like IIS5/IIS6.
You have shown that IIS5, IIS6, and IE6, IE7, and Firefox all works
under variety of networking related situations.
If you disconnect a computer from the network, unless the computer
domain name is hooked to loopback it will fail in the same way --
suggesting network name.
Resolution of computer domain name has to do with NETBIOS, once again
network name resolution.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Dec 13, 1:10 am, "carpentier" <techni...@adents.com> wrote:
> Thank you for your help,
>
> In fact I find another point, using firefox and computer domain name (like=
http://COMPUTER1/virtualfolder/default.aspx), login works
> properly, but not with IE. It seems like authentication cookie ".ASPXAUTH"=
> doesn't work on IE6 or IE7 (I
> validate cookie on it) and DNS name.
> My SQL server is targeted because I trace the connection, I've test the we=
b
> site with VS debugger (using Web deployment project). On a local computer
> (using computer domainename) out of a network the problem is still the sam=
e.
> I am actually searching for authentication problem with the Autodetect
> cookie of ASP.NET, something like that, but without any conviction...
>
> David
>
> "David Wang" <w3.4...@gmail.com> a =E9crit dans le message de news:
> 688681d5-a014-4f24-b013-b2269fd47...@e23g2000prf.googlegroups.com...
>
>
>
[vbcol=seagreen]
[vbcol=seagreen]
s[vbcol=seagreen]
>
..[vbcol=seagreen]
>
>
>
>
>
>
> - Show quoted text -
| |
| carpentier 2007-12-14, 1:29 pm |
| Ok, I found the trouble. In fact, computer names was declared with
underscore character, this character is not taken into account with DNS
other than Microsoft one's. I change computer name from "STAT_XXXX" to
"STAT-XXXX" and know everything works fine.
Thank you for your help.
David
"David Wang" <w3.4you@gmail.com> a écrit dans le message de news:
fa186cf4-a59c-4ba3-89b1-0428326fbee9@i29g2000prf.googlegroups.com...
I would still suggest starting with software configuration of network
names and network name resolution. All your evidence shows that the
issue has nothing to do with web browsers like IE6/IE7/Firefox nor web
servers like IIS5/IIS6.
You have shown that IIS5, IIS6, and IE6, IE7, and Firefox all works
under variety of networking related situations.
If you disconnect a computer from the network, unless the computer
domain name is hooked to loopback it will fail in the same way --
suggesting network name.
Resolution of computer domain name has to do with NETBIOS, once again
network name resolution.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Dec 13, 1:10 am, "carpentier" <techni...@adents.com> wrote:
> Thank you for your help,
>
> In fact I find another point, using firefox and computer domain name
> (likehttp://COMPUTER1/virtualfolder/default.aspx), login works
> properly, but not with IE. It seems like authentication cookie ".ASPXAUTH"
> doesn't work on IE6 or IE7 (I
> validate cookie on it) and DNS name.
> My SQL server is targeted because I trace the connection, I've test the
> web
> site with VS debugger (using Web deployment project). On a local computer
> (using computer domainename) out of a network the problem is still the
> same.
> I am actually searching for authentication problem with the Autodetect
> cookie of ASP.NET, something like that, but without any conviction...
>
> David
>
> "David Wang" <w3.4...@gmail.com> a écrit dans le message de news:
> 688681d5-a014-4f24-b013-b2269fd47...@e23g2000prf.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
|
|
|
|
|