Jump to content


Photo

Error 0

Server 2012 R2 Update Error

  • Please log in to reply
5 replies to this topic

#1 comprev

comprev

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 23 March 2018 - 10:25 PM

I've installed Immunet on a 2012R2 server. The server is a new install VM used as a test bed. I was wanting to test Immunet before using it. If I click "Update Now" on the main page, the dialog box that pops up will get new definitions, but the first message it lists is "Could not connect to the update server (error 0), please try again. If the problem persists, please contact Immunet Support."

 

The version of Immunet is 6.0.8.10638. The VM has been rebooted and this has continued for a couple of weeks.



#2 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 2,038 posts
  • LocationEarth

Posted 24 March 2018 - 05:23 AM

Server 2012R2 is a supported platform.

 

Double check that Immunet's processes are not being partially blocked, sandboxed or interfered with by your VM software, firewall or any other security software you may have installed, that being sfc.exe, iptray.exe (and freshclam.exe if you have ClamAV enabled). Make sure to allow for both in-coming and out-going "unrestricted IP traffic" for all processes.

 

If that's not the issue definitely let us know & I have already alerted the Admins to please view this topic.

 

Cheers, Ritchie...


* Immunet Global Forum Moderator *


#3 Wookiee

Wookiee

    Member

  • Administrators
  • 25 posts

Posted 24 March 2018 - 12:12 PM

How much space do you have available for that VM? Any high disk space usage alerts or anything like that ?



#4 John_3_16

John_3_16

    Member

  • Members
  • PipPip
  • 15 posts

Posted 24 March 2018 - 05:48 PM

I agree with Ritchie, whitelisting Immunet software with your firewalls, proxies and any other security software is the first step to insure I/O communications.

 

GL and God bless. :D



#5 comprev

comprev

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 26 March 2018 - 01:24 AM

I made NO changes to the VM, Hyper-V, or the Windows 10 host. Also, this VM had been rebooted several times over the past couple of weeks since installing Immunet. However, today Immunet is seeing the update server. So, I don't have any idea what the problem was.



#6 ritchie58

ritchie58

    Staff Member

  • Moderators
  • 2,038 posts
  • LocationEarth

Posted 26 March 2018 - 03:25 AM

The issue has seemed to have corrected itself? That is really weird comprev, especially if you didn't make any configuration changes!

 

Please by all means if you see the same behavior start again let us know. I believe some serious further investigation is warranted if it does.

 

Regards, Ritchie...


* Immunet Global Forum Moderator *





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users