Sorry, I do not understand the question.
I thought you were saying that your next step will be to place the publisher on a different machine from the subscriber, which seems like reasonable thing to do.

I am trying to find some tool that is not from us AND is not a network analyzer like WireShark (because that goes a different route to the network), and can either listen to specified UDP multicasts, or allows some easy UA PubSub subscriptions like OpcCmd. Because if such tool had worked, we have to diagnose our software deeper. But if it had not worked, then my knowledge - and my task - ends there - it would be something in your system that I am afraid we cannot help with.

Unfortunately the tools I have found so far were either 1) for Linux, or 2) needed to be built first (source code only) - which makes it less attractive.

Regards

Hello.

Please come back here later then wither way, we need to find a solution.

Best regards

Hello.

I myself (always using the built-in Windows Firewall) have not seen issues with the firewall blocking the OPC UA PubSub. But, when Googling around, it seems that the Windows Firewall can be blocking the incoming UDP. And certainly other firewall products. So turning any firewall off just for the test would make sense.

Best regards

Hello,

yes, we have a demo publisher. But I do not put much hope into using it. Since you can capture the packets using WireShark, it is much more likely that the publishing side is OK.

In QuickOPC Launcher, you can either

1) Start Tools -> OPC UA Demo Publisher. This use the default (=some) network card.
2) Start Tools -> OPC UA Demo Publisher (Interactive Mode). Then you can enter e.g.

The default multicast IP address and the port are the same as yours.

Best regards

Hello, and thank you.

Do you have any other OPC UA subscriber that you can use to check if the problem is confined only to our software, or is something more broad? Frankly, I think it si something outside of our software that we cannot influence.

Also, an idea: There are indications - even in Beckhoff documentation such as infosys.beckhoff.com/english.php?content=../content/1033/tf7...tc3_vision/6802889227.html&id= (although for a different product - not precisely what you are doing), - that the check you have enabled, "Promiscuous Mode (use with Wireshark only)" can indeed have bad consequences if it is used for other purposes. So while I understand it might have been needed to verify the functionality with Wireshark, I suggest that you now turn it off, and repeat the tests (various conbinations). Please only use OpcCmd, because as I wrote, the other approaches might have additional problems.

Best regards