Router not allowing more than one client on the same network connect to any given Source server at t
1 replies, posted
I feel like it's our end at least, since this didn't happen until we bought this new router because our old one kept booting everyone off every 10 minutes.
This problem is odd to explain, but I'll try my best.
Say there's two Garry's Mod servers on the same box, but different ports.
I connect to one, but no one else on the same network as me can connect to it anymore, and still can't connect to it for quite a while until I disconnect. The server is pingable, responds in the server browser, but otherwise won't connect.
BUT. The other person trying to connect can still connect to the second server on the different port just fine, no problems. But now the first person can't connect to THAT server.
We can't find any settings in the router's stuff that would relate to this, and it's a royal pain in the ass.
Router: [url=http://www.netgear.com/home/products/networking/wifi-routers/R7500.aspx]Netgear Nighthawk X4 R7500[/url]
[editline]24th November 2015[/editline]
Never mind, opened every single port that all Source games use manually and that fixed it. :|
Have never had to do this before, ever. What the fuck.
[highlight]Solved.[/highlight]
SOLVED THE PROBLEM FOR GOOD!
As it turns out, if you use Steam's "join game" function rather than using the server browser, it tries to connect on the same port as the client you're joining.
In my case, it was trying to join using the same client port as whatever client was connected to the server at the time, since people in the house just connect from my server info box rather than the server browser, it was just causing the connection to be rejected.
That was a dumb ride.
[highlight]Solved for real.[/highlight]
Sorry, you need to Log In to post a reply to this thread.