I Just got a cable modem from adelphia cable service and my pings are horrible. I questioned adelphia about this and they were not able to give me a clear answer. My downloading and streaming are just fine..Im rather impressed with how fast i cand ownload at but my pings to servers are just rediculous. I am hoping that there are soem settings in my tcp/ip stack I can change but im not sure were or how to do it..
Thanks
Josh
**specs**
500mhz
10/100 ehternet card
192 mgs ram
win98 se
Cable Ping Horrible
-
Lobo
- SG VIP
- Posts: 17660
- Joined: Thu Nov 23, 2000 2:32 pm
- Location: Panama City, FL and a FAN of Dale Earnhardt Jr. Bud Chevy & NASCAR , and the Atlanta Braves
Do you have speed patch installed, whose:
It has been verified by experiment that certain auto-negotiating ethernet cards (both in PCs and in Macs), when connected to certain models of cable modem, sense the ethernet duplex setting incorrectly. Such a cable modem has ethernet hardware which is capable of operating only in half-duplex mode, at 10 Mbps, yet some auto-negotiating ethernet cards sense it as full-duplex. If an auto-negotiation card incorrectly starts operating in full-duplex mode, there can be collisions between ethernet packets being transmitted in both directions at the same time, leading to packet loss, and repeated re-transmissions. There is no visible evidence of this apart from poor performance. This problem can be avoided by manually configuring your ethernet card to be 10 Mbps half-duplex. No ill-effects will transpire from doing this, even when it is not necessary. The exact wording of the setting changes required varies from one manufacturer to another, so the instructions below are necessarily rather broadly defined.
To make this change under Win98/ME, follow these steps:
Open Control Panel.
Double-click Network.
From the scrollable list, select your Ethernet adapter (rather than any dial-up) with a green icon.
Click the button Properties.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK all the way out - you might need to restart.
To make this change under Windows 2000 or XP, follow these steps:
Open Control Panel.
Double-click Network and Dial-up Connections.
Identify the icon for your cable modem connection: usually Local Area Connection.
Right-click that icon and select Properties.
Under the ethernet adapter icon, click the button Configure.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK to exit the Connection properties
It has been verified by experiment that certain auto-negotiating ethernet cards (both in PCs and in Macs), when connected to certain models of cable modem, sense the ethernet duplex setting incorrectly. Such a cable modem has ethernet hardware which is capable of operating only in half-duplex mode, at 10 Mbps, yet some auto-negotiating ethernet cards sense it as full-duplex. If an auto-negotiation card incorrectly starts operating in full-duplex mode, there can be collisions between ethernet packets being transmitted in both directions at the same time, leading to packet loss, and repeated re-transmissions. There is no visible evidence of this apart from poor performance. This problem can be avoided by manually configuring your ethernet card to be 10 Mbps half-duplex. No ill-effects will transpire from doing this, even when it is not necessary. The exact wording of the setting changes required varies from one manufacturer to another, so the instructions below are necessarily rather broadly defined.
To make this change under Win98/ME, follow these steps:
Open Control Panel.
Double-click Network.
From the scrollable list, select your Ethernet adapter (rather than any dial-up) with a green icon.
Click the button Properties.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK all the way out - you might need to restart.
To make this change under Windows 2000 or XP, follow these steps:
Open Control Panel.
Double-click Network and Dial-up Connections.
Identify the icon for your cable modem connection: usually Local Area Connection.
Right-click that icon and select Properties.
Under the ethernet adapter icon, click the button Configure.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK to exit the Connection properties
-
Xile
-
Xile
Here is a trace route to yahoo if you want me to trace route somewere else just ask. Umm Im not sure what you mean by whos speed tweak do i have installed...I got tcp/optimizer but that didnt seem to help...Im going to call me isp and ask them if they know that there pings aer horrable or if they can come out to my house and do a latency test to there server ( I live in a run down area of town) so the lines might be old. But if you have any ideas,im all ears.
Thanks
Josh
Tracing route to http://www.yahoo.akadns.net [216.115.102.75]
over a maximum of 30 hops:
1 8 ms 9 ms 7 ms 10.58.80.1
2 9 ms 7 ms 9 ms 24.48.217.197
3 64 ms 73 ms 64 ms 64.8.28.129
4 67 ms 74 ms 65 ms pos4-0.ftwttx-rdra-12012.network.adelphia.net [64.8.29.29]
5 105 ms 86 ms 72 ms 64.66.111.61
6 67 ms 66 ms 67 ms p3-00-02-00.r0.dfw00.adelphiacom.net [66.109.12.153]
7 67 ms 80 ms 72 ms p3-00-00-00.n0.dfw00.adelphiacom.net [66.109.0.161]
8 102 ms 103 ms 103 ms p3-00-03-00.n0.fll00.adelphiacom.net [66.109.0.49]
9 109 ms 110 ms 111 ms p3-01-01-00.n0.dca00.adelphiacom.net [66.109.0.9]
10 111 ms 118 ms 110 ms p3-00-00-00.r0.dca00.adelphiacom.net [66.109.0.142]
11 213 ms 280 ms 459 ms p3-00-00-00.p0.dca90.adelphiacom.net [66.109.6.150]
12 111 ms 122 ms 112 ms ibr01-g6-0.paxe01.exodus.net [198.32.190.10]
13 111 ms 115 ms 118 ms bbr01-p5-1.hrnd01.exodus.net [216.32.132.177]
14 113 ms 115 ms 114 ms bbr02-p3-0.stng02.exodus.net [209.185.9.6]
15 147 ms 147 ms 146 ms bbr01-p5-0.sntc05.exodus.net [209.185.9.113]
16 148 ms 147 ms 150 ms bbr01-p3-0.snva02.exodus.net [216.32.132.18]
17 151 ms 149 ms 151 ms dcr01-g9-1.snva02.exodus.net [64.15.160.19]
18 150 ms 146 ms 150 ms 64.15.161.130
19 148 ms 148 ms 156 ms http://www.yahoo.akadns.net [216.115.102.75]
Trace complete.
Thanks
Josh
Tracing route to http://www.yahoo.akadns.net [216.115.102.75]
over a maximum of 30 hops:
1 8 ms 9 ms 7 ms 10.58.80.1
2 9 ms 7 ms 9 ms 24.48.217.197
3 64 ms 73 ms 64 ms 64.8.28.129
4 67 ms 74 ms 65 ms pos4-0.ftwttx-rdra-12012.network.adelphia.net [64.8.29.29]
5 105 ms 86 ms 72 ms 64.66.111.61
6 67 ms 66 ms 67 ms p3-00-02-00.r0.dfw00.adelphiacom.net [66.109.12.153]
7 67 ms 80 ms 72 ms p3-00-00-00.n0.dfw00.adelphiacom.net [66.109.0.161]
8 102 ms 103 ms 103 ms p3-00-03-00.n0.fll00.adelphiacom.net [66.109.0.49]
9 109 ms 110 ms 111 ms p3-01-01-00.n0.dca00.adelphiacom.net [66.109.0.9]
10 111 ms 118 ms 110 ms p3-00-00-00.r0.dca00.adelphiacom.net [66.109.0.142]
11 213 ms 280 ms 459 ms p3-00-00-00.p0.dca90.adelphiacom.net [66.109.6.150]
12 111 ms 122 ms 112 ms ibr01-g6-0.paxe01.exodus.net [198.32.190.10]
13 111 ms 115 ms 118 ms bbr01-p5-1.hrnd01.exodus.net [216.32.132.177]
14 113 ms 115 ms 114 ms bbr02-p3-0.stng02.exodus.net [209.185.9.6]
15 147 ms 147 ms 146 ms bbr01-p5-0.sntc05.exodus.net [209.185.9.113]
16 148 ms 147 ms 150 ms bbr01-p3-0.snva02.exodus.net [216.32.132.18]
17 151 ms 149 ms 151 ms dcr01-g9-1.snva02.exodus.net [64.15.160.19]
18 150 ms 146 ms 150 ms 64.15.161.130
19 148 ms 148 ms 156 ms http://www.yahoo.akadns.net [216.115.102.75]
Trace complete.
-
Lobo
- SG VIP
- Posts: 17660
- Joined: Thu Nov 23, 2000 2:32 pm
- Location: Panama City, FL and a FAN of Dale Earnhardt Jr. Bud Chevy & NASCAR , and the Atlanta Braves
In Optimizer under ping, click on modify and enter your isp [url]http://WWW.comcast.net,[/url] (Example) do it twice, then start ping, at end RIGHT click, select copy, back here in reply box, cursor blinking at begining, RIGHT click and select paste
-
Xile
Correct me if im wrong but this adress (ca-susanville1b-110.ssvlca.adelphia.net [24.54.7.110] ) i think is my dhcp server
and also adelphia told me to go **** myself and that "they cant help me with that right now"
Does that help at all?
Thanks for your time
Josh
Pinging [24.54.7.110] with 32 bytes ->bytes=32 time=0ms TTL=64
Pinging [24.54.7.110] with 32 bytes ->bytes=32 time=0ms TTL=64
Pinging [24.54.7.110] with 32 bytes ->bytes=32 time=0ms TTL=64
Pinging [64.8.50.26] with 32 bytes ->bytes=32 time=138ms TTL=242
Pinging [64.8.50.26] with 32 bytes ->bytes=32 time=140ms TTL=242
Pinging [64.8.50.26] with 32 bytes ->bytes=32 time=140ms TTL=242
Ping statistics for above hosts:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 138ms, Maximum = 140ms, Average = 69ms
and also adelphia told me to go **** myself and that "they cant help me with that right now"
Does that help at all?
Thanks for your time
Josh
Pinging [24.54.7.110] with 32 bytes ->bytes=32 time=0ms TTL=64
Pinging [24.54.7.110] with 32 bytes ->bytes=32 time=0ms TTL=64
Pinging [24.54.7.110] with 32 bytes ->bytes=32 time=0ms TTL=64
Pinging [64.8.50.26] with 32 bytes ->bytes=32 time=138ms TTL=242
Pinging [64.8.50.26] with 32 bytes ->bytes=32 time=140ms TTL=242
Pinging [64.8.50.26] with 32 bytes ->bytes=32 time=140ms TTL=242
Ping statistics for above hosts:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 138ms, Maximum = 140ms, Average = 69ms