None of our computers will shut down through deadline.
I tried the Magic Packet Sender App.
I told it to listen and it didn’t hear anything.
I tried sending a magic packet through another machine using the Magic Packet Sender and the app notified me it received it.
Could it be that Deadline isn’t getting the correct MAC address? How would I check this? And if it is the problem how would I tell deadline to update the mac address in memory?
We can shutdown the system fine through command line. But not through deadline.
If I launch the Deadline Network Configuration program. It shows All of the machiens “online” properly. But under Launcher Version all of the slaves running as a service are listed as “Launcher version: no response” also under MAC Address it has nothing listed so I think it’s ?Unable to get the Mac Address from a machine running its launcher as a service?
If I run “NbtStat - A 192.168.94.151” (The ip) I can get the mac address. So it’s certainly possible to do through a service. I think it’s just a bug in reporting.
Hi Gavin,
I’ve logged this as a bug, and we’ll look into it. I should note that the MAC address is only required to start up the machine when it is offline using Wake On Lan, and the Magic Packet application is only meant to test if your machine is receiving the magic packet that tells it to wake up. 
Cheers,
Hmmmm… Any idea then why we can’t shut down remotely? Something I can test on my end to give you more info?
I can do it through CMD. But if I send it through deadline nothing happens.
Sorry, I forgot to mention to check if Remote Administration is enabled under the Launcher Settings in the Repository Options in the Monitor. This needs to be set to True so that the Launcher on each machine will listen for remote control commands (like shutting down the machine).
Cheers,
No dice. Remote administration was already enabled.
This might be a dumb question, but is the Launcher running on the remote machine that isn’t shutting down?
Also, could it be possible that some security software (ie: antivirus or firewall) is preventing the communication? In the error you posted earlier, it’s showing that the port being used is 5042, so maybe you need to make an exception for this on the remote machine. We have tested this here and it seems to be working fine. Note that the same type of communication is used for all remote commands (ie: starting/stopping the slave, etc), so in your situation this problem is probably more widespread than just not being able to shutdown the machine remotely.
Cheers,