Router installation
-
- A regular
- Posts: 58
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Fri Mar 05, 2004 1:30 pm
-
- Staff
- Posts: 42
- Joined: Sun Mar 07, 2004 12:49 am
- Location: Corona, CA
- Contact:
i really have no choice other than speakeasy and the price for what you get is not costeffective so i am calling Cox Cable every day till it is fixed but in the mean time... I remember edge saying he was routing around vario and i am still routed through them is this going to change at all?
BTW check this out--i am timing out like crazy today
BTW check this out--i am timing out like crazy today
-
- New to forums
- Posts: 7
- Joined: Sun Sep 21, 2003 8:41 am
Hussie and I are roommates. Looks like part of the issue was I we had an SMC 7004VWBR router which, through trial and error, cannot handle the load needed to run to gaming comps. Stay away from that router if you are running a home network for gaming.
Now, regarding COX. They suck. We had them visit us a few times, had their engineers call us directly, talked to 2 managers/supervisors and the outcome was all the same.
You ping fine to various websites so the issue is not loss. Your tracert is fine (they looked at the one above) and it is not unusual to see a couple of timeouts in the path??
I think it is a maintenance issue with them, and they don't want to spend the money or time to fix it. We put in a new router and now we can play without lagging out or getting disconnected, but the ping for CS is awful in regards to our server. WE both have 100s, but like you said, I think the packet loss is factoring into that more than the fact that we are going through the verio network.
Anyhow, gaming is possible now, just at a crappy ping for our clans server.
Thanks for the tips and advice.
Peace,
[SU]BigDaddy
Now, regarding COX. They suck. We had them visit us a few times, had their engineers call us directly, talked to 2 managers/supervisors and the outcome was all the same.
You ping fine to various websites so the issue is not loss. Your tracert is fine (they looked at the one above) and it is not unusual to see a couple of timeouts in the path??
I think it is a maintenance issue with them, and they don't want to spend the money or time to fix it. We put in a new router and now we can play without lagging out or getting disconnected, but the ping for CS is awful in regards to our server. WE both have 100s, but like you said, I think the packet loss is factoring into that more than the fact that we are going through the verio network.
Anyhow, gaming is possible now, just at a crappy ping for our clans server.
Thanks for the tips and advice.
Peace,
[SU]BigDaddy
ok i had a buch of our seattle guys play on servers in LA and they had the same ping issues and they did tracerts the problems seemed to be in att route can you guys route around that too or just verio?
we are trying to get the best for everyone and right now the seattle one is suckin is this just us or are others experiencing problems too?
we are trying to get the best for everyone and right now the seattle one is suckin is this just us or are others experiencing problems too?
-
- Staff
- Posts: 42
- Joined: Sun Mar 07, 2004 12:49 am
- Location: Corona, CA
- Contact:
If a hop entirely times out (three *'s in the trace for that hop), then it's most likely the case that the router is configured to not respond to that type of query. If this applies to them, then you're right that there is nothing to worry about. My trace to InterNAP LA looks like this and I do perfectly fine:
But if there are other issues than that, we need to look into them.
Code: Select all
C:\WINDOWS>tr www
NFO win32 trace tool v1.01, copyright (c)2004 Nuclearfallout Enterprises, Inc.
Tracing route to www [66.150.188.20]
with up to 30 hops:
1 * * * Request timed out.
2 9.4 ms 8.0 ms 9.1 ms 12.244.20.241
3 9.5 ms 8.9 ms 9.6 ms 12.244.0.13
4 23.9 ms 24.0 ms 9.7 ms 12.244.72.18
5 10.1 ms 11.2 ms 10.7 ms tbr1-p012402.st6wa.ip.att.net [12.122.5.174]
6 25.3 ms 28.1 ms 24.1 ms tbr2-cl1.sffca.ip.att.net [12.122.12.113]
7 33.9 ms 33.3 ms 33.6 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
8 33.2 ms 33.1 ms 33.6 ms gar1-p341.lsnca.ip.att.net [12.123.199.177]
9 * * * Request timed out.
10 33.9 ms 33.4 ms 34.1 ms border1.ge3-1-bbnet1.ext1.lax.pnap.net [216.52.255.22]
11 36.2 ms 36.1 ms 36.8 ms nuclearfallout-11.border1.ext1.lax.pnap.net [216.52.220.210]
12 34.6 ms 35.6 ms 34.3 ms www.nuclearfallout.net [66.150.188.20]
Trace complete.
C:\WINDOWS>
here is Lameducks tracert from seattle to LA
He knows the first one is his problem but that 9th one is not and that seems to be where his trouble is comming from.
Code: Select all
Tracing route to outlawnation.nuclearfallout.net [64.94.100.53]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 8 ms 9 ms 12.244.20.161
3 15 ms 11 ms 21 ms 12.244.0.21
4 12 ms 11 ms 11 ms 12.118.106.5
5 17 ms 11 ms 12 ms tbr1-p012402.st6wa.ip.att.net [12.122.5.174]
6 31 ms 33 ms 29 ms tbr2-cl1.sffca.ip.att.net [12.122.12.113]
7 37 ms 35 ms 37 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
8 37 ms 35 ms 39 ms gar1-p340.lsnca.ip.att.net [12.123.199.225]
9 * * * Request timed out.
10 35 ms 39 ms 37 ms border1.ge3-1-bbnet1.ext1.lax.pnap.net [216.52.255.22]
11 42 ms 44 ms 38 ms nuclearfallout-11.border1.ext1.lax.pnap.net [216.52.220.210]
12 37 ms 37 ms 44 ms client.la.losangeles.nuclearfallout.net [64.94.100.53]
Trace complete.