OTOY Forums

Have you already run uninstall_daemon.bat andthen _install_daemon.bat
and run _installed_daemon.bat again?

As I understand it, auto-configure is only needed when running more than one master, which I am not doing. However, I did so anyway (and have done so periodically) with the same result. Now, I would not expect anything different in this regard, as the slave is looking at port 21000 for the master. That said, I will leave auto configure enabled, and change the slave to look at port 125 and see if that makes any difference.

rappet wrote:Have you already run uninstall_daemon.bat andthen _install_daemon.bat
and run _installed_daemon.bat again?

No, I have not yet done that. I will do so now.

OK, I uninstalled, then reinstalled and ran the daemon on the slave. Same result, including making the daemon look for port 1025.

I'm now going to try to run the scripts on my master and see if that makes any connection in the reverse...

And again, no difference. I am officially out of ideas...

When I started with networkrendering I also had troubles gegting there.
I had to allow Octane daemon by my firewall (from Panda security) to make the connection after all.
I believe the window firewall automatically took over when I disabled my Panda firewall .

And you do not have the slave daemon running on the master, right?
(Run it only at the slave pc)

I'm really surprised by how crude this process is, given the selling point of network rendering. More than a few of us here have built Octane-specific slave machines at considerable cost, and more are doing so every day. First, just finding a concise step-by-step of complete instructions and troubleshooting tips is difficult, forcing a dependency on the (very fortunate) generosity of the community. Then, the lack of almost any install/diagnostic tools to help ascertain any issues.

I might just transfer over to work on my slave machine. Had on done so in the first place, I would not have needed to purchase that additional license of Octane. Who likes wasting money?

I hope that I can get this running soon. I also hope that OTOY recognizes that more work needs to be done to support network rendering installation and diagnostics. Aoktar states (I believe correctly so) that he can do little on his end, as this is an Octane core function. It should not be this hard to do. I mean, it's 2015....

It works great when you get there.
Probably it is due to something obvious when having this solved.
Others, maybe Abstrax , might help you better then I can.

Your printscreens seems ok to me btw, so it might atill be something of allowing connection.
If I were you at this point I would enbale the firewall again, then
Restart the pc, trying to connect again by start daemon and this way force a popup of your firewall to allow the connection.

Good advice. I'll try that again, thanks!