When i try to restart a CentOS slave from one of our Windows workstations i keep getting this error:
The requested address is not valid in its context 255.255.255.255:5042
Strange thing is, all slave.ini files show the correct IP and MAC address.
When i change the windows hosts file, and map the ip to the slave/netbios name, it all works, this is however not a very good fix, as i can’t keep fixing the hosts files on all workstations whenever a new slave is added or changed.
The slaves are recognized on the network through their netbios names.
ipv6 on the slaves and workstations is set to ignore/disabled.
Any idea how to solve this? (besides editing all hosts files on all workstations)
Before you edited your windows hosts file, were you able to ping the remote machine using its machine name from a command prompt? Just want to confirm if it’s a Deadline issue or a more general name resolution issue.
Cheers,
sorry to get back to this so late.
Just tested it on a machine where the hosts file was not edited, and no, it is not able to ping the slave by name, just by IP.
So, not a Deadline problem apparently.
I find it odd though that the windows network discovery finds the hosts though, but i’m not able able to ping it by name in a cmd terminal…odd
Do you have any idea where i should look, as Google is not very useful with returned results.
Basically, the linux slaves have nmbd running, which windows explorer uses for discovery of names? But what does windows cmd and Deadline use for name discovery?
Sven
GOD!, i’m such a scatterbrained turd!
nmb and smb where NOT installed…sigh
Thing is, all our new blades had OCZ SSD disks for their OS, and since OCZ SSD are complete and utter rubbish (we’ve had over 60% of those SSDs die within 1 month) we cloned a wrong disk, one that DIDN’T have smb and nmb installed, which has me making an arse of myself on this forum and making me waste Ryan’s time…