401.3 When Accessing Remote UNC Share

I've been trying to figure out the following issue for a few days with
no luck. There are two servers involved, both are standalone servers
(no domain):

WebServer - Windows 2003 R2
FileServer - Windoows 2000 SP4

>From the WebServer i've created a new Virtual Directory, and specified
a UNC path on the FileServer. I then specify an Account to use when
accessing the UNC. This account exists on both the WebServer and
FileServer with the same password. Accessing the UNC from Windows
Explorer works flawless. Trying to access the UNC though a browser
results in the following:

If the UNC Username and password has no prefix, I get error 500
If I specify \\WebServer\Username along with the password I get a
401.3 error
If I specify \\FileServer\Username along with the password I get
another error 500

I've verified that the UNC username exists in the Metabase. If I
disable the UNC username/password, and check the both to use the
current credentials (with basic Authentication checked) I am prompted
with a login screen. Entering the account in there (or even one of
the admin accounts) results in a 401.3 error after a few attempts.

Using the exact same credentials to access the file share from outside
IIS is working. I'm stuck for ideas, as neither computer is in a
domain so Delegation can't be an issue. Is there something simple i'm
missing?

On Oct 27, 12:51 am, GTU... RemoveThis @hush.com wrote:
> I've been trying to figure out the following issue for a few days with
> no luck. There are two servers involved, both are standalone servers
> (no domain):
>
> WebServer - Windows 2003 R2
> FileServer - Windoows 2000 SP4
>
> >From the WebServer i've created a new Virtual Directory, and specified
>
> a UNC path on the FileServer. I then specify an Account to use when
> accessing the UNC. This account exists on both the WebServer and
> FileServer with the same password. Accessing the UNC from Windows
> Explorer works flawless. Trying to access the UNC though a browser
> results in the following:
>
> If the UNC Username and password has no prefix, I get error 500
> If I specify \\WebServer\Username along with the password I get a
> 401.3 error
> If I specify \\FileServer\Username along with the password I get
> another error 500
>
> I've verified that the UNC username exists in the Metabase. If I
> disable the UNC username/password, and check the both to use the
> current credentials (with basic Authentication checked) I am prompted
> with a login screen. Entering the account in there (or even one of
> the admin accounts) results in a 401.3 error after a few attempts.
>
> Using the exact same credentials to access the file share from outside
> IIS is working. I'm stuck for ideas, as neither computer is in a
> domain so Delegation can't be an issue. Is there something simple i'm
> missing?

Incidentally, a ProcessMon reveals the following:

Access Denied when trying to access \\FileServer\Share. Going deeper
it shows the impersonating account as \\WebServer\User, and the User
under process as "NT Authority\System" (App Pool is using Local System
for troubleshooting).

Is the fact that the account appears to be impersonated causing any
issues?