Client update failed

Discussion in 'ESET NOD32 Antivirus' started by shaolinmonk, Oct 24, 2011.

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

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Using latest EAV Business 4.2.71.2 with update mirror enabled. Mirror authentication is set to NONE in Advanced Setup, and Connect to LAN is set as "System account (default)". All clients are joined to the Windows domain.

    Client update works fine when logged in as a domain user.

    Client update fails when logged in as a local computer user (there are situations when we need to log in in this mode).

    Couldn't figure for the past several days! Any help will be greatly appreciated.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    When you update via http there should be no issues with authentication. Can you confirm you download updates via http and not from a shared folder ?
     
  3. shaolinmonk

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Yes, update via internal HTTP server is checked, and not from shared folder.

    Some more info. EAV BE with mirror is installed on Windows 2008 R2 server, if it helps. All the required TCP ports 2221-2224, 445, and UDP ports 137-139 are opened on server firewall.
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Is http authentication set to None in the mirror setup then?
     
  5. shaolinmonk

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Yes, mirror authentication is set to NONE.

    Tried clearing cache. Tried disabling firewall on client side. Eset HHTP Server and ERA Server services are started and running. Doesn't work whatsoever.

    Clients are pointed to http://192.168.11.3:2221 for updates. As mentioned somewhere in the forum, tried http://192.168.11.3:2221/update-ver but only blank page shows up.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Try changing the port 2221 to another one both on the server creating the mirror as well as on one of the clients (just for a test first). You could also use netstat to find out if there's another application listening on that port and clashing with ERAS.
     
  7. shaolinmonk

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Changed port to 1111 both on server and client - cannot update. Netstat shows it's listening in port 1111.

    Changed back to port 2221 but netstat shows it's not listening on that port. I've opened TCP port 2221 on windows firewall to the application Eset HTTP Server. Even tried opening port 2221 to application ERA server. Not listening on that port. So what gives?

    Nestat shows no other application is listening on port 2221.
     
  8. shaolinmonk

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Ok got the port 2221 listening on the server. And now strangely, client cannot update either as domain user or local user.

    Disabled malwarebytes on client, changed ports, added everyone to the mirror folder permission, ping works both ways, .... nothing works.

    Looks like going IIS route may be the only other way ... I just don't want to run another service on the server.

    If any one had similar experience, your advice would be appreciated.
     
  9. shaolinmonk

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Re: Client update failed (fixed)

    My stupid mistake!

    Mirror server works using either ERAS method or client EAV/ESS BE method. Just make sure to select correct internal HTTP server (EHttpServ.exe). There are two - one within the ERAS program folder and one within ESET client program folder. When using ERAS method, open TCP port 2221 for HTTP server within ERAS program folder. When using client method, use HTTP server within ESET client program folder.

    One small issue I faced though. When using ERAS method, ESET HTTP Server service is automatically started which is for use client EAV/ESS BE. This is not what we want. My solution is to set ESET RA HTTP Server to startup type Automatic, and ESET HTTP Server is set to startup type Disabled. This worked for even after restarting the server several times.

    Having both mirrors enabled also creates problem. Just use one method.
     
    Last edited: Oct 26, 2011
  10. dmaasland

    dmaasland Registered Member

    Joined:
    Nov 10, 2010
    Posts:
    468
    Did you insert your .lic file into the EAV / ESS clients? If not then it should be impossible to start the client http server.
     
  11. shaolinmonk

    shaolinmonk Registered Member

    Joined:
    Oct 24, 2011
    Posts:
    8
    Yes, of course I did insert .lic file and that's how I enabled mirror functionality. Even after removing .lic file, when ERAS mirror is enabled, client HTTP server starts rather than its RA HTTP server.

    Anyway, I got it working and happily chugging along for now.
     
Thread Status:
Not open for further replies.