Unusual Hex-like windows slave IP when using EC2

Deadline
1

Hello all

When using windows instances as slaves on Amazon’s EC2 the IP address reported in Deadline Monitor seems to be in an odd IPv6 hex format.

Here’s an example: fe80::488:c0c:c9b7:79c1%13

What might be causing this? IPv6 isn’t turned on for the slave network adapter.

Because of this issue, unless I un-tick “Use Slave’s IP address for Remote Control” in the repo options I can’t ping or connect to the Slave logs, however turning off this option interferes with connecting to nodes on the other side of our vpn so is not ideal.

Dave

2

Hello Dave,

So in looking this over, I want to just verify that the you fully disabled Teredo tunelling for IPv6. If you haven’t, the steps on how to can be found at lonesysadmin.net/2011/04/25/how- … t-windows/ and this should then revert to only IPv4 addressing.

3

Turns out I hadn’t properly disabled IPv6, those instructions did the job however and now the IP address is showing as expected.

Thanks!