Netware: Creating Mirror Directory with nod32umc fails

[gooze]

Hello,

how can i create an local Mirror Directory with nod32umc.nlm?

I try different things and the best result i get after running LOAD SYS:/nod32umc.nlm -u USERNAME -p PASSWORD /Directory was:

Module LIBC.NLM load status OK
Module NOD32UMC.NLM load status OK

NOD32 Update Mirror Creator, Version 2.52.2,
(C) 2006 Eset, s.r.o.
Update started on 07-26-2009, 15:29:22.
Checking remote update packages at 'www.eset.com'... ok
Checking local update packages in 'SYS:/NOD32/MIRROR\'... ok (0 nups found).
Update finished at 15:29:22, total time: 0 sec (00:00:00).

But there are no update Files in the Mirror directory. Where do i get the latest signatures?

Thanks

[BFG]

Hi gooze,

Did you follow the exact steps listed in the manual?

BFG

[WayneP]

Hello gooze,

You can't create a mirror with the Novell client because it does not download updates from the internet. The manual states that you have to create a mirror folder on the same drive as the NOD32 module. Then have a Windows machine set up as a mirror and point the save location to the folder on the Novell machine.

[nopieees]

excuse me guys i cant find nod32umc and it is not in the manual .
would you please show us what is the benefit of this module

[BFG]

Hello nopieees,

This article explains the nod32umc module.

BFG

[T3dster]

Here's how we did it. Running NetWare 6.5 sp7
Created a folder on sys named NOD32. In there you put the code for NOD32.
Create a cfg file with notepad named amon.cfg which contains this
exclude=_admin:/;zen:/;sys:/;
onread-
notify
clean
delete
log
Then create a folder on sys\public named mirror
Then we created a script file (.ncf) with notepad named sig-upd.ncf that contains this
#Download NOD32 update files to SYS:\Public\Mirror
sys:/nod32/nod32umc -a sys:/nod32/nod32.auth sys:/public/mirror/
Then created another ncf named nod-upd.ncf that contains this script
#Download NOD32 update files to SYS:\Public\Mirror
sys:/nod32/nod32umc -a sys:/nod32/nod32.auth sys:/public/mirror/
We load amon via the startup script autoexec.ncf
We use a scheduled task (similar to crontab) in the Novell Remote Manager to run the sig-upd.ncf and five minutes later the nod-upd.ncf
It seems to work well for us