- This topic has 33 replies, 11 voices, and was last updated 16 years, 9 months ago by
.
-
Posts
-
@Alzir wrote:
Is the first one the IP I gave you because although it looks like the servers/bams I’ve been going through, it doesn’t match my current IP?? If my connection wasn’t responding to WAN ping, it’s because I only saw the post at 3 or 4 this afternoon past, but I enabled it right away.
I was going to say that this is a strange test because many of us will be on dynamic IP address allocation not static – so every time you reboot your router you will get a random IP from your ISP. So multiplay may be pinging someones elses router.
many of us will be on dynamic IP address allocation not static
Can’t believe I didn’t think of that either 😳 Mine’s probably changed since resetting my router.
I’m guessing this will be old hat to most of you, but have any of you guys set up static IPs from your router and then done all the correct port forwarding to the application/game? It was a little time consuming but it’s not difficult and it sorted my CS:S and Steam problems out (but NZ internet is stoneage in comparison to the uk).
Also, getting your ISP to turn off ‘interleaving’ (which I think is some bullshi7 error checking that just adds latency) makes a massive difference. NZ Telecom pretty much tell you to f**k off when you ask but other ISP’s will gladly turn it off and it instantly took 40 – 60ms off my TF2 ping. Decent routers can report if it’s set to on or off for your connection if you want to check. Off FTW!
step by step here —-> http://www.portforward.com
Like you say though, I doubt the server issues are all ISP ones.
- You must be logged in to reply to this topic.