Hi, I'm trying to connect Wincc Pro V15.1 (siemens) to a sample server from this github (the Quickstart Empty Server for instance) remotely.
What I have done is create a remote Virtual Machine, then run the Empty Server in that VM. Then the remote Server url is something like this: opc.tcp://52.255.171.136:62546. Set the AutoAcceptUntrustedCertificates in xml config file to true.
Then in my local laptop, I have use a sample client/ UAExpert Client/ Prosys Client and test remote connection to that server, and all of them is successful.
The problem is, when I use Wincc Pro and create an OPC UA connection, it always shows this message: "Cannot resolve IP address opc.tcp://52.255.171.136:62546. Try computer name instead".
At first, I thought that my setting of Wincc does not allow the Wincc to connect with remote Server. But the problem is, my Wincc can connect to this server successfully: opc.tcp://opcuaserver.com:48010 (the demo opc ua weather server).
If the connection via UAExpert Client is working, the problem seems to be on WinCC Pro site. Could you test with the DNS name of the virtual machine like opc.tcp://myvirtualmachine:62546.
Hi, I'm trying to connect Wincc Pro V15.1 (siemens) to a sample server from this github (the Quickstart Empty Server for instance) remotely.
What I have done is create a remote Virtual Machine, then run the Empty Server in that VM. Then the remote Server url is something like this: opc.tcp://52.255.171.136:62546. Set the
AutoAcceptUntrustedCertificates
in xml config file totrue
.Then in my local laptop, I have use a sample client/ UAExpert Client/ Prosys Client and test remote connection to that server, and all of them is successful.
The problem is, when I use Wincc Pro and create an OPC UA connection, it always shows this message: "Cannot resolve IP address opc.tcp://52.255.171.136:62546. Try computer name instead". At first, I thought that my setting of Wincc does not allow the Wincc to connect with remote Server. But the problem is, my Wincc can connect to this server successfully: opc.tcp://opcuaserver.com:48010 (the demo opc ua weather server).
Have you ever faced this problem before?