S
Silmar
Hi!
My testing environment is made of three W2k3 servers. One is DC, on second
there is IIS with my ASP.NET 2.0 application, third one is just a client. In
web.config I've got <authentication mode="Windows" /> and <identity
impersonate="TRUE" />. In IIS I disabled anonymous access, only integrated
authentication is left.
If I access my application from second server everything works OK. But when
I access it from third one I've got an error message which I paste below.
What I found is an event from application event log, source ASP.NET
2.0.50727.0 and event ID 1309. In it's description I found that thread
serving my request "Is impersonating: False". After a little googling I
found almost acceptable solution. I enabled anonymous access on IIS but as
user I set domain user. And that helped, now I can access my application
remotly and it works. However I lost information about user who is accessing
it, now it is always user I set for anonymous access.
Does anyone know how to solve this?
Regards
Tomek
My testing environment is made of three W2k3 servers. One is DC, on second
there is IIS with my ASP.NET 2.0 application, third one is just a client. In
web.config I've got <authentication mode="Windows" /> and <identity
impersonate="TRUE" />. In IIS I disabled anonymous access, only integrated
authentication is left.
If I access my application from second server everything works OK. But when
I access it from third one I've got an error message which I paste below.
What I found is an event from application event log, source ASP.NET
2.0.50727.0 and event ID 1309. In it's description I found that thread
serving my request "Is impersonating: False". After a little googling I
found almost acceptable solution. I enabled anonymous access on IIS but as
user I set domain user. And that helped, now I can access my application
remotly and it works. However I lost information about user who is accessing
it, now it is always user I set for anonymous access.
Does anyone know how to solve this?
Regards
Tomek