使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


Can I Use a VPN to Connect to an OPC DA Server on a Remote PC?


Last Update: 2018/11/12

No; however, Kepware provides an OPC UA Tunneling solution using the OPC UA Client Driver that allows the OPC DA client to establish a local connection to KEPServerEX V5 (which is both an OPC UA and OPC DA server). The OPC UA Client Driver then establishes a connection to KEPServerEX V5 on the remote PC. For more information, refer to OPC UA Tutorial.

Unfortunately, users cannot get requested data back to the client from the server when using OPC DA over a VPN connection. This is because OPC DA is designed using Microsoft's Component Object Model (COM) and uses Distributed COM (DCOM) for remote connectivity. When a connection is established to a remote server, and data requests are made by the client, the server will send callbacks (which are unsolicited messages from the server, like data change events) to the IP address that made the connection. When connected to a VPN, it will broker a local IP address on that network. When an OPC DA connection is established through a VPN, the brokered IP will be used not the IP of the PC with the OPC DA server. All callbacks to the client from the server will be sent to the brokered IP. The VPN does not have the ability to route the callback to the local OPC DA client.

Tags
DCOM