Jump to content

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×