Railpro Assistant connection issues

[snowdog]

I'm hoping there is a fix for this.

I'm running Railpro Assistant AND HC Simulator on my Linux box (Thanks to G8B4Life) and have an issue with Railpro Assistant. I can get it to connect to the server (usually on the first try) but after the first file is installed, it loses connection. I then have to restart my computer to get it to work again. This also happened when my box was Windows so I don't think the OS is the issue.

Has anybody else experienced this? Is there a fix? Or a workaround?

Thanks in Advance,
Snowdog 

[G8B4Life]

I've not encountered that before, but I've not used RPA for a long time. I'll have to get a Linux distro running in a Virtual Machine and see if I can replicate what your experiencing though because you say it happened on your Windows PC as well it kinds of points to an issue outside of your PC. ie between your router and Rings server. I can't see why you'd meed to reboot your PC to be able to connect again though.

To clarify the connection being lost is the one between RPA and Rings server and when you say installed you mean downloaded from the server into RPA and HC Sim?

- Tim

[snowdog]

hi Tim,

I thought that might provoke a question after I posted. After I do a download of one or more files (doesn't matter what type) and install them onto either the HC or the LM3 and I realize I forgot a file. I go back to grab another file off the RP server and the RPA shows that it's "Not connected". No matter how many times I close RPA and restart it, it won't reconnect until I do a complete restart of my linux box...

BTW, Ubuntu 24.x now 25.x is pretty darn cool!

Bryan

[G8B4Life]

Well I didn't get a successful install on Debian, RPA and HC Sim couldn't see each other. I'll have to try something else...

A thought in the meantime, I wonder if this is a manifestation of a peculiarity I observed years ago. If the port used by RPA is not being released by your system when you close RPA when you reopen RPA it won't be able to get that port and it won't be able to connect; at least this was the behaviour in 2021 (I doubt it's been fixed.).

You should be able to test for this in the terminal (I haven't checked this myself yet). Open RPA and then type in the terminal "netstat -tunlp" without the quotes (you may have to use sudo). Your looking for a entry under local address with the port 4608, and a foreign address that starts with 99. If you have it then close RPA and type the netstat command again, that entry should be gone.

- Tim