DHCP Address discovery
Posted: 14 May 2020, 10:50
Hello,
It is more of a feature or a bug. Currently, when specifying the IP address of the discovery server UaExpert finds the server. However, when afterwards trying to connect the error as follows occur:
It is due to the DHCP server, which responded to initial Discovery with the assigned name, and it is used to connect to, for example:
It replaced the IP address to arm; but the local PC does not know who is arm as it is gained from the DHCP of embedded device.
The workaround to this problem is to go into Server's properties, and replace "arm" with the actual IP address.
It then connects fine and discovers all the nodes finely.
The question/topic is if that behavior of changing the IP address of the server with the response of the DHCP server is desirable.
It is more of a feature or a bug. Currently, when specifying the IP address of the discovery server UaExpert finds the server. However, when afterwards trying to connect the error as follows occur:
Code: Select all
[uastack] OpcUa_P_RawSocket_InetAddr: Unexpected error in getaddrinfo: 11
[uastack] OpcUa_P_ParseUrl: OpcUa_P_RawSocket_InetAddr reports error 0x80000000.
Could not connect to server: BadCode: Select all
Adding Url opc.tcp://arm:8888The workaround to this problem is to go into Server's properties, and replace "arm" with the actual IP address.
It then connects fine and discovers all the nodes finely.
The question/topic is if that behavior of changing the IP address of the server with the response of the DHCP server is desirable.