Re: read and write file from network drive (NAS)

From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 06/28/05


Date: Tue, 28 Jun 2005 09:33:08 -0500

On Sun, 26 Jun 2005 19:07:04 -0700, oceandeep <ocean@sunset.hk> wrote:

¤ I have a NAS machine within the dmzone with IP 192.168.11.xxx
¤ where i want to write and read file from a designated location
¤
¤ I have created 2 folders "source" and "target" in the NAS, which i can
¤ access through explorer
¤ from the Web Server Machine by UNC path "\\192.168.11.xxx\source" and
¤ "\\192.168.11.xxx\target" respectively.
¤
¤ However, in ASP.net (VB) code when i tried to read the file by the same UNC
¤ path "\\192.168.11.xxx\source" , it returns error message "Logon failure:
¤ unknown user name or bad password"
¤
¤ I have tried to allow full control of ASPNET user in the NAS and put ASPNET
¤ user in the webserver side to the group "administrators" but still doesnt
¤ help.
¤
¤ I searched through the web and found some results about i have to
¤ "impersonate" the ASP.NET instance and assign a valid username and password
¤ of the NAS. I have followed this article
¤ http://support.microsoft.com/default.aspx?scid=kb;EN-US;306158#2 and
¤ implemented the code to impersonate a different user.
¤
¤ my webserver platform is Win 2003, VS.net 2003 , .Net Framework 1.1

If you're using Anonymous (no) authentication (w/o impersonation) then the local ASPNET account must
have the same credentials (password) on both machines in order to delegate security.

If you're using Basic authentication (w/impersonation) then you can use a domain account to delegate
security. If you're using local accounts in a workgroup environment then user credentials must be
the same on both computers in order to delegate security.

Credentials cannot be delegated when using Integrated Windows NT authentication unless you implement
Kerberos, which doesn't sound possible in your network configuration.

Paul
~~~~
Microsoft MVP (Visual Basic)



Relevant Pages

  • Re: SMS 2003 + NAS
    ... Let's approach this outside of the NAS issue entirely for the moment. ... site system connection account. ... Of course the site server's machine account must have rights on the DP. ... will probably want to clear the site server machine ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 + NAS
    ... Let's approach this outside of the NAS issue entirely for the moment. ... site system connection account. ... Of course the site server's machine account must have rights on the DP. ... will probably want to clear the site server machine ...
    (microsoft.public.sms.admin)
  • Re: Indexing a NAS share
    ... If you are indexing a virtual directory that is pointing to the NAS share ... If you added the share manually to your catalog then Index Server uses ... Otherwise we use the SYSTEM account. ...
    (microsoft.public.inetserver.indexserver)
  • Re: FSO to non domain server UNC?
    ... Have you tried enabling auditing on both machines to ... the NAS does not record any attempt to access it by the FSO. ... the FSO uses some computer account, and since the computer/NAS are not ...
    (microsoft.public.inetserver.iis.security)
  • Re: ASP.NET application cannot access network drive
    ... I finally figured out a way to disable all "guest" access to the NAS ... was to create a new "ASPNET" user account on the NAS drive WITHOUT ... Windows' aspnet_wp.exe worker process uses. ...
    (microsoft.public.dotnet.framework.aspnet.security)