• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Problem connecting to a NT share from ASP via UNC

I've got two ASP methods for browsing directories on NT shares.  They worked until we upgraded from IIS 3 to IIS 4. One method is the FileFunctions component, the other is a script I wrote using the FileSystemObject Object.  For some reason, these scripts running on the IIS 4 server can connect to a Win95 share but not an NT share via a UNC.  Permissions have not been changed and the web server has retained the same langroup name.  We're stumped.  Any suggestions?
0
jlow
Asked:
jlow
1 Solution
 
MasseyMCommented:
can you post some code?
0
 
jlowAuthor Commented:
This is not dependent on code.  It's a IIS 4 / NT server related issue.
0
 
mcixCommented:
SP3 is applied, correct?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jlowAuthor Commented:
Yes, we have SP3.
0
 
crasherCommented:
for some reasons, do You connect to your file using a username/password ?
in this case, try to configure the user as a local user (dependant of the machine) and not as a domain user.

Some IIS functions have changed from v3 to v4, i've experienced problems using FTP with DOMAIN users and IIS4, but it worked well with IIS3 .

0
 
BlackManCommented:
IIS4 introduced a new user (IUSR_WAM as far as I remember) which must be given rights to your network simular to IUSR_<node>. The reason it works on Win95 is that Win95 doesn't care about security, but NT does.
0
 
rakhrasCommented:
This is a problem with IIS 4.0.
See the Microsoft Knowledge base (Q183060)
In that article, they say:

Network paths such as UNC's should work for Basic / Anonymous access, but they do not work when you use the updated JET driver under IIS 4.0. This is because the user security context is switched to SYSTEM when it reads the database. The system account cannot access networked resources. Move the database to the Web server and use a local path. For  Visual InterDev to work from a remote workstation in this situation, set
up the system DSN's as described in the Microsoft Knowledge Base article listed in the REFERENCES section. The article was written to show how to work around delegation problems on authenticated projects, but the fix is applicable to this problem also.


Ralph.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now