Broadband Tech > General Questions > Which ic better DSL or CAble connection?

Which ic better DSL or CAble connection?

Same name topic also had some views check it out click here
http ://www.dslreports.com/forum/remark,6639629~root=chat~mode=flat
--
http ://groups.msn.com/OfficialWindows98And98SecondEditionHelpSite

reply to yook
The link above will hopefully give you a general idea.

It all depends on your location and the types of service available to you.

What city and state are you in? Are there specific providers that you have looked into?

reply to yook
»I think DSL is better than Cable

One more

reply to Microsoft 98
You should investigate all options in your area before making a decision, your local cable or phone company may give you a discount for using all of their services.

reply to yook
If your cable choice is Charter...go with ANYTHING, including dial up, over Charter.
--
Charter Pipeline SUX. Nough said.

reply to yook
simple terms

DSL not shared with neighbor hood
Cable Shared with neighbor hood

Dsl steady ping (great for gamers)
Cable not steady (not good for gamers)
--
Advertize Speeds 768/128 I'm getting 731/136

reply to yook
Not this war again! It depends. End of discussion.
--
Satellite "BROADBAND" sucks. luwigie@dslr.net

reply to yook
No kidding.. I have cable and it works great with games. It just depends who your ISP is. Getting Cable was great for me because getting DSL would required me getting my lines repaired was one excuse and the other was not being close to the CO. Funny how the CO was no more then 5000 feet from where I lived.

Go with cable.

reply to NightLinks

said by NightLinks:

---

simple terms

DSL not shared with neighbor hood
Cable Shared with neighbor hood

Dsl steady ping (great for gamers)
Cable not steady (not good for gamers)

---

reply to yook
Another location that I go to sometimes has 3000/400 cable and the pings are consistant at 14 or so.
--
Satellite "BROADBAND" sucks. luwigie@dslr.net

reply to yook
Interesting:

quote:

---

DSL not shared with neighbor hood
Cable Shared with neighbor hood

Dsl steady ping (great for gamers)
Cable not steady (not good for gamers)

---

quote:

---

DSL not shared with neighbor hood - steady SLOW speed
Cable Shared with neighbor hood - unsteady but FAST speed

Dsl steady HIGH pings (very bad for gamers) - INTERLEAVING
Cable not steady but LOW pings (very good for gamers)

---

reply to yook
It all depends on what you have available in your area. many different companies uses different caps and have different prices.
--
Let's Roll
[text was edited by author 2003-05-03 14:10:40]

reply to whizkid3
I have something good here my friend has cable how come he pings from 9-40 in his own server?
--
Advertize Speeds 768/128 I'm getting 731/136

reply to yook
Nightlinks, can you explain - your statement is very unclear.

Do you mean he gets 9-40ms pinging his own server (which is on his own subnet before the cable modem)?

yeah he does that's weird he gets 9-40 ping out of this own server with cable
--
Advertize Speeds 768/128 I'm getting 731/136

reply to yook
If the ping isn't leaving his own network, then it has nothing to do with the cable, however...

its possible that the ping is leaving his network, going to the UBR-CMTS, and back. This would illustrate a problem with his configuration. Can you have him do a tracert, and post it here?

reply to whizkid3

said by whizkid3:

---

My experience is currently with Optimum Online cable & in the past, Verizon (and other) DSL - what I can report:

On OOL I average 8800kbps down / 850kbps up (smells a whole lot better than anyones DSL; ten times faster than most).

