Ok, we’re using realport from a Windows 10 x64.
Realport versin is 4.7.410.0.
We are using OpenVPN on the computer as a server and having the Digi connect to the server over the OpenVPN, that part works just fine, perfect in fact.
Here is our problem. I go to device manager, select Multiport serial adapters, S9Digi(that is our name) and select properties. In advanced I click properties and then click on Port1(Com10 in our case). On this page you see a small box called port status and the item in question is “Device Port:” which has a rest status of “Not acquired”.
Here is the problem, after a Digi reboot and VPN reconnection, which takes about 60 seconds, netstat -a -p tcp -n shows 192.168.254.2:771 connected, the real port is up. It shows as connected in Connections-IP Connections on the digi as well.
When I open up our application on the computer and try to connect to COM10, the Port Status changes to “Aquiring…(Xth try)” where X continually counts up and the application continues to attempt the connection. If I open up a cmd.exe session and type mode, only COM1 appears. As soon as the application’s connection attempt times out, I type mode and COM10 is there.
The only way to fix this is to go into the Digi-Configuration-Network-Interfaces-Serial-Serial Port 0 and do any of the following:
- Toggle “Enable Echo”, OR
- Toggle Flow Control" to HW or to None…or None to HW,
Click save and then I attempt to connect using my application and it works fine. It will continue to work fine until the router reboots, after which I need to do one of the methods above.
Does anyone know w trick on how to get the Digi to do this itself?