Help - Netshied Autoupdate not working

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I am having problems with Autoupdate with Netshield, insofar as the
client machines will not perform scheduled update from locally stored
DAT file.

OK. here is the problem I have

I can download DAT file from nai ftp site and save this on server to a
shared folder accesible to all clients.

Using the console I "point" all the clients to this folder.

If I then schedule the update to either a specific time or at startup
then it fails.

However, if I launch update in immediate mode it finds the DAT file and
updates fine.
Also, a scheduled update from the ftp site to any of the clients also
works.

Looking at the system event log (Applications) I find the message -
Error id: 4034 - The specified directory does not exist.

and the Netshield Activity log shows -

Update    NT AUTHORITY\SYSTEM    Locating installation and temp directories.
Update    NT AUTHORITY\SYSTEM    An unknown error occured while reading from
the remote system and the connection was dropped.

I am running s small network of one server (NT4 SP6) and 6 client
workstations (mix of win2k and XP). Netshield 4.03a with 5.1.00 Scan
engine

Any helpful advice would be welcome.

Thanks

Bill

Re: Help - Netshied Autoupdate not working

bill@thetennis.net says...
Quoted text here. Click to load it

At a guess, the scheduled update runs as a different user to
the immediate update, and it doesn't have enough rights.
--
If you don't want the whelks don't muck 'em about
If you don't want them someone else may

Re: Help - Netshied Autoupdate not working

ddotbudd@man.ac.uk says...
Quoted text here. Click to load it

Thanks for the thought Ayatollah, but from the same machine and with
same user login, immediate works, but scheduled doesn't.

Any further thoughts/ideas would be appreciated.

Thanks

Bill

Re: Help - Netshied Autoupdate not working

bill@thetennis.net says...
Quoted text here. Click to load it
Yebbut, I had a similar problem with a Perl script on a win2003
server, turned out when I ran it "on demand", it had the rights
of the user I logged in with, but when it ran scheduled, it had
the rights of some other user (whether I was logged in at the
time or not). Something in the logs ought to tell you what user
it was running as.
--
If you don't want the whelks don't muck 'em about
If you don't want them someone else may

Site Timeline