Jump to content

Archived

This topic is now archived and is closed to further replies.

bbahes

Mirror Tool - Unauthorized access

Recommended Posts

Hi!

 

I have created mirror on virtual appliance using command

 

sudo ./MirrorTool --mirrorType regular --intermediateUpdateDirectory /tmp/mirrorTool/mirrorTemp --offlineLicenseFilename 
/tmp/mirrorTool/offline.lf --outputDirectory /tmp/mirrorTool/mirror

 

Under policy settings for Update for Security product I have entered hxxp://IP_ADDRESS_OF_APPLIANCE:2221under Update server.

 

However I'm getting Unauthorized access on client under Update.

 

What am I doing wrong?

Share this post


Link to post
Share on other sites

The mirror tool merely downloads update files from ESET's servers and saves them to a local disk. It does not contain an http server for distributing updates so there's no ehttpsrv process that would listen on port 2221. You can use a 3rd party http server or serve mirrored files via a smb share to other clients.

Share this post


Link to post
Share on other sites

The mirror tool merely downloads update files from ESET's servers and saves them to a local disk. It does not contain an http server for distributing updates so there's no ehttpsrv process that would listen on port 2221. You can use a 3rd party http server or serve mirrored files via a smb share to other clients.

 

So if I wanted to share update files via file share in Update server  I would have to enter network share location? What specific folder? What about credentials?

Share this post


Link to post
Share on other sites

 

The mirror tool merely downloads update files from ESET's servers and saves them to a local disk. It does not contain an http server for distributing updates so there's no ehttpsrv process that would listen on port 2221. You can use a 3rd party http server or serve mirrored files via a smb share to other clients.

 

So if I wanted to share update files via file share in Update server  I would have to enter network share location? What specific folder? What about credentials?

 

 

It all depends on the operating systems. The mirror tool merely downloads and saves update files to a disk and then you share the files like any other files. See the instructions for sharing files via Samba for instance.

Share this post


Link to post
Share on other sites

 

 

The mirror tool merely downloads update files from ESET's servers and saves them to a local disk. It does not contain an http server for distributing updates so there's no ehttpsrv process that would listen on port 2221. You can use a 3rd party http server or serve mirrored files via a smb share to other clients.

 

So if I wanted to share update files via file share in Update server  I would have to enter network share location? What specific folder? What about credentials?

 

 

It all depends on the operating systems. The mirror tool merely downloads and saves update files to a disk and then you share the files like any other files. See the instructions for sharing files via Samba for instance.

 

 

I know how to make a share on linux distribution like your virtual appliance CentOS 6.7, however I wanted to know where to enter those credentials in policy and what folder to share?  /tmp/mirrorTool/mirrorTemp or

/tmp/mirrorTool/ or /tmp/mirrorTool/mirror ?

Share this post


Link to post
Share on other sites

This was yet another great feature of ESET 4/5... You could have a mirror setup from your admin console, definitions downloaded, and policy updated to point to the location in less than 5 minutes.  The hackery now you have to go through with the proxy server, or setting one of your endpoints to act as a mirror is way too over the top for such a simple task.

Share this post


Link to post
Share on other sites

This was yet another great feature of ESET 4/5... You could have a mirror setup from your admin console, definitions downloaded, and policy updated to point to the location in less than 5 minutes.  The hackery now you have to go through with the proxy server, or setting one of your endpoints to act as a mirror is way too over the top for such a simple task.

 

I agree, we still use v5, but I'm testing this new Mirror Tool and license is about to expire in less that 30 days so I have to make decision, renew license or drop for competitor product.

Share this post


Link to post
Share on other sites

I know how to make a share on linux distribution like your virtual appliance CentOS 6.7, however I wanted to know where to enter those credentials in policy and what folder to share?  /tmp/mirrorTool/mirrorTemp or

/tmp/mirrorTool/ or /tmp/mirrorTool/mirror ?

