Hi Scott,
Thanks for answering. Yes they are completely separate machines. I can
impersonate an interactive user if needs be, the application is secured and
I have free reign over the server it will run on if I need to do anything
hacky, but I was kinda hoping I wouldn't have to.
Beats me why I need to physically impersonate a user, I imagine explorer
doesn't change the account it's running under to view a network share.
The application I'm writing makes files, then using the username, password,
domain in it's database connects out to machines on their admin share and
deploys them (lots of security to think about I know). I'm considering
writing some client software now for the machines it deploys to - C# just
doesn't seem to be up to the task.
Cheers,
Matt
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:hd********************************@4ax.com...
Hi Matt:
I take it the second machine is not in the same domain?
One approach would be to create a local user account on the remote
machine with the same username and password as a user on the web
server.
Mapped drives are a no-no in ASP.NET because they only load for an
interactive user, i.e. a user logged into a visible desktop, which the
asp.net worker process does not.
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 18 May 2005 14:00:30 +0100, "Matt Dockerty" <Ps reply to
group> wrote:
Hi,
I'm trying to connect to a network share using a username / password /
domain of my choosing.
I've tried the WindowsIdentity.Impersonate route but can only impersonate
the users on the local machine / domain using this method.
I could go about creating actual mapped drives but I'd much rather
connecttemporarily to a UNC share without affecting the system configuration.
I've Googled this one to death. Does anybody have any ideas?
Thanks,
Matt