Re: URGENT - Very Puzzled - IIS Authentication
- From: Kevin Jones <kjonesNOSPAM@xxxxxxxxxxx>
- Date: Thu, 24 Aug 2006 21:27:44 +0100
And if you read his post it says:
>> As part of our Group Policy all client XP PCs have thier IE home page set to
>> http://intranet.ourdomain.com which is the URL to our intranet.
so when they open their browser it will go there by default!
Juan T. Llibre wrote:
Given that it's an intranet app, and that all your clients are within your.
network, instruct your users to go to http://sguk-web1 to enter the intranet.
While you sort things out regarding the naming issue, that will cover your *ss.
Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Bren" <m> wrote in message news:uXy6CH7xGHA.4972@xxxxxxxxxxxxxxxxxxxxxxx
Hi All
My appologies for the URGENT shout but I need to get this sorted by 06:00 GMT otherwise I am going to have 150 screaming intranet users moaning at me.
Win 2k Server
ASP.NET 2
I have just deployed our shiny new ASP.NET 2 Intranet app and want to use Integrated windows authentication at IIS level with "windows" authentication in web.config.
I have put the tick in "Integrated Windows Authentication" in the directory security tab of the website in IIS and taken the tick out of the "Anonymous Access"
As part of our Group Policy all client XP PCs have thier IE home page set to http://intranet.ourdomain.com which is the URL to our intranet.
The win2k intranet server is called sguk-web1 with an IP of 192.168.0.9
Users log onto the local area network as normal using thier windows logon, authenticating against active directory.
The problem I am getting is as follows:
When a user opens up IE which takes them to the URL stated they get a log on dialogue to enter thier network username and password again, which I don't want to happen I just want it to go straight to the intranet and have windows handle all authentication and authorization in the background.
To puzzle matters further if the user types in http://sguk-web1 then everything works as it should do and windows does everything in the backgroud.
But if the user types in http://192.168.0.9 then we get the same issue as if they had gone to the URL http://intranet.ourdomain.com .
Any suggestions?
- Follow-Ups:
- Re: URGENT - Very Puzzled - IIS Authentication
- From: Juan T. Llibre
- Re: URGENT - Very Puzzled - IIS Authentication
- From: Bren
- Re: URGENT - Very Puzzled - IIS Authentication
- References:
- URGENT - Very Puzzled - IIS Authentication
- From: Bren
- Re: URGENT - Very Puzzled - IIS Authentication
- From: Juan T. Llibre
- URGENT - Very Puzzled - IIS Authentication
- Prev by Date: Customize Visual Studio .NET Web Setup Projects
- Next by Date: Re: Problems with Theme and Context.RewritePath()
- Previous by thread: Re: URGENT - Very Puzzled - IIS Authentication
- Next by thread: Re: URGENT - Very Puzzled - IIS Authentication
- Index(es):
Relevant Pages
|