I put a network standalone installation of Octane on a spare desktop that GPU upgrade recently, so as to help with rendering.
I cannot figure out why, but it refuses to see the master.
It is correctly on the network with defined IP address. It can see all machines and network devices like NAS and printer etc.
Try to run Octane NW and the CMD window that pops up shows it trying to connect to master ip address at 0.0.0.0 IP, rather than the 192.168.1.12 where it should be. The other two NW nodes run perfectly.
Same Octane version of course. I've also checked that Octane daemon is set up with same settings prior to running, and that's right too.
I've even tried running CMD line command specifically, telling it the designated master IP address and port - it then lists these as it tries to connect, but then does not complete the connection.
Windows firewall is clear, and is allowing Octane to communicate outwardly etc.
I am really stuck on this node.