Skip to main content

Firewall blocking access to Acronis at 185.151.160.15

Thread needs solution

My computer is trying repeatedly to access IP 185.151.160.15 which I show as belonging to Acronis.  I have Acronis True Image 2018 and it appears to be working properly.

Any idea why my computer is trying to access this IP?

Thanks,
Joe

0 Users found this helpful

Joe, there are several possibilities for this connection.

On my own computer, I only see one such connection to a slightly different IP address which is for the Cloud Dashboard service (mms_mini.exe to 185.151.161.13) which is due to the fact that I have ATI 2019 signed in to my Acronis Account and this enables me to access the dashboard from the Account page of the ATI GUI.

The other possibility is that you have the default setting to 'Participate in the Acronis Customer Experience Program' ticked on the main Settings page in the ATI GUI which also involves Google Analytics.

Hi Steve, thanks for your help.  I'm not participating in the Customer Experience Program, and I don't use Acronis Cloud.  As it doesn't appear to be affecting my installation, guess I will just ignore it.  The only problem is that it clutters my Sonic Wall firewall log.

Thanks,
Joe

Joe, you can try to check what actual program is making the connection as follows:

Open an Administrator level Command Prompt.
(CMD run as Administrator)

Then run netstat -b  and look for the IP address / program name making the connection.

C:\>netstat -b

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    10.36.111.118:49703    185.151.161.13:7795    ESTABLISHED
 [mms_mini.exe]

Didn't see the foreign IP but the connection isn't established.  I have several connections that reference mms_mini.exe but they don't show the foreign IP:

 

 TCP    127.0.0.1:5905         Joe-Windows10:49731    ESTABLISHED
 [mms_mini.exe]

 

I have two computers running Acronis and they are both trying to access that IP.  Here's a brief excerpt from packet capture in the Sonic Wall.

 

11/11/2018 17:00:27.496 -- X0* 192.168.102.25 185.151.160.15 IP TCP 59831,7796 DROPPED 66[66]
5 11/11/2018 17:00:28.016 -- X0* 192.168.102.25 185.151.160.15 IP TCP 59831,7796 DROPPED 66[66]
6 11/11/2018 17:00:28.512 -- X0* 192.168.102.25 185.151.160.15 IP TCP 59831,7796 DROPPED 66[66]
7 11/11/2018 17:00:31.064 -- X0* 192.168.102.16 185.151.160.15 IP TCP 62986,7796 DROPPED 66[66]
8 11/11/2018 17:00:31.560 -- X0* 192.168.102.16 185.151.160.15 IP TCP 62986,7796 DROPPED 66[66]
9 11/11/2018 17:00:32.096 -- X0* 192.168.102.16 185.151.160.15 IP TCP 62986,7796 DROPPED 66[66]

Joe, another option via using netstat that may help.

C:\>netstat -b -o|find "185.151.16"
  TCP    10.36.111.118:49703    185.151.161.13:7795    ESTABLISHED     4320

C:\>tasklist|find "4320"
mms_mini.exe                  4320 Services                   0     37,232 K

The first netstat -b -o command output is passed using | to the find command looking for your remote IP address "181.151.16"

On my system this returns a Process ID of 4320

The tasklist command output is passed again to the find command to identify process 4320 which shows it is the mms_mini.exe Service process.