mirror update

Discussion in 'ESET NOD32 Antivirus' started by maximx86, Oct 21, 2008.

Thread Status:
Not open for further replies.
  1. maximx86

    maximx86 Registered Member

    Joined:
    Jun 14, 2007
    Posts:
    11
    Hi all,

    is there a quick way of checking that NOD be is getting update files from a local mirror not from ESET servers?

    thanks
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Under the advanced setup menu, the updater server will be set to something you specify like \\server\share or http://localserver:2221. If it is set to Choose Automatically then you are receiving updates from Eset.
     
  3. maximx86

    maximx86 Registered Member

    Joined:
    Jun 14, 2007
    Posts:
    11
    right,

    i understand I enter this in ERAC under Server Oprions\Upate\

    http://abbey-server01:2221

    When in type this in a browser I get '500 - Internal Server Error'. Is that normal? I think my pcs still get updates from ESET as half of my pcs have newer signatures than the server.

    the miror is setup properly as whenever the server gets downloads new files they appear in the mirror folder
     

    Attached Files:

    • nod.png
      nod.png
      File size:
      18 KB
      Views:
      349
  4. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    That screenshot is for the RAS, not a Nod32 client. Assuming you have a single server providing updates and running RAS, the update server there should be set to Choose Automatically so it downloads updates from Eset (or from a different upstream server if that is your case). Individual Nod32 clients should be pointed at http://[Your RAS Server]:2221 for updates and you do this by either manually configuring each Nod32 client or by pushing the configuration down with the configuration manager in the remote administrator console.
     
Thread Status:
Not open for further replies.