M
Marianne
Had 1.1 configured so that a process I was launching on a web server would
have access to a domain controller in a different domain. This was
accomplished by setting the <processModel> tag in machine.config to use the
ASPNET account with a specified password. Then on the DC created an
identical account with the same password (pass-through authentication).
After switching to ASP.NET 2.0, I get "Access Denied" messages when trying
to access the DC (it's just calling dnscmd.exe which connects to the DC for
purposes of getting zone information out of DNS). Since pass-through
authentication isn't working now, this means either the aspnet_wp.exe
process isn't being created like it used to be or there is/are additional
security mechanisms in place that didn't exist in 1.1. If anyone has any
idea how to make this work I'd greatly appreciate any input. Thanks.
Marianne
have access to a domain controller in a different domain. This was
accomplished by setting the <processModel> tag in machine.config to use the
ASPNET account with a specified password. Then on the DC created an
identical account with the same password (pass-through authentication).
After switching to ASP.NET 2.0, I get "Access Denied" messages when trying
to access the DC (it's just calling dnscmd.exe which connects to the DC for
purposes of getting zone information out of DNS). Since pass-through
authentication isn't working now, this means either the aspnet_wp.exe
process isn't being created like it used to be or there is/are additional
security mechanisms in place that didn't exist in 1.1. If anyone has any
idea how to make this work I'd greatly appreciate any input. Thanks.
Marianne