Itoo Software Forum
Forest Pack => Forest Pro (*) => Topic started by: Mouton on June 26, 2018, 02:12:42 PM
-
Hi Itoo
i have recently upgraded to new itoo forestpack pro every time i want to update the itoo library gives me error 13 Network error
how to fix
regards
moutn
-
Same error here! I don't know what to do!
-
We have few reports about this error.
We are still investigating what could be the problem.
So far it seems to be some bad settings (some user says of Internet Explorer ) on user side.
If You do figure this out before we do (we can't replicate on our side, so it is hard) please share Your solution.
-
if have done also a clean installation of FOrest pack and railclone in still gives me "error 13 Network error
Socket operation times out "
-
Could You please state Your OS version? Is it Win 7?
-
Hi,
Please, open the attached certificate on the problematic computer and click on the Install Certificate... button (attaching screen-shot). Hope that helps.
Best regards,
-
Hello,
I have the same problem on the servers of my renderfarm in windows 7.
thanks to the certifica it works.
thank you
-
Same here. Sometimes it works and sometime no connection to updater account.
-
i'am on win 10 and i installed the certificate and the problem is still there
-
Mouton
Did you try to check the connection by using any TCP scanning tool (as nmap) and test the server port from your workstation in a following way?
nmap -p 16720 serverIP
What's the result? It is most likely caused by a third-party firewall, anti-virus, or Internet security solution, I would recommend you to double check settings for those. Please check all rules applied to the port 16720. As mentioned previously, it must be open both for TCP and UPD.
On the license server computer please try following steps:
Access your Windows Services list by opening a run box (Windows key + R) and then type services.msc and press return.
Please find the Itoo Software License Server service. It should be running and set to automatic. If so, please have a look in Event Viewer for the error. From there you should identify what's blocking the connection.
Hope it help you to identify where the problem is.
-
thanks rokas
looks to me it was my Antivirus that blocked the outgoing traffic of the update manger