Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Ive tried to browse to add OPCServers to my failover group, but the browsing is not working. What do I do?

0
Posted

Ive tried to browse to add OPCServers to my failover group, but the browsing is not working. What do I do?

0

This is very likely caused by the firwall settings at the remote node. To perform a browse of a remote node File and Printer Sharing must be opened (TCP 137, 138, 139, 445). Once the browse has been completed the ports can be blocked again as they are not used during the normal operation of OPCFailover. From OPCFailover V1.6 it will be possible to manually specify the remote node name and OPCServer CLSID instead of browsing. Once more, can you explain this CLSID and ProgID thing? Yes. When a client application wishes to make a connection to a server, it uses the servers CLSID to identify it. A CLSID is a 128 bit globally unique identifier and as such is quite difficult for humans to remember. To make life easier for people, a CLSID can have a human readable alias associated with it. This alias is known as a ProgID. The client application can then be configured to use the ProgID (human readable alias) to define its connection to the server. The computer will handle the job of converting

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123