Here's the situation:
- Server A is used as a Redistribution server for Etrust Antivirus signature updates.
- Server B has Etrust installed and when it tries to obtain a signature update from Server A, it gets a connection error stating it could not connect to the file. (networking has been ruled out)
- When the service that runs this job on Server B(ETrust Antivirus Job Server) is changed to logon using a domain account, rather than the Local System Account, it can access the required file on Server A and the signature download is successful. Using a domain account is not an acceptable final solution.
I have 2 different clients, one with the above problem, another, with seemingly the same configuration, same rights to the required files, same ETrust settings, and it has no problem updating the signature using the Local System Account to start the same service.
According to Computer Associates, this is a phenomenon they have seen but cannot explain, they see it as an O/S rights issue. Their only work-around is to change the account used to start the required service.
Is anyone aware of a local security policy setting in Windows 2000 Server that would forbid the access to files to a service from another server that is using the Local System Account? Or of any other settings that would restrict this?
Hope this is clear.
Thank you
R Leduc
- Server A is used as a Redistribution server for Etrust Antivirus signature updates.
- Server B has Etrust installed and when it tries to obtain a signature update from Server A, it gets a connection error stating it could not connect to the file. (networking has been ruled out)
- When the service that runs this job on Server B(ETrust Antivirus Job Server) is changed to logon using a domain account, rather than the Local System Account, it can access the required file on Server A and the signature download is successful. Using a domain account is not an acceptable final solution.
I have 2 different clients, one with the above problem, another, with seemingly the same configuration, same rights to the required files, same ETrust settings, and it has no problem updating the signature using the Local System Account to start the same service.
According to Computer Associates, this is a phenomenon they have seen but cannot explain, they see it as an O/S rights issue. Their only work-around is to change the account used to start the required service.
Is anyone aware of a local security policy setting in Windows 2000 Server that would forbid the access to files to a service from another server that is using the Local System Account? Or of any other settings that would restrict this?
Hope this is clear.
Thank you
R Leduc
