Installing 3ds Max 2016 as a render node?

[richard_rosenman]

So maybe the reason I'm not experiencing problems is due to my server running the manger is only using IPv4.

Well, looks like I had already been down that path - lol. Just checked the manager and IPv6 was already disabled. If I re-anable it, it gets stuck on trying to connect to 127.0.x.x.

Would it be easier to configure Remote Desktop to use IPv4 (if that's even possible) and instead change that since the nodes render fine with IPv6 disabled? All I need is to have Remote Desktop working. I could switch to another like VNC as Vlado suggested but that's a huge task to do it to all the rendernodes and I'd prefer not to.

-Rich

[richard_rosenman]

Also, just tried Backburner 2018 and I get the exact same error on the render node.

-Rich

[Donald2B]

Well, looks like I had already been down that path - lol. Just checked the manager and IPv6 was already disabled. If I re-anable it, it gets stuck on trying to connect to 127.0.x.x.

Would it be easier to configure Remote Desktop to use IPv4 (if that's even possible) and instead change that since the nodes render fine with IPv6 disabled? All I need is to have Remote Desktop working. I could switch to another like VNC as Vlado suggested but that's a huge task to do it to all the rendernodes and I'd prefer not to.

-Rich

Man, I'm at a loss here.

RDP works across both IPv4 and IPv6 without issue. You just have to enable "Allow remote connections to this computer". Then you have to make sure to turn off windows firewall or setup to allow RDP traffic through.

I just type in the computer name and I'm good to go. So I'm not sure why you are having such an issue with IPv6. UNLESS you DHCP server (machine / device) is NOT handing out IPv6 addresses to the machines on the network.

[richard_rosenman]

Update: I believe I have solved it.

1 - I disabled IPv6 on the render node. As mentioned previously, this allowed the render node to properly connect to the manager and render but it breaks Remote Desktop and I could no longer remote in to check the node.

2 - I disabled Windows Firewall on the render node and I could then remote desktop back in, to the now non-IPv6 render node.

My guess is that with IPv6, remote desktop already had Windows Firewall rules that allowed it to log in. I assume that when disabling IPv6 and falling back to IPv4, these rules didn't exist and the firewall was blocking remote desktop.

Disabling the Firewall fixed that. At least that's my hunch. Curious to hear if that's what you think it was.

I wanted to say thank you to everyone for the help on getting these render nodes working. It's a community like this that is invaluable when it comes to helping one another.

Regards,
-Rich

[Donald2B]

Yep! Windows firewall strikes again!

I have a hardware firewall so I disable the Windows Firewall on all of the machines / servers / rendernodes.

I'm glad you got it all sorted out!

[Syclone1]

Glad you are up and running Richard,
My smaller farm is all IPv4 and like Troy I have a hardware firewall and my render slaves are actually blocked from accessing the internet and have all the winblows firewalls disabled. If I do need to access them remotely I can RDP into my main puter and then from that one RDP in to the slaves, sounds weird but works well lol.

[flino2004]

I use hamachi with ip6 from there and it works