When IIS logs to a UNC path, it attempts to connect to the target source
with the SYSTEM account. That means that in order for this to properly work,
you would need to grant access to the domain account. The only way this
feature works in a non-domain or cross-domain environment is if you were to
grant Anonymous access to your NAS (which isn't exactly a viable solution).
Basically, this only works properly when both the IIS box and the target
file server are Windows machines in a trusted domain environment.
--
Joe Corey
MCSE, MCSA, Security+
jcorey.TakeThisOut@andrew.cmu.edu
<mmdanni.TakeThisOut@tiscali.it> wrote in message
news:1157096150.811414.158750@p79g2000cwp.googlegroups.com...
> Hi
>
> in my company we have just installed a new web server and i'm trying to
> configure remote logging for iis 6.0.
> The idea would be to make the web server log on our NAS server on the
> same network but unfortunately i'm not able to make it work.
> The architecture is very simple:
> * web server win 2003 standard edition
> * nas: os linux embedded
>
> Whenever i try to save a log on a shared folder of the nas server
> nothing happens; the only thing is an error message on the event viewer
> (this is translated by me because my os is in italian)
> =========
> "Impossible to create registry file \<server
> name>\<directory>\W3SVC1400611488. Make sure that the directory name is
> correct and that computer has the priviledge to write on the directory.
> =========
>
> Any idea of what i'm doing wrong?
> Which user should i use?
>
> Many thanks
> MMD
>
>> Stay informed about: Remote Logging