My first hop ping is consistently 9ms. (DSL providers inherently adjust 'interleaver depth' to achieve faster data rates - this typically results in first hop pings on DSL of 20 - 50 ms - ask gamers how much they enjoy their DSL.

[text was edited by author 2003-05-03 01:54:26]

---

reply to yook

pings - DSL vs. Cable

Also keep in mind with DSL phone line quality matters a lot in the first hop which is what causes some of the complaints. DSL is the way to go for stable throughput because it's not shared like cable is. so your cable is fine now, but if it gets oversold like comcast does, you will be hating it. Also as far as DSL Speed VS cable speed, anyone who has DSL at 1.5Mb down and 256Kb up, could get up to 8MB down and 1MB up, if the telcos wanted to do that with the current setups.

#1 192.168.0.1 (Unavailable): TTL Exceeded in Transit, ttl=255, 0.7 ms, 0.7/0.7/0.7 ms, Packets out 1, in 1, 0% loss
#2 67.33.163.1 (adsl-33-163-1.asm.bellsouth.net): TTL Exceeded in Transit, ttl=63, 13.4 ms, 13.4/13.4/13.4 ms, Packets out 1, in 1, 0% loss
#3 209.149.96.65 (Unavailable): TTL Exceeded in Transit, ttl=253, 13.3 ms, 13.3/13.3/13.3 ms, Packets out 1, in 1, 0% loss
#4 209.149.96.158 (Unavailable): TTL Exceeded in Transit, ttl=252, 13.9 ms, 13.9/13.9/13.9 ms, Packets out 1, in 1, 0% loss
#5 209.149.96.246 (Unavailable): TTL Exceeded in Transit, ttl=251, 14.2 ms, 14.2/14.2/14.2 ms, Packets out 1, in 1, 0% loss
#6 65.83.237.0 (axr00asm-1-3-0.bellsouth.net): TTL Exceeded in Transit, ttl=249, 13.9 ms, 13.9/13.9/13.9 ms, Packets out 1, in 1, 0% loss
#7 65.83.236.2 (pxr00asm-2-0-0.bellsouth.net): TTL Exceeded in Transit, ttl=248, 14.5 ms, 14.5/14.5/14.5 ms, Packets out 1, in 1, 0% loss
#8 157.130.71.169 (so-2-0-0.GW13.ATL5.ALTER.NET): TTL Exceeded in Transit, ttl=247, 14.0 ms, 14.0/14.0/14.0 ms, Packets out 1, in 1, 0% loss
#9 152.63.84.102 (0.so-0-1-0.XL2.ATL5.ALTER.NET): TTL Exceeded in Transit, ttl=246, 14.8 ms, 14.8/14.8/14.8 ms, Packets out 1, in 1, 0% loss
#10 152.63.10.106 (0.so-0-0-0.TL2.ATL5.ALTER.NET): TTL Exceeded in Transit, ttl=245, 15.1 ms, 15.1/15.1/15.1 ms, Packets out 1, in 1, 0% loss
#11 152.63.3.193 (0.so-6-0-0.TL2.DCA8.ALTER.NET): TTL Exceeded in Transit, ttl=244, 32.6 ms, 32.6/32.6/32.6 ms, Packets out 1, in 1, 0% loss
#12 152.63.144.30 (0.so-4-3-0.XL2.DCA8.ALTER.NET): TTL Exceeded in Transit, ttl=243, 34.2 ms, 34.2/34.2/34.2 ms, Packets out 1, in 1, 0% loss
#13 152.63.35.98 (188.at-2-0-0.CL2.IAD5.ALTER.NET): TTL Exceeded in Transit, ttl=242, 34.7 ms, 34.7/34.7/34.7 ms, Packets out 1, in 1, 0% loss
#14 152.63.38.141 (0.so-6-0-0.XR2.IAD8.ALTER.NET): TTL Exceeded in Transit, ttl=241, 34.8 ms, 34.8/34.8/34.8 ms, Packets out 1, in 1, 0% loss
#15 152.63.41.33 (POS7-0.GW4.IAD8.ALTER.NET): TTL Exceeded in Transit, ttl=241, 35.2 ms, 35.2/35.2/35.2 ms, Packets out 1, in 1, 0% loss
#16 157.130.30.246 (wcgGigE-gw2.customer.alter.net): TTL Exceeded in Transit, ttl=240, 32.3 ms, 32.3/32.3/32.3 ms, Packets out 1, in 1, 0% loss
#17 64.200.95.146 (washdc5lcx1-oc48.wcg.net): TTL Exceeded in Transit, ttl=231, 43.8 ms, 43.8/43.8/43.8 ms, Packets out 1, in 1, 0% loss
#18 64.200.240.193 (hrndva1wcx2-pos6-0.wcg.net): TTL Exceeded in Transit, ttl=232, 94.7 ms, 94.7/94.7/94.7 ms, Packets out 1, in 1, 0% loss
#19 64.200.210.98 (nycmny2wcx2-pos0-0.wcg.net): TTL Exceeded in Transit, ttl=233, 40.6 ms, 40.6/40.6/40.6 ms, Packets out 1, in 1, 0% loss
#20 64.200.87.226 (nycmny2wcx3-pos9-0.wcg.net): TTL Exceeded in Transit, ttl=234, 43.9 ms, 43.9/43.9/43.9 ms, Packets out 1, in 1, 0% loss
#21 64.200.87.110 (nycmnyhlce1-oc48.wcg.net): TTL Exceeded in Transit, ttl=235, 40.1 ms, 40.1/40.1/40.1 ms, Packets out 1, in 1, 0% loss
#22 64.200.86.150 (nycmny2lce1-netaccess-atm.wcg.net): TTL Exceeded in Transit, ttl=233, 40.1 ms, 40.1/40.1/40.1 ms, Packets out 1, in 1, 0% loss
#23 209.123.11.150 (1187.at-0-1-0.gbr1.oct.nac.net): TTL Exceeded in Transit, ttl=235, 41.5 ms, 41.5/41.5/41.5 ms, Packets out 1, in 1, 0% loss
#24 64.21.102.2 (0095.gi-1-1.msfc1.oct.nac.net): TTL Exceeded in Transit, ttl=235, 40.5 ms, 40.5/40.5/40.5 ms, Packets out 1, in 1, 0% loss
#25 209.123.109.175 (www.dslreports.com): Echo Reply, ttl=43, 43.3 ms, 43.3/43.3/43.3 ms, Packets out 1, in 1, 0% loss
Out 25, in 25, loss 0%, times (min/avg/max) 0.7/30.4/94.7
[text was edited by author 2003-05-04 23:06:28]