ASPNET user with network resources elsewhere on a domain

I've been trying to workout how, without impersonation, I can allow an application running under the default ASPNET user to access a network resource (SQL Server/ADAM) not on the same physical machine.

It seems that because the ASPNET user is a local user not a domain user I can't setup windows authentication on the network resource. That seems to leave impersonation which MS et al say is unwise.

Have I mised something here?

Regards,

Steve.Yes.

You can change the user running the asp.net process. ONly the STANDARD user is a local user. It CAN also be a domain user, per your choosing.