By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,014 Members | 1,012 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,014 IT Pros & Developers. It's quick & easy.

Spawning a process with ASP.NET 2.0 beta 2

P: n/a
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
Nov 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi Marianna:

Is the 2.0 project running under IIS or under the VWD thingy?

One tip is that in 2.0 you can spawn a process with a specific
username and password using the Process class. This might make things
easier for you in either case.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 7 Jun 2005 16:25:23 -0400, "Marianne" <Ma******@nospam.nospam>
wrote:
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


Nov 19 '05 #2

P: n/a
It's running under IIS. After trying the Process method earlier, I received
some error that I can't specifically recall--I'll recreate that test and
post the results. In the meantime, this was absolutely working correctly
under ASP.NET 1.1 but as soon as the upgrade happened it fails every time
now. So I'm at a loss to explain the problem.

Marianne
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:3i********************************@4ax.com...
Hi Marianna:

Is the 2.0 project running under IIS or under the VWD thingy?

One tip is that in 2.0 you can spawn a process with a specific
username and password using the Process class. This might make things
easier for you in either case.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 7 Jun 2005 16:25:23 -0400, "Marianne" <Ma******@nospam.nospam>
wrote:
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

Nov 19 '05 #3

P: n/a
Hi Scott,

I am developing an asp.net application using c# and asp.net 2.0 beta 2. I
started developing this page usign beta1. In beta 1 I have written some code
in Page_LoadComplete(object sender, EventArgs e) events of page. It was
working fine. But after I installed beta 2.0 Page_LoadComplete events is not
firing at all. Can u guide me how can I achieve this goal?

Thankx in advance.
Shailesh.

"Scott Allen" wrote:
Hi Marianna:

Is the 2.0 project running under IIS or under the VWD thingy?

One tip is that in 2.0 you can spawn a process with a specific
username and password using the Process class. This might make things
easier for you in either case.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 7 Jun 2005 16:25:23 -0400, "Marianne" <Ma******@nospam.nospam>
wrote:
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


Nov 19 '05 #4

P: n/a
Shailesh,

Please don't post the same question multiple times
as replies to different posts.

That only creates confusion in the newsgroup.

I addressed your question as a reply to your first message.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================

"Shailesh" <Sh******@discussions.microsoft.com> wrote in message
news:FC**********************************@microsof t.com...
Hi Scott,

I am developing an asp.net application using c# and asp.net 2.0 beta 2. I
started developing this page usign beta1. In beta 1 I have written some code
in Page_LoadComplete(object sender, EventArgs e) events of page. It was
working fine. But after I installed beta 2.0 Page_LoadComplete events is not
firing at all. Can u guide me how can I achieve this goal?

Thankx in advance.
Shailesh.

"Scott Allen" wrote:
Hi Marianna:

Is the 2.0 project running under IIS or under the VWD thingy?

One tip is that in 2.0 you can spawn a process with a specific
username and password using the Process class. This might make things
easier for you in either case.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 7 Jun 2005 16:25:23 -0400, "Marianne" <Ma******@nospam.nospam>
wrote:
>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
>


Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.