- v6.1.0.54178R
- Repository: OSX Server 10.6.8, Monitor: OSX 10.8.5, Slave: Win 7 Pro SP1 and OSX 10.8.5
- Cinema4D
- We have a mixed pool of Deadline Slaves, half Windows 7 Pro and half OSX. I’ve got the Deadline Monitor installed on a Mac (OSX 10.8.5) and when I try to control a Windows-based slave (connect to slave log, restart slave, etc…) it states ‘Connection refused’. That same Mac can successfully control the OSX slaves. I also have the Monitor installed on a Win 7 Pro machine and it’s able to perform all remote control functions to both Win and OSX slaves.
Is there a specific setting that needs to be adjusted on the OSX monitor or the Windows slaves to enable OSX to remotely control?
Can you ping the Windows machine using its host name from a terminal on the Mac? I’m guessing it’s just a DNS issue, and the Mac is unable to resolve the Windows machine via its hostname.
Cheers,
Ryan
Thanks for the suggestion, Ryan.
Initially, the answer to your question was no. But I enabled network discovery and file sharing on the Windows box and can now successfully ping the machine using its IP address and hostname. However, I still can’t use remote functions or connect to the slave log. Any other recommendations?
-Dylan
Hmm, strange. Can you try modifying the slave’s properties in the Monitor and specify the machine’s IP address as an override (see attached image)? Perhaps that would help…
The Host Name/IP address override works! But only if an IP address is provided – hostnames aren’t working (e.g. COMPUTER.local). I also tried the option to ‘Use Slave’s IP Address for Remote Control’ in the repository options but the slave log stalls on the initial ‘Connecting’ message.
The IP address fix isn’t ideal, but it’ll get us up and running, thanks for your help! I’m going to continue to investigate the issue – I think we have funky hostname problems on our network.
Dylan, one thing you could try for improving hostname resolution in a mixed Windows/Unix network is assigning a WINS server. Many routers offer WINS as do Synology NAS, but regular machines can also host the service. You then need to configure samba on all the unixy-type machines to include WINS in their hostname resolution. For example on Ubuntu this is done in the nsswitch.conf file. (It may be necessary to install the winbind package too). The exact approach varies a bit from one platform and distro to the next, but if you Google “WINS on [platform]” you should find helpful blog posts to get it set up.
Thanks, Coulter! I will check it out!
