Log In
Home
03/08/2022
Offline
Has anyone seen anything on Windows Server 2019 that would prevent browsing the network in a Active Directory domain environment to find available OPC servers on remote hosts when all other OPC communications seem to be functioning normally and file share browsing seems to also be functioning. There is something I’m missing here, but I cannot find it. Since the core OPC functions are working, tools like OPC Expert are not showing any errors and guides for DCOM settings from OSIsoft, KEPware, and OSI Institute are all being used to no avail. None of the DCOM settings seem to be addressing the CLSID network browsing. If a client has the ability to supply a remote host and query that host, the OPC services enumeration works just fine. The problem is that we are attempting to use clients that do not have any features to manually define the servers and solely relies on the network browsing functions.
Please tell me someone else has seen this behavior.
04/13/2016
Offline
We have the same problem Matrikon OPC Explorer returns no results when browsing the Network Neighborhood. Our application that browses fails to connect to OPC Severs. Our only change was to upgrade the Domain Controllers to Windows Server 2019.
Do you still have the problem?
05/30/2017
Offline
Sounds like a firewall issue. Note that the behaviour will change depending on whether a network interface is a “private”, “public” or “domain” network. Check if you can use Windows Explore to browse the networks.
03/08/2022
Offline
In testing, Firewalls were disabled. The network can be browsed with Windows Explorer. The domain is at Windows 2019 level and all the members of the domain are Windows 10 or Windows Server 2019. Most of the servers that we are trying to browse are on Windows Server 2019.
@dwilder, When you upgraded the DCs to 2019, did you raise the functional domain level, as well? That could very well be where the issue lies, something in the structure of a 2019 domain.
1 Guest(s)
Usage Policy