I hope that someone here can help with what should be a simple problem.
We have a web server running on machine a - let's call it machine a. From that web server we need to access a share on machine b - let's call it machine b. We simply want to put pdf documents in the share that can be accessed from a web client via the path http://domain.com/pdf/document.pdf.
We've created a virtual directory (pdf) in IIS 6.0 that points to the share and can verify that this is set up properly - pointed to a share on a network server and with proper login credentials since we can browse this share just fine from within the IIS manager.
The problem occurs when trying to access a document via the client as described above. We get an http 500 error. The resulting log file entries are as shown below:
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2009-10-21 23:14:51
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2009-10-21 23:15:02 W3SVC1 10.0.1.24 GET /pdf/111455.1.pdf - 80 - 10.0.1.50 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:1.9.1.3)+Gecko/20090824+Firefox/3.5.3+(.NET+CLR+3.5.30729) 500 16 1326
The subcode 16 "UNC Authorization Credentials" and the Win32 code 1326 "Unknown User Name or Bad Password" would indicate that we don't quite have something set up correctly yet.
We've added a user IUSR_machinea login to machineb and given this user account read privileges to the share. We've also gone into the properties for the virtual folder within IIS and certified that Anonymous access is turned on and that the login/password match the IUSR_machinea account set up on machineb.
We've also tried using the same login/password in IIS for the virtual directory for the anonymous access as what was assigned to the share itself and we've also tried using an admin login/password for the anonymous user and get the same results no matter what we try. We've tried turning Windows authentication on/off and no difference either.
I can also verify that if I point the virtual directory to a folder on machina itself that the link from the web client works fine and the document is retrieved as it should be so the problem is definitely related to connecting to the share.
Can anyone tell us what we are doing wrong?
Thanks in advance!!