RailPro > RailPro Specific Help & Discussion

Cannot Connect to RailPro Server

<< < (3/5) > >>

Alan:

--- Quote from: G8B4Life on December 19, 2019, 06:45:47 PM ---Looks like I might need to test Avast too.

Alan, what blocking does Avast do? Is it the firewall blocks the connection or does Avast pick the program up as a threat (malicious or potentially unwanted program)? If it's a threat/pup it's reporting I'd expect Avast to question you on what you wanted to do (quarantine or ignore) and I'd expect Nod32 to do the same. I've only ever once had an antivirus not let me access/run a program regardless that I specified to ignore the threat but I've run some truly questionable (to an Antivirus program) software in my research before, much more dubious than RPA so I'm kinda surprised that Avast, and possibly Nod32 would flag RPA to the level of not being able to ignore it permanently.

- Tim


--- End quote ---

Picks up the program as a threat. Avast does give you the option to ignore and proceed. Works as expected afterwards. Windows Defender same same.


G8B4Life:
Thanks for the info Alan.

It would be possible to submit RPA to Avast as a false positive (https://www.avast.com/en-us/false-positive-file-form.php) however I don't use Avast and I'm not giving them my email address so they can send me junk for the privilege of reporting the false positive. It might be worthwhile for someone who does use Avast (and has given Avast their email address previously) to file the false positive report.

Anyway, back to waiting for the OP to come back with anything further.

- Tim

Alan:

--- Quote from: G8B4Life on December 21, 2019, 07:36:09 AM ---It would be possible to submit RPA to Avast as a false positive.
- Tim

--- End quote ---

Already did. Twice when I first purchased RP. Also made Tim Ring aware of the Avast submission at the time.

DavidMcC:

The port test to the PAT Test site gave me tests that both fail and are probable passes.

PAT Test  for RailPro
Test Results
---------------
Your IP Address: 24.45.178.133
Sockets created

Result
1  4608  4608 55072  Fail.
2  9121  4608 55072  Fail.
3  4608 57253 57253  Probable Pass. 
4  9121 57254 57254  Probable Pass.
5  4608  4608 55072  Fail.
6  9121  4608 55072  Fail.
7  4608 57255 57255  Probable Pass.
8  9121 57256 57256  Probable Pass.
9  4608  4608 55072  Fail.
10 9121  4608 55072  Fail.
11 4608 57257 57257  Probable Pass.
12 9121 57258 57258  Probable Pass.

I am guessing that probably means CGNAT and that I am out of luck for now.

G8B4Life:
It certainly appears to be CGNAT but there is something about the results I was not expecting.

In the first, second, fifth, sixth, ninth and tenth tests columns 2 and 3 do not match (Fail). This is a hallmark that Port Address Translation (CGNAT) is being used. That column 3 is the same number in those tests was not expected.

The rest of the tests displayed expected and unexpected results. As expected the port numbers in column 3 are increasing by one each time the test is run but the fact that column's 2 and 3 are the same is unexpected. In this scenario it appears that your PC has chosen port numbers that just happen to match the range allocated to you by your ISP (fixed range allocated to you) or that your ISP is using a dynamic port range which I think is the case.

The fact that the first, fifth and ninth tests failed with a changed source port and these are the tests that use both the same source and destination ports as RPA yes you are pretty much out of luck at the moment. I've got no idea how long it'll take me to implement a CGNAT breaking proxy for RPA (there is only one thing I can not figure out how to do yet that is stopping it) so my suggestion would be to take any or all of the suggestions I made in my first post.

- Tim

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version