Both IIS and the UNC server do not need to be in a domain for remote
fileshare to work -- I use both types all the time. However, there could be
network/IPSec policies that require domain membership -- but that is outside
the scope of IIS and into the realm of networking/access -- you will have to
provide that piece of information

As for ACL -- you can only assume that IIS is walking across the network as
the configured UNC username/password, so verify both UNC Share ACL as well
as NTFS ACL allows that user necessary access.

401.3 indicates that some authenticated user was denied access by ACL -- you
need to determine what user authenticated.

1326 indicates that you authenticated with the wrong username/password.
Probably differences between domain and local user accounts, though you need
to determine what user was being authenticated.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
Hi David,

Thanks for the link. However, in my case it does not appear to work. From
Figure 6. the way I'm set up it should be using the UNC metabase
user/password entries (which I've checked using Notepad) via Anonymous
Access. So its either a domain issue (IIS machien is not in it), or some
sort of ACL on the file server which is preventing access, unfortunately I
can;t see the ogs of teh domain server, only the IIS machine.

[quoted text, click to view]