12-19-2013 03:46 AM
I'm having exactly the same problem Wire Warrior had: not being able to change the hostname on my WSN gateway due to this bug in LV2013. And also the responded IP address is 127.0.0.1.
I hope NI can fix the bug soon.
I just wanted to join the cause. XP
12-19-2013 08:37 AM
The work around will get you going at least.
WW
12-19-2013 08:37 AM
Hi Alejandro,
Good news! This bug has been fixed as part of the System Configuration 5.5.1 release. The underlying issue is listed on the bug fix list. The problem was caused by a mismatch in the IP address returned with a localhost session opened on a real-time target. Upgrading to 5.5.1 should fix the problem. Please let me know if it doesn't!
12-20-2013 03:25 AM - edited 12-20-2013 03:26 AM
Thanks for your your reply! I still didn't downloaded the new upgrade but it's good to know.
I was using the workaround and also some trick to go around the IP Address but I guess it will be easier from now on.