Problem Kicked for high ping from my owm Dedicated Server?

Discussion in 'Community Support' started by Sean Kenney, Mar 1, 2019.

  1. Sean Kenney

    Sean Kenney Well-Known Member

    Joined:
    Feb 9, 2015
    Ratings:
    +316 / 0 / -0
    I keep getting kicked from my r3e dedicated server. The server is a seperate machine, and in the same room as my main computer, with my router as the only division.

    -I have a 1gb up and down connection...aka fast.
    -fairly fast desktop i5K etc
    -I have tried having the server on two different machines and the same things happens. One of them is a fast machine amd Ryzen1600.

    I get kicked when someone joins or after about 30 seconds. It seems I get a couple of network spikes as it happens...which obviously is the high ping.

    Have the ports in my router.
    RaceRoom Racing server connection UDP: 60000
    RaceRoom Racing server game traffic TCP: 60001
    RaceRoom Racing server ping and time UDP: 60002

    Any ideas?
     
  2. NL-Jos

    NL-Jos Well-Known Member

    Joined:
    Jun 5, 2015
    Ratings:
    +182 / 0 / -0
    I've got different problems with the numbers 60000-60001-600002
    May try this
    Open a second server (wich get the the numbers 60003-60004-60005) and look if you get the same problems.
    You can close the first server, every next server get higher numbers as long you have one server open.
    Maybe this will be help you.
     
  3. rad

    rad Well-Known Member

    Joined:
    Jan 29, 2015
    Ratings:
    +458 / 0 / -0
    [​IMG]
     
    • Funny Funny x 2
  4. Sean Kenney

    Sean Kenney Well-Known Member

    Joined:
    Feb 9, 2015
    Ratings:
    +316 / 0 / -0
    That didn't work either
     
  5. NL-Jos

    NL-Jos Well-Known Member

    Joined:
    Jun 5, 2015
    Ratings:
    +182 / 0 / -0
    Than i can't help, sorry
     
    • Like Like x 1
  6. Sean Kenney

    Sean Kenney Well-Known Member

    Joined:
    Feb 9, 2015
    Ratings:
    +316 / 0 / -0
    2872 64.119646 192.168.1.xx(ME!) 52.33.134.128 TCP 55 [TCP Keep-Alive] 51724 → 443 [ACK] Seq=1179 Ack=6787 Win=65536 Len=1

    I get this in wireshark a lot when I get an erros....I don't know anything about it but I am guessing this is tyhe issue.... TCP to port 443 on my machine...or something like that lol
     
  7. G.Deurwaerder

    G.Deurwaerder Well-Known Member

    Joined:
    Jan 29, 2015
    Ratings:
    +115 / 0 / -0


    I had this problem too, one year ago, and then the problem turned out to lie with the provider, they block the number 60000 for a reason (private reason I think) look at the port where TCP is on, there is a possibility to this on both TCP or UDP
     
  8. Sean Kenney

    Sean Kenney Well-Known Member

    Joined:
    Feb 9, 2015
    Ratings:
    +316 / 0 / -0
  9. Esr Admin

    Esr Admin Well-Known Member

    Joined:
    Apr 27, 2017
    Ratings:
    +110 / 0 / -0
    We did some more testing with Sean.
    Raceroom dedicated is on Asus external router that is connected to the ISP router.
    Pc1 connected on asus router can join and gets kicked out after 30 second max.
    Pc2 connected on ISP router gets no response from server.
    Outside connection can join no issue and does not get kicked out.

    Even without the asus router added to the isp router, the same problem happened. It's pretty obvious that the isp router is causing the issue. Any idea on how to stop this from happening.
    Can we send the logs to anyone?

    Isp router is on At&T BGW210-700
    All firewall off and packet filtering off.