Posted: 14 Apr 2015, 05:49
Yesterday I tried joining online session but couldn't get it working neither via RVHouse lobby nor via direct IP. I was sure though I had forwarded my ports exactly as recommended by RVHouse documentation, and I had also disabled my firewall network monitoring during the tests.
My ports forwarding setup was:
2301 TCP
47624 TCP
2300-2400 UDP
If I'm not mistaken this is exactly following RVHouse recommendations.
But today while trying in LAN at home I noticed in my firewall log than one computer was trying to reach 2300 TCP, and it occurred to me that this was not in the ports forwarding range (UDP would, but not TCP). That could explain why I couldn't get it working with remote players on Internet (while it works in LAN).
I checked Microsoft recommendation and noticed they mentioned both TCP Inbound 2300-2400 and UDP Inbound 2300-2400 (as well as TCP Connection 47624 Inbound of course). It means that range 2300-2400 has to be forwarded not only for UDP, but for TCP as well (and in that case the port 2300 TCP I noticed today is now properly included).
So today I updated my ports forwarding setup to:
2301 TCP <-- no longer needed
47624 TCP
2300-2400 UDP
2300-2400 TCP <-- new
and I could join (with mmudshark).
So the question is: are the RVHouse documentation wrong or outdated? (as it has to be noted it does not follow MS recommendations). Anyone has more info / knowledges about that topic?
My ports forwarding setup was:
2301 TCP
47624 TCP
2300-2400 UDP
If I'm not mistaken this is exactly following RVHouse recommendations.
But today while trying in LAN at home I noticed in my firewall log than one computer was trying to reach 2300 TCP, and it occurred to me that this was not in the ports forwarding range (UDP would, but not TCP). That could explain why I couldn't get it working with remote players on Internet (while it works in LAN).
I checked Microsoft recommendation and noticed they mentioned both TCP Inbound 2300-2400 and UDP Inbound 2300-2400 (as well as TCP Connection 47624 Inbound of course). It means that range 2300-2400 has to be forwarded not only for UDP, but for TCP as well (and in that case the port 2300 TCP I noticed today is now properly included).
So today I updated my ports forwarding setup to:
2301 TCP <-- no longer needed
47624 TCP
2300-2400 UDP
2300-2400 TCP <-- new
and I could join (with mmudshark).
So the question is: are the RVHouse documentation wrong or outdated? (as it has to be noted it does not follow MS recommendations). Anyone has more info / knowledges about that topic?