Parent Server Won't Update Itself - Def Download Failed

[stelmerfudd]

Hi,

I'm new to this group. If this has been answered somewhere already, I apologize. Please point me there.

I'm running Symantec Corporate 8. I have been using cegetter.bat on the parent server. It was working fine on another server but that server was decommissioned. I moved all of the clients to the new parent server. All of that went fine, but I have been having problems with the new server updating itself with the new virus defs that are downloaded with cegetter. I saw the article posted here suggesting the newer script, xdbdown. And I will try that.

One thing I noticed is that the new .xdb file that is downloaded with cegetter in C:\Program Files\SAV directory isn't getting moved to the VPHOME directory. (I don't understand how that file gets moved. I'm thinking maybe navup8.exe moves the xdb file but I'm not sure.)

I don't know if I've missed some configuration setting on the new server or what.

I found this article,

http://service1.symantec.com/SUPPORT/ent-security.nsf/pfdocs/2003082912294348?Open,

made the registry changes and the virus defs got updated on the server and the clients on 5/18/2005, but they haven't been updated since then.

Also, when I select "Update Virus Defs Now" in the console, I get the message in the console under Status of Client Updates, "Def Download Failed" and also notice that the server has not updated itself either.

What is going on here? Any help would be greatly appreciated.

Thank you!

 

[Stiddy]

Can the server ftp to symantec.com?



HTH - Stiddy

 

[stelmerfudd]

I couldn't get the server to ftp directly. I couldn't get the configuration on the server past our proxy server. That's why I started using the cegetter script.

I just tried the xdbdown.cmd file. It got the lastest xdb file and saved it to c:\Program Files\SAV but the server still hasn't updated itself and has not updated the clients. I checked the VPHOME directory. The new XDB file was not moved there. I don't really understand how that works, how the file gets moved from the SAV directory to VPHOME.

Thanks.

 

[Stiddy]

Well,
cegetter script uses ftp. You should have a batch file and a text file as follows.

CEGETTER.bat
ftp -s:\Symantec\FTP\cescript.txt
call "D:\Symantec\FTP\navup8.exe"
REM The following line copies the .xdb file to the SAV
REM directories
move D:\Symantec\FTP\*.xdb C:\progra~1\SAV\
del /q D:\Symantec\FTP\navup8.exe

CEGETTER.txt
open ftp.symantec.com
anonymous
blahblah@blah.com
cd public/english_us_canada/antivirus_definitions/norton_antivirus/static
lcd D:\Symantec\FTP
bin
hash
prompt
get navup8.exe
quit

HTH - Stiddy

 

[stelmerfudd]

Hi Stiddy,

Yeah, I have that cegetter.bat. Its getting the xdb file to the SAV directory but its not moving the file to VPHOME.

I tried using xdbdown.cmd this morning and just running it from a command line. It worked fine, deleted the old xdb files from the SAV directory. I also noticed that the xdb file got moved to VPHOME. Lo and behold the virus defs got updated on the server and on the clients. I just don't know why or trust it to keep working.

Its been so long since I tried configuring LiveUpdate on the server I can't remember exactly why it wouldn't work except that it had something to do with not being able to get through the proxy server. I believe there is an option to use the settings in Internet Explorer which I tried and no dice. Didn't work.

Thanks for the reply.

 

[fuego007]

The SAV folder IS the VPHOME folder.

Have you tried restarting the server? Every once in a great while, I find that my primary server will get the .xdb file but no convert it into a .vdb file. It MUST do this in order to disseminate the defs to clients.

Bob

 

[stelmerfudd]

Hi Bob,

OK. What you said, "The SAV folder is the VPHOME folder." may be what the problem is. I don't know how but the VPHOME share is not pointing to the SAV folder. The VPHOME share is pointing to the Symantec folder.

I have resolved the problem with my own script (at least patched it so its working). What I saw was that the .xdb file was not getting moved to the VPHOME share so I wrote a script that did that. I just added the lines to the cegetter.bat file that runs as a scheduled task. The supposedly newer, better xdbdown.cmd would error, "ERROR: This script needs Windows 2000 or better." and it is running on a w2k server.

The server does get restarted regularly.

Thanks for the reply.

Richard