I wrote a response some time ago explaining the protocol utilized by the 536 dongle for remote control and audio. I don’t current have access to that as I’m on my iPad at a remote location myself.
However, in general, the 536 uses a port for control via a very simple ASCII set on commands. Using a network capture program like WireShark it is very simple to capture and identify that. Also easy to port forward that from your external IP address.
The audio is much more difficult which uses industry standard RTTP or Real Time Transport Protocol. The problem with port forwarding this is that the RTP Control frame at startup negotiates several random data ports between the server and client. These are not a static assignment but rather dynamic depending on what is available inside your network.
I have not captured how ProScan server/client is doing this so don’t know if it is similar.
Also in terms of the problem being discussed in this thread, the 10.0.x.x address is the Wide Area address assigned to the router by your ISP. This address will be different for every person’s router. So I’m not sure you are using the correct external IP.
Internally, the port forwarding must be routed to your local 536 network address which will be something similar to 192.168.x.x.
Not reading this thread fully, I’m not sure you guys are using the correct IP addresses.
Sent from my iPad using Tapatalk