Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - boxes

Pages: [1]
1
Doubleposting for the sake of solving my own problem:

 I have a Netgear router and it wasn't playing nice with Quake 2, in most servers. The solution was to enable QoS, get rid of all the default rules, and make Quake 2 the highest priority on the router. Was able to play railz for an hour with zero disconnects, whereas previously it would take about 10-12 minutes (about a match and a half) to get disconnected. I'm going to post this in the OP as well for any future people who have this same problem.

2
i might have worded that incorrectly and maybe you misunderstood. i didn't mean "both" at the exact same time, just that we both run into those conditions from which we get disconnected. (after for playing for a match or so we get DCed)

snip
ah i am the misunderstandee(er?)

im going to do a hard reset on my router and see if it plays nice on a default configuration.

3
snip

snip
snip

i might have worded that incorrectly and maybe you misunderstood. i didn't mean "both" at the exact same time, just that we both run into those conditions from which we get disconnected. (after for playing for a match or so we get DCed)

edit: fiddled with my nat being open and closed with no results, also forwarded the port i saw in the logs to my sub ip to see if it would help- nada.

4
 hello tastyfriends,

  i recently got my dad back into playing quake 2 as per request, i set him up with his old config, got him a functional modern client, and showed him the server list. everything works fine, except after generally no matter what happens, after about a match and a half we'll /both/ get forcibly disconnected. i thought it might have been something with our configs, or something in the router- but i've extensively exhausted all possibilities and came here to explore if it was a common occurrence. i figured if we both get DCed in around the same time frame on different computers, configs, and even OSes that our IP must be getting blocked/was banned for some reason or another.

the names we go by are 'boxes' (me) and 'springgreens'. i've tested this on rails,dm,wodx you name it, all the same thing. any way anyone can check this out for me?

SOLUTION:
Quote
  I have a Netgear router and it wasn't playing nice with Quake 2, in most servers. The solution was to enable QoS, get rid of all the default rules, and make Quake 2 the highest priority on the router. Was able to play railz for an hour with zero disconnects, whereas previously it would take about 10-12 minutes (about a match and a half) to get disconnected. I'm going to post this in the OP as well for any future people who have this same problem.

5
Trouble Shooting / Re: Kicked from game on connect?
« on: May 17, 2017, 11:16:42 AM »
-cut im a massive retard and just did massive necromancy on a stickied thread-

Pages: [1]