flyfisho
Registered
It sounds as it is in the tilte and it has taken me down some very distant pathways to work this out to why.
I had a dedicated server working from a pc at home.
The internet was TPG FTTN at 20 up and 40 down mbps. The dedi was working fine as i use a provider to assign a DDNS as i dont have a static IP.
I upgraded to FTTB and now get approx 50 up and 770 down mbps.
As soon as i upgraded the dedi stopped showing up in match maker. i managed to get it to show up but when i connect it times out 5 tries.
I have tried moving the ports around to get it to connect but it always fails as it does not return on the x+1 HTTP port.
So i have simulation port 55100 and HTTP server port 48010
TCP 48010
UDP 48011
UDP 48012
UDP 55100
So the issue is i can never get the port after 48010 (x+1 is 48011) to show up on the system and get recognized so RF2 dedi will show up in game but fails to connect.
Runing on CMD to test it with the dedi running comes up as:
C:\Users\Administrator>netstat -ano | findstr 480
TCP 0.0.0.0:48010 0.0.0.0:0 LISTENING 4660
UDP 0.0.0.0:48012 *:* 4660
There is no 48011 for rf2 dedi to connect properly.
I have had it running fine on win 11 with the previous internet connection and have even tried windows server 2022 to dive deeper into why the x+1 port never shows up and breaks the connection.
No matter what range of ports i set it never broadcasts with the x+1 port.
So if you set the HTTP port rf2 will always go to the next two ports after it to connect properly.
This only happened after using super fast internet.
I am at a loss and can only try linux to run a dedi on fast internet.
I had a dedicated server working from a pc at home.
The internet was TPG FTTN at 20 up and 40 down mbps. The dedi was working fine as i use a provider to assign a DDNS as i dont have a static IP.
I upgraded to FTTB and now get approx 50 up and 770 down mbps.
As soon as i upgraded the dedi stopped showing up in match maker. i managed to get it to show up but when i connect it times out 5 tries.
I have tried moving the ports around to get it to connect but it always fails as it does not return on the x+1 HTTP port.
So i have simulation port 55100 and HTTP server port 48010
TCP 48010
UDP 48011
UDP 48012
UDP 55100
So the issue is i can never get the port after 48010 (x+1 is 48011) to show up on the system and get recognized so RF2 dedi will show up in game but fails to connect.
Runing on CMD to test it with the dedi running comes up as:
C:\Users\Administrator>netstat -ano | findstr 480
TCP 0.0.0.0:48010 0.0.0.0:0 LISTENING 4660
UDP 0.0.0.0:48012 *:* 4660
There is no 48011 for rf2 dedi to connect properly.
I have had it running fine on win 11 with the previous internet connection and have even tried windows server 2022 to dive deeper into why the x+1 port never shows up and breaks the connection.
No matter what range of ports i set it never broadcasts with the x+1 port.
So if you set the HTTP port rf2 will always go to the next two ports after it to connect properly.
This only happened after using super fast internet.
I am at a loss and can only try linux to run a dedi on fast internet.