Every time my slaves starts, I get this in the logs :
2012-04-03 14:33:34: Auto Configuration: No auto configuration could be detected, using local configuration
The problem is that I want to push the license server through the auto-configuration.
My slaves are on windows 7 and my pulse on windows 2008 R2.
Is there a chekbox that I have missed somewhere?
No checkbox. You’ll have to tell Pulse how to handle auto-configuration requests though. Information on how to do that can be found here:
thinkboxsoftware.com/deadlin … iguration/
Now, while you can use Pulse, the slaves should be able to automatically configure themselves on IPv4 networks on their own. I added the same mechanism we used for Pulse directly to our vendor daemon, but didn’t have time or equipment to implement IPv6 support.
The requirement for both is that broadcast packets are able to pass from slaves to either Pulse or the vendor daemon. Meaning if you have multiple subnets, the Pulse machine needs to be a member on all of them.
If you need more in-depth info, just let me know and I’ll explain more deeply.
Here are more info:
Pulse machine
FX-Pulse.frima.local
192.168.69.220
255.255.255.0
Render node
FX-Render-01.frima.local
192.168.69.91
255.255.255.0
Deadline Repository
FX-Deadline.frima.local
192.168.69.42
255.255.255.0
Licence server
ProdFlexMR.frima.local
192.168.69.221
255.255.255.0
Auto-config setting
Ruleset Name : License
Slave Filter : IPV4 Match : 192.168..
License Server : @prodflexmr.frima.local
All other options are unmarked
I use the default port (5043) for the auto-config, and firewalls on all machines are disabled.
I still get the “No auto configuration could be detected” problem
Does it work if you change the IP4 Match wildcard pattern to: 192.168.69.*