-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
i need tweaks for a 56k modem for gaming
- Thread starter AMD900
- Start date
- Joined
- Feb 1, 2003
- Location
- Shreveport, La
I like what AMD900 said.
- Joined
- Jan 8, 2003
Some people 'like me' are just stuck on dialsuck because of the rural places we live. You broadband users really like to hammer down on just how much you think everyone in the world has broadband access. You guys like to make us feel like were just cheap and don't want to pay the extra costs for broadband. I would pay $200/month for a 512k line in this small town if it were available. I can use dialup or I can buy a T1 for $1300/month. So lighten up on the dude a little. If your lucky enough to live where fast internet is offered, be grateful.
As for tweaking your modem, the best thing you can do is the following...... buy an external model, then run some traceroutes. See what ping your getting to your gateway server. Which is the very first server your connected to, it belongs to your ISP. If your latency is real good to that first HOP, then keep going, find out where your bottleneck is. I get 100ms ping to my gateway and 200-250 to gaming servers. Chances are you will find, either your ISP sucks, your modem sucks, or your phoneline sucks. Replacing all 3 might be your solution. No tweaks in the world will ever bring your latency down enough to worry about.
As for tweaking your modem, the best thing you can do is the following...... buy an external model, then run some traceroutes. See what ping your getting to your gateway server. Which is the very first server your connected to, it belongs to your ISP. If your latency is real good to that first HOP, then keep going, find out where your bottleneck is. I get 100ms ping to my gateway and 200-250 to gaming servers. Chances are you will find, either your ISP sucks, your modem sucks, or your phoneline sucks. Replacing all 3 might be your solution. No tweaks in the world will ever bring your latency down enough to worry about.
- Joined
- Jan 8, 2003
You do all of that by opeing a dos prompt. And typing commands. Start with a traceroute to google.com. Type this:
tracert www.google.com
and let it finish, the very first machine you ping is the gateway, her is an example taken from me.
C:\Documents and Settings\Nick>tracert www.google.com
Tracing route to www.google.com [216.239.57.99]
over a maximum of 30 hops:
1 154 ms 132 ms 129 ms ip-66-45-192-2.nw-tel.com [66.45.192.2]
2 127 ms 130 ms 131 ms ip-66-45-192-1.nw-tel.com [66.45.192.1]
3 132 ms 129 ms 132 ms fe-2-0-1-term-bh-wen.nw-tel.com [66.45.205.193]
4 155 ms 134 ms 135 ms border25s.fe5-3.nwtel-1.sea.pnap.net [206.191.14
4.65]
5 136 ms 149 ms 134 ms core3.ge3-0-bbnet2.sea.pnap.net [206.253.192.195
]
6 144 ms 138 ms 145 ms 208.172.81.133
7 164 ms 149 ms 158 ms dcr1-loopback.SantaClara.cw.net [208.172.146.99]
8 158 ms 187 ms 155 ms ibr01-p5-0.sntc05.exodus.net [208.172.156.74]
9 150 ms 181 ms 156 ms csr21-ve243.SantaClarasc4.cw.net [216.34.3.11]
10 150 ms 164 ms 160 ms google-exodus.exodus.net [64.41.147.62]
11 * 177 ms * 216.239.49.2
12 196 ms 173 ms 166 ms 216.239.57.99
Trace complete.
Notice this ? ... 1 154 ms 132 ms 129 ms ip-66-45-192-2.nw-tel.com
This is MY gateway server, the first server on the list on it's way to google.com. Take this server's IP address and ping it a few times by typing this:
ping 1.2.3.4 where 1.2.3.4 is place the IP of your gateway server. if your pings are 100-150ms then your ISP isn't the problem, start looking through the trace route you did earlier, find out at what point your ping becomes to high. Do some traceroutes to different places to get a real idea of where the problem is.
If you get confused, do a traceroute to google.com and paste the results here, you can copy things in a dos prompt by right clicking in it and choosing MARK then highlight everything you want to copy, and right click again, it's now in your clipboard.
tracert www.google.com
and let it finish, the very first machine you ping is the gateway, her is an example taken from me.
C:\Documents and Settings\Nick>tracert www.google.com
Tracing route to www.google.com [216.239.57.99]
over a maximum of 30 hops:
1 154 ms 132 ms 129 ms ip-66-45-192-2.nw-tel.com [66.45.192.2]
2 127 ms 130 ms 131 ms ip-66-45-192-1.nw-tel.com [66.45.192.1]
3 132 ms 129 ms 132 ms fe-2-0-1-term-bh-wen.nw-tel.com [66.45.205.193]
4 155 ms 134 ms 135 ms border25s.fe5-3.nwtel-1.sea.pnap.net [206.191.14
4.65]
5 136 ms 149 ms 134 ms core3.ge3-0-bbnet2.sea.pnap.net [206.253.192.195
]
6 144 ms 138 ms 145 ms 208.172.81.133
7 164 ms 149 ms 158 ms dcr1-loopback.SantaClara.cw.net [208.172.146.99]
8 158 ms 187 ms 155 ms ibr01-p5-0.sntc05.exodus.net [208.172.156.74]
9 150 ms 181 ms 156 ms csr21-ve243.SantaClarasc4.cw.net [216.34.3.11]
10 150 ms 164 ms 160 ms google-exodus.exodus.net [64.41.147.62]
11 * 177 ms * 216.239.49.2
12 196 ms 173 ms 166 ms 216.239.57.99
Trace complete.
Notice this ? ... 1 154 ms 132 ms 129 ms ip-66-45-192-2.nw-tel.com
This is MY gateway server, the first server on the list on it's way to google.com. Take this server's IP address and ping it a few times by typing this:
ping 1.2.3.4 where 1.2.3.4 is place the IP of your gateway server. if your pings are 100-150ms then your ISP isn't the problem, start looking through the trace route you did earlier, find out at what point your ping becomes to high. Do some traceroutes to different places to get a real idea of where the problem is.
If you get confused, do a traceroute to google.com and paste the results here, you can copy things in a dos prompt by right clicking in it and choosing MARK then highlight everything you want to copy, and right click again, it's now in your clipboard.
- Joined
- Mar 1, 2002
- Location
- Texas
I hereby declare Wiz4rd, "the man".
- Joined
- Jan 8, 2003
I don't think I'm the man, but when it comes to internet connectivity I have quite a bit of knowledge. Most of the folks I know where I live have to deal with dialup, and after me having a 50k connection with low dial-up pings, a lot of people kept asking me how I did it, when the most people get here is 28.8k with 500ms+ pings on the phonelines around here that I believe MOSES brought over on the ark.
I spent many hours troubleshooting my connection, from re-wiring my home phonelines to replacing lines outside my house, to changing modems, to changing ISP's. I learned all this stuff the hard way.
Unless the phoneline out on the poles real close to your house is the problem, I can just about work with anyone to get them a better connection.
Always start with a ping to your gateway server. It's the closest machine to you that you connect to. If you have high ping there, then WAMMO there is your problem. Talking with your isp, and or changing ISP's can fix this sometimes. But if the ping is high at the gateway, you know the problem is from that gateway to your modem. Then it's a matter of starting with the modem and working your way to the gateway server. If the problem is between the gateway server and 1 of the other hops, then a ISP change might fix everything, because different ISP's use different tier backbones usually and the latency issue might be because of overcrowded lines that supply your ISP their bandwidth.
Anyways dude, run those traceroutes and pings, if you get stumped, ask in here, and or paste what results you get. We may not be able to solve the problem, but we sure will be able to tell you where the problem is.
I spent many hours troubleshooting my connection, from re-wiring my home phonelines to replacing lines outside my house, to changing modems, to changing ISP's. I learned all this stuff the hard way.
Unless the phoneline out on the poles real close to your house is the problem, I can just about work with anyone to get them a better connection.
Always start with a ping to your gateway server. It's the closest machine to you that you connect to. If you have high ping there, then WAMMO there is your problem. Talking with your isp, and or changing ISP's can fix this sometimes. But if the ping is high at the gateway, you know the problem is from that gateway to your modem. Then it's a matter of starting with the modem and working your way to the gateway server. If the problem is between the gateway server and 1 of the other hops, then a ISP change might fix everything, because different ISP's use different tier backbones usually and the latency issue might be because of overcrowded lines that supply your ISP their bandwidth.
Anyways dude, run those traceroutes and pings, if you get stumped, ask in here, and or paste what results you get. We may not be able to solve the problem, but we sure will be able to tell you where the problem is.
- Joined
- Sep 30, 2002
- Location
- Karachi, Pakistan
here is mine (tracert and ping to gateway)
Trace Route to Google Result
Ping result for gateway
how do you diagnose this?
i think so my problem starts here
i tried pinging No 1 - No 5 all gave results under 170 but No 6 gave me ping replies of 300+ grrr !!!
Trace Route to Google Result
Ping result for gateway
how do you diagnose this?
i think so my problem starts here
i tried pinging No 1 - No 5 all gave results under 170 but No 6 gave me ping replies of 300+ grrr !!!
- Joined
- Jan 8, 2003
baqai: What I would do now, is run some traceroutes to some other places, try other countries as well. What you need to determine is if "202.125.128.6 and 203.208.147.85"
is a backbone your ISP uses and you need to see if your connection always goes through there. This is the point where your ping starts to spike up. If so, then you need to contact some other isp's in your area, and see if their connections run through that host or not.
Find one that doesn't, and try their service for a month.
Your actually lucky, because when it comes down to it, the farther away the 'problem' is from your modem, the more options you have to fix it. According to that tracert you posted, you have a good clean line between you and the gateway server, which is great.
But you really need to make sure that is really the place that is causing the lag. Only way to do that is to run traceroutes to some more places and see. Once you are sure that is your dead spot, contact your ISP and ask how they are connected to those 2 IP addresses and let them know of the lag. I would also then call some other ISP's and ask if their connections run through or around those IP's.
I would also like to note, your ping to your gateway is a little bit laggy but not to bad. I usually get 120ms to mine, but that depends how far you are from your isp. I said you have a good clean line to the gateway because your ping to it is within reason, given the fact I don't know how far you are from the machine you dial into. I'm about 2 miles from mine which is very good. Remember the closer you are to the machine your dialing into the lower your ping will be to. And the better chance you will have of getting a higher connection handshake.
Let me know how it goes.
is a backbone your ISP uses and you need to see if your connection always goes through there. This is the point where your ping starts to spike up. If so, then you need to contact some other isp's in your area, and see if their connections run through that host or not.
Find one that doesn't, and try their service for a month.
Your actually lucky, because when it comes down to it, the farther away the 'problem' is from your modem, the more options you have to fix it. According to that tracert you posted, you have a good clean line between you and the gateway server, which is great.
But you really need to make sure that is really the place that is causing the lag. Only way to do that is to run traceroutes to some more places and see. Once you are sure that is your dead spot, contact your ISP and ask how they are connected to those 2 IP addresses and let them know of the lag. I would also then call some other ISP's and ask if their connections run through or around those IP's.
I would also like to note, your ping to your gateway is a little bit laggy but not to bad. I usually get 120ms to mine, but that depends how far you are from your isp. I said you have a good clean line to the gateway because your ping to it is within reason, given the fact I don't know how far you are from the machine you dial into. I'm about 2 miles from mine which is very good. Remember the closer you are to the machine your dialing into the lower your ping will be to. And the better chance you will have of getting a higher connection handshake.
Let me know how it goes.
Last edited:
- Joined
- Sep 30, 2002
- Location
- Karachi, Pakistan
i ran some more test here are results
trace route result for www.go4b.net
trace route result for www.deltagaming.net
Trace Route to www.overclockers.com
so i think so the problem is 203.208.147.85 it is accessed in most of the cases and everytime the very same ip starts giving higher pings
Pinging the ip confirmed that
Now should i call my ISP and ask them what is this ip or what???
trace route result for www.go4b.net
trace route result for www.deltagaming.net
Trace Route to www.overclockers.com
so i think so the problem is 203.208.147.85 it is accessed in most of the cases and everytime the very same ip starts giving higher pings
Pinging the ip confirmed that
Now should i call my ISP and ask them what is this ip or what???
- Thread Starter
- #13
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>tracert www.google.com
Tracing route to www.google.com [216.239.57.99]
over a maximum of 30 hops:
1 167 ms 154 ms 164 ms nas3.fayetteville1.nc.us.da.qwest.net [63.152.9.
88]
2 241 ms 154 ms 141 ms 63.152.24.110
3 351 ms 166 ms 165 ms atl-edge-05.inet.qwest.net [63.152.126.73]
4 278 ms 177 ms 166 ms tpa-core-01.inet.qwest.net [205.171.27.109]
5 280 ms 165 ms 165 ms atl-brdr-03.inet.qwest.net [205.171.21.102]
6 194 ms 166 ms 177 ms atl-core-02.inet.qwest.net [205.171.21.150]
7 266 ms 177 ms 177 ms agr3-loopback.Atlanta.cw.net [208.172.66.103]
8 253 ms 182 ms 185 ms acr1-so-2-0-0.Atlanta.cw.net [208.172.67.201]
9 309 ms 225 ms 271 ms dcr1-loopback.SantaClara.cw.net [208.172.146.99]
10 231 ms 177 ms 177 ms dcr1-so-0-2-0.Atlanta.cw.net [208.172.75.9]
11 241 ms 237 ms 236 ms csr21-ve243.SantaClarasc4.cw.net [216.34.3.11]
12 230 ms 225 ms 260 ms ibr01-p5-0.sntc05.exodus.net [208.172.156.74]
13 229 ms 237 ms 236 ms csr21-ve243.SantaClarasc4.cw.net [216.34.3.11]
14 242 ms 237 ms 236 ms google-exodus.exodus.net [64.41.147.62]
15 242 ms 236 ms 260 ms 216.239.49.2
16 242 ms 238 ms 236 ms 216.239.57.99
Trace complete.
C:\Documents and Settings\Administrator>
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>tracert www.google.com
Tracing route to www.google.com [216.239.57.99]
over a maximum of 30 hops:
1 167 ms 154 ms 164 ms nas3.fayetteville1.nc.us.da.qwest.net [63.152.9.
88]
2 241 ms 154 ms 141 ms 63.152.24.110
3 351 ms 166 ms 165 ms atl-edge-05.inet.qwest.net [63.152.126.73]
4 278 ms 177 ms 166 ms tpa-core-01.inet.qwest.net [205.171.27.109]
5 280 ms 165 ms 165 ms atl-brdr-03.inet.qwest.net [205.171.21.102]
6 194 ms 166 ms 177 ms atl-core-02.inet.qwest.net [205.171.21.150]
7 266 ms 177 ms 177 ms agr3-loopback.Atlanta.cw.net [208.172.66.103]
8 253 ms 182 ms 185 ms acr1-so-2-0-0.Atlanta.cw.net [208.172.67.201]
9 309 ms 225 ms 271 ms dcr1-loopback.SantaClara.cw.net [208.172.146.99]
10 231 ms 177 ms 177 ms dcr1-so-0-2-0.Atlanta.cw.net [208.172.75.9]
11 241 ms 237 ms 236 ms csr21-ve243.SantaClarasc4.cw.net [216.34.3.11]
12 230 ms 225 ms 260 ms ibr01-p5-0.sntc05.exodus.net [208.172.156.74]
13 229 ms 237 ms 236 ms csr21-ve243.SantaClarasc4.cw.net [216.34.3.11]
14 242 ms 237 ms 236 ms google-exodus.exodus.net [64.41.147.62]
15 242 ms 236 ms 260 ms 216.239.49.2
16 242 ms 238 ms 236 ms 216.239.57.99
Trace complete.
C:\Documents and Settings\Administrator>
- Thread Starter
- #14
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=192ms TTL=255
Reply from 63.152.9.88: bytes=32 time=187ms TTL=255
Reply from 63.152.9.88: bytes=32 time=170ms TTL=255
Reply from 63.152.9.88: bytes=32 time=178ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 192ms, Average = 181ms
C:\Documents and Settings\Administrator>ping 63.152.
Ping request could not find host 63.152.. Please check the name and try again.
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=255ms TTL=255
Reply from 63.152.9.88: bytes=32 time=155ms TTL=255
Reply from 63.152.9.88: bytes=32 time=163ms TTL=255
Reply from 63.152.9.88: bytes=32 time=229ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 255ms, Average = 200ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=235ms TTL=255
Reply from 63.152.9.88: bytes=32 time=159ms TTL=255
Reply from 63.152.9.88: bytes=32 time=153ms TTL=255
Reply from 63.152.9.88: bytes=32 time=255ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 255ms, Average = 200ms
C:\Documents and Settings\Administrator>63.152.9.88
'63.152.9.88' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=167ms TTL=255
Reply from 63.152.9.88: bytes=32 time=153ms TTL=255
Reply from 63.152.9.88: bytes=32 time=165ms TTL=255
Reply from 63.152.9.88: bytes=32 time=164ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 167ms, Average = 162ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=140ms TTL=255
Reply from 63.152.9.88: bytes=32 time=152ms TTL=255
Reply from 63.152.9.88: bytes=32 time=151ms TTL=255
Reply from 63.152.9.88: bytes=32 time=149ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 152ms, Average = 148ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=268ms TTL=255
Reply from 63.152.9.88: bytes=32 time=161ms TTL=255
Reply from 63.152.9.88: bytes=32 time=160ms TTL=255
Reply from 63.152.9.88: bytes=32 time=145ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 268ms, Average = 183ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=178ms TTL=255
Reply from 63.152.9.88: bytes=32 time=151ms TTL=255
Reply from 63.152.9.88: bytes=32 time=163ms TTL=255
Reply from 63.152.9.88: bytes=32 time=162ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 178ms, Average = 163ms
C:\Documents and Settings\Administrator>
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=192ms TTL=255
Reply from 63.152.9.88: bytes=32 time=187ms TTL=255
Reply from 63.152.9.88: bytes=32 time=170ms TTL=255
Reply from 63.152.9.88: bytes=32 time=178ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 192ms, Average = 181ms
C:\Documents and Settings\Administrator>ping 63.152.
Ping request could not find host 63.152.. Please check the name and try again.
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=255ms TTL=255
Reply from 63.152.9.88: bytes=32 time=155ms TTL=255
Reply from 63.152.9.88: bytes=32 time=163ms TTL=255
Reply from 63.152.9.88: bytes=32 time=229ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 255ms, Average = 200ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=235ms TTL=255
Reply from 63.152.9.88: bytes=32 time=159ms TTL=255
Reply from 63.152.9.88: bytes=32 time=153ms TTL=255
Reply from 63.152.9.88: bytes=32 time=255ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 255ms, Average = 200ms
C:\Documents and Settings\Administrator>63.152.9.88
'63.152.9.88' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=167ms TTL=255
Reply from 63.152.9.88: bytes=32 time=153ms TTL=255
Reply from 63.152.9.88: bytes=32 time=165ms TTL=255
Reply from 63.152.9.88: bytes=32 time=164ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 167ms, Average = 162ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=140ms TTL=255
Reply from 63.152.9.88: bytes=32 time=152ms TTL=255
Reply from 63.152.9.88: bytes=32 time=151ms TTL=255
Reply from 63.152.9.88: bytes=32 time=149ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 152ms, Average = 148ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=268ms TTL=255
Reply from 63.152.9.88: bytes=32 time=161ms TTL=255
Reply from 63.152.9.88: bytes=32 time=160ms TTL=255
Reply from 63.152.9.88: bytes=32 time=145ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 268ms, Average = 183ms
C:\Documents and Settings\Administrator>ping 63.152.9.88
Pinging 63.152.9.88 with 32 bytes of data:
Reply from 63.152.9.88: bytes=32 time=178ms TTL=255
Reply from 63.152.9.88: bytes=32 time=151ms TTL=255
Reply from 63.152.9.88: bytes=32 time=163ms TTL=255
Reply from 63.152.9.88: bytes=32 time=162ms TTL=255
Ping statistics for 63.152.9.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 178ms, Average = 163ms
C:\Documents and Settings\Administrator>
- Joined
- Jan 8, 2003
baqai: Yep your problem is around 5 and 6 where I said I thought it was last time. Contact your ISP and find out what those IP addresses are and then try to find an ISP that doesn't use those.
AMD900: Your pings actually look quite good. I can't see a bottleneck in those, it might simply be the particular game server your trying to use. Try using one in your own country and see if your pings are better.
AMD900: Your pings actually look quite good. I can't see a bottleneck in those, it might simply be the particular game server your trying to use. Try using one in your own country and see if your pings are better.
- Joined
- Sep 30, 2002
- Location
- Karachi, Pakistan
i tried playng on a local CS server and i was getting around 200-300 pings but when i try to play on some international server (oc.com's server for instance) i get around 400-500 ping 
i called my ISP and i was greeted by a typical customer support person who had NO idea of what i was talking about .. to make the story short i was "advised" to get my phone line checked grrr!!! and yeah "she" had no idea of trace route and gateways and to be honest seems to me she had idea of NOTHING !! argh!
i am going to pay a visit to my ISP .. i have already ordered cable connection and it's going to take around 10 days for installation and i have nothing to kill time so no harm is bashing the ISP
i called my ISP and i was greeted by a typical customer support person who had NO idea of what i was talking about .. to make the story short i was "advised" to get my phone line checked grrr!!! and yeah "she" had no idea of trace route and gateways and to be honest seems to me she had idea of NOTHING !! argh!
i am going to pay a visit to my ISP .. i have already ordered cable connection and it's going to take around 10 days for installation and i have nothing to kill time so no harm is bashing the ISP
- Joined
- Jan 8, 2003
I find it hard to believe all of this information is new. if it is I guess maybe I stumbled onto something. As for your ISP giving you the run around, I should of warned you about that. The ISP's here in my valley are small, when you call them you usually get to talk to the network administrator and he/she will tell you everything.
The traceroute command is good when you need to find out where your connection goes to reach a particular server, and if there are any problems along that route.
200-300ms ping on a gaming server is descent, I wouldn't expect much better unless the gaming server is hosted by your next door neighbor.
The traceroute command is good when you need to find out where your connection goes to reach a particular server, and if there are any problems along that route.
200-300ms ping on a gaming server is descent, I wouldn't expect much better unless the gaming server is hosted by your next door neighbor.
Similar threads
