Log In
Register
Forum
Topic RSS
19:21, EEST
November 11, 2020
Offline
Hello,
To my great distress I found in the documentation (section Limitations) of the latest version (1.5.10) of the UA Gateway a blown up version of the earlier:
No Remote DCOM Connections
Apparently I wasn’t the first to have missed the old two-liner version of this section (or why would blow it up with a hure picture and more warning texts)
To my knowledge this quite severe limitation is nowhere else mentioned. It is also quite odd, as the whole idea of DCOM (D for Distributed) is to have remote connections.
The text however is less definitive than the old one. Actually the new text doesn’t say it cannot be done, just that it isn’t supported.
Which means that someone knows, at least to some extend, how it can be done.
My problem is that I cannot place the UAGateway at the same server as the OPC server. There is a categorical NO there.
So if no remote connection is possible, UAGateway is useless to me and I have wasted quite a lot of money on it.
So my question is whether anyone can help me with or give me a hint or a direction to search on how to accomplish a remote DCOM connection.
16:02, EEST
Moderators
February 1, 2019
Offline
Hello,
Remote DCOM is not tested on UaGateway and is out of the scope for warranty or our technical support. Additionally, Microsoft is hardening DCOM connections in Windows due to security concerns, which makes DCOM connections even more troublesome. See https://opcfoundation.org/forum/classic-opc-da-ae-hda-xml-da-etc/microsoft-dcom-update/ for more details. Therefore, the generic recommendation is to always install UaGateway in the same computer with the OPC DA server.
However, with proper configuration, DCOM technically works on UaGateway. You can find some instruction on how to create a connection between a remote OPC COM DA server and UaGateway at https://documentation.unified-automation.com/uagateway/1.5.10/html/dcom_sec.html. Please note that this instruction is only intended to provide hints for the “out-of-support” use case and does not guarantee a successful DCOM connection.
15:51, EEST
November 11, 2020
Offline
Hello again,
I need to come back at this issue since Microsoft’s hardening of DCOM connections seems to have more impact than I thought at first.
It is not entirely clear to me whether UAGateway will continue to work remotely when the hardening requirements are enforced?
And I understand I need to change the DCOM configuration at the server side, but do I need to do anything at the UAGateway side?
Thanks,
Reinier
18:11, EEST
December 21, 2011
Offline
It should be enough to update UaGateway to the latest version.
On the server side, you have still the option to disable the hardening, until March 2023.
Once the hardening is applied, only clients that have been updated respectively, can connect. But as said, te latest version of UaGateway should work fine.
You can check this article that I wrote for more details.
Most Users Ever Online: 1919
Currently Online:
41 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 734
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1523
Posts: 6449
Newest Members:
christamcdowall, redaahern07571, nigelbdhmp, travistimmons, AnnelCib, dalenegettinger, howardkennerley, Thomassnism, biancacraft16, edgardo3518Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1026, Jimmy Ni: 26, Matti Siponen: 346, Lusetti: 0
Administrators: admin: 1
