You configured Windows Integrated Authentication, which is an identity that
cannot hop off of the IIS machine unless ....
Read the following two sections in the URL I posted
<a style='text-decoration: underline;' href="http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/deploy/confeat/RemStorg.asp" target="_blank">http://www.microsoft.com/technet/treeview/default.asp?url=/technet/pro...chnol/w</a>
Pass-Through Authentication in a Workgroup Environment
In a workgroup environment, all user accounts are local. Pass-through
authentication using Basic authentication can still function, as long as
both the IIS and file servers have user accounts with identical user names
and passwords. This configuration quickly becomes an administrative burden
and consequently is not widely implemented. For these circumstances,
designating a single user account designed specifically for use with the UNC
connection is likely the best choice.
Pass-Through Authentication in a Domain Environment
When working in a domain environment, if you use Basic authentication-which
should always be implemented with Secure Sockets Layer (SSL) to encrypt the
user name and password data-or Kerberos, via Integrated Windows
authentication, pass-through authentication should work without additional
configuration. This presumes, of course, that the file server(s) and IIS are
members of the same domain or trusted domains. Windows Server 2003 has a new
feature called constrained delegation that allows you to implement
delegation in a more secure fashion and to delegate other kinds of logon
credentials besides Basic and Kerberos. More information and instructions on
setting up constrained delegation follows. You can find additional
information in Windows Server 2003 Help.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Fredrick A. Zilz" <fzilz.DeleteThis@NOSPAM.interhealthusa.com> wrote in message
news:%23RRfrk6rDHA.1740@TK2MSFTNGP12.phx.gbl...
Well I changed the account that is used from the use authenticated user to a
specific account, not what I wanted to do, but at least it works now.
"Fredrick A. Zilz" <fzilz.DeleteThis@NOSPAM.interhealthusa.com> wrote in message
news:%23U2zBmvqDHA.2064@TK2MSFTNGP11.phx.gbl...
> I am having trouble. I created a virtual directory that points to a share
> on another server. everyone in my domain has rights to the share and I
have
> verified I can open the share via the unc path. however when I go the
> website, I get a request for credentials which does not succeed. I have
the
> sight set for windows authentication. Same setup with the directory
being
> local works. I tried changing the app pool for the virtual directory and
> using a user which I specifically gave right to the share - still no go.
>
> IIS 6.0 on Windows 2003, share directory on Windows 2003.
>
> Thanks in advance for your assistance.
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: remote directory virtual directory