by Guest on Thu Oct 02, 2003 7:50 pm
Hi Andrew,
UNC works, but due to Windows design you must meet some pre-requisites to enable them to actually work. They do NOT work in the default configuration.
This is because WinSyslog is installed to be running under the Windows local system account. This account is restricted from network I/O by Windows design. This is a security measure - and it is a good one.
So, to use a UNC name from a service (like WinSyslog), you must create an account that has permissions to actually access the UNC share. Then, you must grant it "log on a service" rights so that the service can use it. Also make sure that it has permissions to access all local ressources needed. Then, go to Windows Services Manager and change the service account to the new one. Now you are able to access the UNC share.
As a general note, I do not recommend writing to UNC shares. This introduces another level auf fault probability. I recommend to run the service directly on that machine. Otherwise, if the network (or authentication) fails, you loose logging capabilities.
But as I said, it is doable...
Best regards,
Rainer Gerhards
Adiscon