Share the subfolder /tmp/mirrorTool/mirror and set the path on clients as \\server\mirror.

Share this post


Link to post
Share on other sites

I have this problem with "Unauthorized access" too.

 

1. I used MirrorTool to download updates for 4/5/6 Antivirus versions to ERA server (virtual appliance with Cent OS)

It created directory structure like

mirror 

  |------eset_upd

             |---------ep6

             |---------era6

             |---------v4

             |---------v5

2. Installed Lighttpd and configured it to open mirror directory, something like hxxp://era.mycompany.local:8008(without authorization)

3. Configured Endpoint 5 Antivirus client to update from hxxp://era.mycompany.local:8008/eset_upd/v5, it's working like a charm

4. Configured Endpoint 6 Antivirus client to update from hxxp://era.mycompany.local:8008/eset_upd/ep6and got error message 'Unauthorized access'. License on client is already activated, updates from ESET servers working without problems.

 

So, how to make mirror work for EP6 clients?

Share this post


Link to post
Share on other sites

 

I know how to make a share on linux distribution like your virtual appliance CentOS 6.7, however I wanted to know where to enter those credentials in policy and what folder to share?  /tmp/mirrorTool/mirrorTemp or

/tmp/mirrorTool/ or /tmp/mirrorTool/mirror ?

Share the subfolder /tmp/mirrorTool/mirror and set the path on clients as \\server\mirror.

 

 

I did. However a new problem appears. Now my client says Invalid username and/or password.

I am able to access this share from client (Windows 10) and browse folder, delete, create, modifiy....however Endpoint antivirus won't authorize.

 

UPDATE: One thing that happened today. As i powered on virtual machines and started Endpoint antivirus update I got message Could not connect to server.

After I accessed share from Windows Explorer with credentials, Endpoint antivirus reverted to message Invalid username and/or password.

Share this post


Link to post
Share on other sites

First of all, check if Endpoint is configured to connect via a proxy. I remember getting the "Unauthorized access" error when I forgot to disable the use of a proxy that I had previously configured but wasn't running any more.

 

As for credentials for connecting to the samba share, you can set them in Endpoint's policy under Update -> Connect to LAN as.

Share this post


Link to post
Share on other sites

First of all, check if Endpoint is configured to connect via a proxy. I remember getting the "Unauthorized access" error when I forgot to disable the use of a proxy that I had previously configured but wasn't running any more.

 

As for credentials for connecting to the samba share, you can set them in Endpoint's policy under Update -> Connect to LAN as.

 

Many thx, Marco! It was 'Use global proxy server settings' by default. Changed to 'Do not use proxy' and anything is ok!  :)

Share this post


Link to post
Share on other sites

 

First of all, check if Endpoint is configured to connect via a proxy. I remember getting the "Unauthorized access" error when I forgot to disable the use of a proxy that I had previously configured but wasn't running any more.

 

As for credentials for connecting to the samba share, you can set them in Endpoint's policy under Update -> Connect to LAN as.

 

Many thx, Marco! It was 'Use global proxy server settings' by default. Changed to 'Do not use proxy' and anything is ok!  :)

 

 

Well, global proxy settings should be configured correctly too. Otherwise activation, LiveGrid, etc. will not work. Then "Use global proxy settings" could be selected in the update setup and update would work.

Share this post


Link to post
Share on other sites

First of all, check if Endpoint is configured to connect via a proxy. I remember getting the "Unauthorized access" error when I forgot to disable the use of a proxy that I had previously configured but wasn't running any more.

 

As for credentials for connecting to the samba share, you can set them in Endpoint's policy under Update -> Connect to LAN as.

 

 

I am able to access share via admin credentials in Windows Explorer.

 

Proxy is set to "Do not use proxy server" and Connect to Lan as is set to Specified user, IP_ADDRESS_OF_ERA\admin

 

Still I'm getting error Invalid Username and/or Password.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...