Discovery GetEndpoints on opc.tcp

[loic3484]

Hello,
Since the last Update of Ua expert I have this issue :
"Discovery GetEndpoints on opc.tcp://xxxxxxx (BadHostUnknow).

Before it used to work perfectly.

I used to get those two warning:
"GetEndpoints failed using the discovery URL opc.tcp://ShortName:4840 returned from FindServers. Do you want to try the URL opc.tcp://172.24.0.18:4840 with the hostname used to call Findservers"

I used to say Yes, Then Have a secodn one:

"The hostname of the discovery URL used to call GetEndpoints (ml_fgss_met) was replaced by the hostname used to call FindServers(172.24.0.18). Do you also want to replace of the EndpointsUrls with this hostname."

I used to say yes also !

But now it is not working I just get an error now.

[Support Team]

Hi,

we have not changed anyting in the hostname/IP-Adress replace logic lately.

Typically the UaExpert expects the network to be able to resolve hostnames.

• If you use hostname in "Custom Discovery" will run in timeout (and return BadHostUnknown).

• If you use the IP-Adress instead in the "Custom Discovery" you may run into two more errors:
  1) run into timeout (and return BadTimeout) in case the IP does not exist,
  2) or run into BadCommunicationError in case the IP exists, but server is not running.

Assuming the FindServers(using IP) is successful, the UaExpert will use whatever was returned by the server in the following GetEndpoints call.

• If the server returnd again some hostname the UaExpert will use that (and again run into the error BadHostnameUnknown)
  -> but than UaExpert is asking to replace hostname with IP adress (which already worked previouly when calling FindServers)

Assuming the GetEndpoints(using IP) is successful, the server returns several EndpointDecriptions

• if the server again returns EndpointDescription having hostnames in all the EndpointURL
  -> than UaExpert is asking to replace all these with IP as well.

You can see that in UaExpert in the tooltip when hovering over the tree view element.