Problems depoloying application to another web site
From: Alex Kudakov (alex@avalon.ru)
Date: 08/27/02
- Next message: Paul Clement: "Re: Login Security ASP.NET - Need help on a idea - Thanks"
- Previous message: Beth Breidenbach: "Re: Forms based security without cookies?"
- Next in thread: Alex Kudakov: "Some comments..."
- Reply: Alex Kudakov: "Some comments..."
- Reply: Alex Kudakov: "I found the solution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Alex Kudakov" <alex@avalon.ru> Date: Tue, 27 Aug 2002 06:20:25 -0700
Hello, I can't understand where is the problem.
I wrote a simple ASP.NET application that access AD.
Application is running on Win2kSrv+Sp2,
named, say, "SERVER"
that is member server ia a domain, not a DC,
server account is trusted for delegation,
nothing changed in default .net configs, etc.
When I deploy my application to default
web site it accesses AD without a problem.
Identity Impersonate in application's web.config
is set to true, Authentication "Windows NT".
I decide to setup additional web site
for hosting that application. I set a new
IP address on "server", add record to DNS, call
my new site "SUPPORT" (in dns i have one host record
for "server", another host record for "support",
not an alias), created web site in IIS manager, bound
it to this IP, installed my application.
Settings between Default and SUPPORT sites are the same.
But my application does not work.
It work's when I log on locally. But where remotly
it failes while accessing AD.
What could be the reason?
Kind Regards,
Alex
- Next message: Paul Clement: "Re: Login Security ASP.NET - Need help on a idea - Thanks"
- Previous message: Beth Breidenbach: "Re: Forms based security without cookies?"
- Next in thread: Alex Kudakov: "Some comments..."
- Reply: Alex Kudakov: "Some comments..."
- Reply: Alex Kudakov: "I found the solution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
