Discussion Locked

VB won't see html file on NT virtual dir

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are running iis4.0sp4 in a mixed nt/novell environment. Our web server has a limited amount of disk space so we were storing html files that our clients needed access to on a novell server. Because of a lack of space and other reasons we needed to move those files from the novell server to another server running NT4sp6. I set up a virtual directory in iis pointed at a sub-folder on the mass storage server. Every day we generate an html activity report file for our clients, if there's no activity no html file is generated. On the web site we can make a link to the files there but when we run a visual basic program to reference it doesn't see them but will see files if they're on the novell server. When a client wants to look at a report a VB program is run which checks to see if the file exists, if it does it is displayed, if not the program shows a different page which says ?No activity? etc. We need it do this because when a client wants to see a daily volume report we need to be able to tell them if there's no activity. Now they just get a 'page not found error'. Any help will be greatly appreciated.

4 replies

by jillbean

Coupla maybes. VB program is using the share name right (\\server\share)? not the virtual name(/virtualdirectory).

If the vb program is executed by the server, it is done as Iusr_machinename (local)account, and maybe doesn't have rights? try specifically allowing guest access (Read/write/execute) on target share and the ACL on the target directory.

Also NT is goofy about using machine names if not pointed at a wins server and running only tcp/ip - if you have this try \\ipaddress\sharename as the path instead of \\server\share.

by tshelley

It turns out that if you have the anonymous iis account syncronized (iusr_machinename) the security token created doesn't have network access. I finally found an article on the MS knowledge base that addressed it. (Q207671).
Once we specified a user account and unchecked the syncronize password box, it worked.

This discussion is closed to new replies.