Hi Cathi,

I reviewed the article that Dave provided the link to. I am not using domains. I am using a simple network configuration. How does this effect the line:

<identity impersonate="true" userName="mydomain\myusername"

>If you are using Win2K you may also have to allow the ASPNET to act as part
>of the operating system (Windows XP and .NET server don't require this
>setting). Select Start/Programs/Administrative Tools/Local Security Policy.
>Then select Local Policies/User Rights Assignment/Act as part of the
>operating system. Add the local ASPNET account and everything should work
>OK.

Is this on the web server or the computer where I want to access the data?

Regards and thanx,
Neil

>
>
>
>>I have an asp.net application that needs to write to a win2k network drive.
>>
>>I have given the user, ASPNET, full control to the network share (More than generous I thought.) I still cannot read or write from the share. Even a System.IO.File.Exists() returns false when the file is really there.
>>I access with the following format: \\IP\Share\File and have no problem when not going to a network drive.
>>I checked my audit log and the specific failure is error 3221225578 "User logon with misspelled or bad password"
>>I tried to make all my ASPNET user passwords the same. Bad idea! Then the application would not even run and resulted in an HTML page that says "server unavailable". Blanking out the password and rebooting allowed the app to run again but I still cannot write to the other server.
>>Anyone know how to deal with this?