Server - Client connection - Discovery Issues

[Esma]

Hello,

We started developing our UA Server with help of the sample lessons. Therefore, end point configuration of our server is very similar to the one in the demo server.
On our development machines, the UA Client application (that we had to use) was able to discover our server, connect it, and correctly browse it. (as well as UAExpert)

However, on different test machines, we faced with a big problem: On one of these machines, everything works fine. However, on many of the others, the client application is even not able to discover our server.
As far as we know, the machines have min-installations: Operating System + the same server-setup and client-setup.
So, it seems that we miss some point. My question is :
- Which configuration issues we should focus on to understand the problem? (Windows 7 32 bit versus - Windows Server 2008 makes difference?, registry issues?, UA.DiscoveryServer service?, opening the port that is used as end point URL?, ... )

- And another small question; if on the same machine, one UA Client is able to connect our server and another UA Client (with older UAStack!) is not able to; what could be the reason? Can we easily say that: UAStack versions must be the same?

[Support Team]

Hello Esma,
when you are facing the connection problems are you trying to connect remote or local?
Maybe you are having problems with the resolution of the host names. Try configuring the server endpoints with IP address instead of hostname. Therefor you can edit the ServerConfig.xml file and replace the entry opc.tcp://[NodeName]:4841 with your IP address.

Best Regards,
Unified Automation Support Team

[Esma]

Hello,

Our first problem is resolved (We realized that each client application was not configured in the same manner in different machines.)
However, the second problem still exist. Here is the scenario;
First of all, we are using local discovery server, local ua clients and local ua servers.

When we start our UATestClient and UADemoServer, the UATestClient is able to discover and connect to UADemoServer.
Then we close UADemoServer and also restart UATestClient.
When we start our own UAServer, the UATestClient is NOT able to discover our UAServer; however, UAExpert is able to discover it.
So, we are not able to understand which application (UATestClient or our UAServer) has a missing/erronous point since they are able to work with some other servers/clients.

NOTE: In srvTrace.log, I saw the following error message: Error: Registration with Discovery Server failed [ret=0x80ae0000]
However, as I mentioned, some other ua clients like UAExpert, is able to discover the server at same time..

[Support Team]

You have to check which server is used for discovery.
The OPCF discovery server is running on port 4840. The UADemoServer is running on port 4841. In the UaExpert you can configure the discovery URL the Add Server dioalog is using.

Check which URL your client is using for dicovery.
If the server logs "Registration with Discovery Server failed" you won't find the server when browsing the discovery server.
To register at the discovery server the server certificate needs to be trusted by the discovery server. You can use the UA Configuration Tool (installed with the discovery server) to trust your server certificate.

Best Regards,
Unified Automation Support Team