We are experiencing an odd issue with Distributed render and max 2015, any help is greatly appreciated.
MAX 2015 SP3 Ext2
V-Ray 3.10.03
Deadline 7.0.2.3
Description:
Use Deadline DBR script using Host Name or IP and Vray throws the following error (where XXX = IP of target machine):
Warning: Could not connect to host xxx.xxx.xxx.xxx:xxxxxx: No connection could be made because the target machine actively refused it.
This warning occurs with any file and all target DR machines in the DR list.
If you direct DR by manually running the vray spawner on the target render node it works though you must first clear the DR list in Vray then add the machines back to the list. Using IP or Host name works.
I wanted to verify if the same port number is being used in both instances, and if not whether it’s being blocked when Deadline is trying to use it, or perhaps Deadline is not using the right port number in your submission. Can you verify?
V-Ray v3.x uses TCP/UDP 20204-20206. It’s hard-coded. Many of the other V-Ray DBR implementation in various other DCC 3D apps, allow the port number to be configured. However, that is not the case with V-Ray DBR in 3dsMax, with the exception of if your using V-Ray RT, which uses standalone V-Ray and hence, the port number 20206 can be tinkered with. It’s all further confusing, as the port numbers change between V-Ray v2.x → v3.x. (I have updated the V-Ray DBR docs in Deadline v7.1 to explain the different port numbers in V-Ray v2 vs. v3 for each DCC app.)
If VRaySpawner runs fine manually, then I would guess that DeadlineSlave being blocked through your local Windows firewall client or port conflict as Dwight mentioned. Remember, that when Deadline is running the ‘show’ on the slave, the VRaySpawner.exe is a childProcess of the DeadlineSlave.exe process, so if it’s being blocked, then children die…[perhaps best to not read that last bit in the literal sense]
This error message is when your trying to send a remote command to one of your slaves? If so, this is typically the firewall blocking comms.
I would work your way through this checklist and ensure all firewall exceptions/configuration is in place. I find it a really handy list to double-check everything is configured correctly for hassle free rendering: docs.thinkboxsoftware.com/produc … tions.html