Hello! I have a problem with nodes on windows10 - Connection failed.
But nodes on win7 are connect correctly.
Will someone have met with such a bug?
Workstation: Win10+corona 2.0 max2016
Nodes: Win10+corona2.0 max2016
Firewall checked, net configuration OK, Run DR under User/Administrator doesnt matter.
I found that at some point, auto detecting the nodes stopped working, due I believe to some change to Windows in some update to it (I suspect related to the remove of the Workgroup or some such thing). The solution for me was not to use the detect nodes, but to enter their names or ip addresses manually.
You don’t mention whether you were use the search LAN to find the nodes, or if you’d added them manually. One thing to try is the latest daily build, there were changes there (“DR is now able to autodiscover slaves connected through all network interfaces.” from the changelog at https://forum.corona-renderer.com/index.php?topic=20852) that seem to have undone whatever it is that Windows did, and I can go back to just using the Search LAN and letting Corona add the nodes by itself.
I still suspect this was due to an update in Windows 10, that is preventing the Win 10 machines communicating with the other machines (which would mean it isn’t a Corona bug). For sure on not installing every daily build, but this particular one has the particular solution that you are looking for (and not very much else so it is pretty safe). Also, that’s always where any fixes come first, in a daily build, as it has to be tested first to make sure it fixes things and doesn’t cause any other problems.
It would be interesting to know if it resolves it - whether a case arises for their being a hotfix to Corona 2 or not would be dependent on whether this fix actually remedies that issue (mind you, if it does fix it, working with that daily build would mean not waiting for any other potential next steps).
Meantime, the DR logs would be important of course, to see what DR is doing at the time. You can use the private uploader for those if they can’t be shared here (Chaos)
Thanks!
The log is it the 1st post.
Ah, as an image - I was looking for it as the actual log doc 
Could you share full logs from the faulty nodes and also the Backburner logs? Here is how to get all of them: https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065
Make sure it’s not just the win10 firewall blocking the nodes from receiving the info, a quick test would be to just disable the firewall and see. The windows firewall is notorious for fucking up programs across the board.
Thanks for the advices. I was sure that everything is set up correctly, because the renderfarm has been working for a long time on. I described the problem and asked my system administrator to check the network settings. As a result, after a while, one of the nodes began to work, but the second one is not yet available.
I do not know what exactly he did, but I ask him to do it again.
These are attached logs from problem node:
CoronaMax2016_log.txt (521 Bytes)
DrLog.txt (859 Bytes)
Can you check if just closing the drserver and then starting it again does not help?
No, it doesnt.
Check the system time and date, system updates also, reinstall lan drivers..
Solved!
Attentive firewall and policy setup for Drserver.exe and check/uncheck “Search lan during render” helped me.
What kind of firewall is it? (what specific application)
What exact options did you change? Could you posy some screenshots?
Does it work now even if you disable “Search lan”, or does it have to remain active?
The reason I am asking this is that thanks to your answers we could:
-understand the issue better
-update our helpdesk
-help other users
Thanks in advance for any input!
This is standart Windows10 firewall. No specific application.
In the firewall, the permission for DrServer.exe for TCP and UDP protocol is registered separately. I have asked my admins for details, because they did it and helped to me.
Yes, it works now without “Search lan” option.
Admin created these two new rules for input connection for DR server.
In the top-left corner automatically created rule by installer, I thought. We leaved it.
same here… firewall makes troubles with DR
long time ago same troubles with vray…
