how-to block ads
|
xxwinmanxx
join:2009-02-19
Baton Rouge, LA
| reply to dhar
Re: [LA] Slow in Baton Rouge 70810
Well, back here again to post that the internet is unuseable. And lookie what we have, dhar is posting as well. I thought this problem was behind us as the download speeds and pings have been killer. I can not even watch a standard def video on you tube. I am to the point of wanting other services now. I am paying for the high end tier of service yet when I am home from work (5:30pm+) I may as well just have the el cheapo connection because thats the speeds I get. Well, wait, I am not even getting 1.5 MBPS at the moment. humm......... | |
xxwinmanxx
join:2009-02-19
Baton Rouge, LA | reply to dhar
 | |
xxwinmanxx
join:2009-02-19
Baton Rouge, LA
| reply to dhar
Default gateway:
Pinging 68.105.28.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 68.105.28.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Primary DNS:
C:\Users\WinMan>ping 68.105.28.11
Pinging 68.105.28.11 with 32 bytes of data:
Reply from 68.105.28.11: bytes=32 time=346ms TTL=61
Reply from 68.105.28.11: bytes=32 time=255ms TTL=61
Reply from 68.105.28.11: bytes=32 time=288ms TTL=61
Reply from 68.105.28.11: bytes=32 time=214ms TTL=61
Ping statistics for 68.105.28.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 214ms, Maximum = 346ms, Average = 275ms | |
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
| I'm not sure if the time of day is a factor in your issue but I am unable to duplicate your ping results when I ping your modem which suggests that the problem is somewhere between the modem and the PC. Have you tried without the router in place recently to see if that makes any difference? | |
j_r0kk
join:2009-03-31
Metairie, LA
| reply to xxwinmanxx
xxwinmanxx,
I'm telling ya, the problem is 100% between the ethernet card and the modem. Call Cox, have them send out a tech with a test modem and a laptop. He'll put his stuff on there and will be able to tell you which is bad. You can have this problem diagnosed in a day with a service call.
-J_r0kk | |
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
| You could also just bypass the router to see if the problem continues. If you still have problems, be sure to try two different computers directly connected to the modem. If it still persists there's a high probability that the ethernet on the modem is having issues. You can always try a USB connection to test that further. | |
dhar
join:2004-07-05
Baton Rouge, LA
| reply to CoxTech1
said by CoxTech1  :I'm not sure if the time of day is a factor in your issue but I am unable to duplicate your ping results when I ping your modem which suggests that the problem is somewhere between the modem and the PC. Have you tried without the router in place recently to see if that makes any difference? I'm not sure what you're saying. xxwinmanxx posted at 10:26 PM, and you replied at 7:48 AM the next day. Unless you pinged him at the same time he posted, I wouldn't expect you to observe his problem, because the problem doesn't exist at all times of the day. When it occurs, it's between roughly 7 PM and 11 PM.
I really hate to see this thread get diluted by unsubstantiated claims that "it's between the PC and the modem", so anyone suggesting this needs to provide a theory to explain how it occurs on an intermittent basis for multiple people at the same time. If the hardware (Motorola SB5100, Linksys WRT610N wired, Realtek 8168 and/or Intel Pro1000 NIC) and/or software (Vista Ultimate, fully patched) has some widespread intermittent Internet slowness bug that occurs only at peak usage times, that would definitely be news to me.
Furthermore, please confirm or deny the claim that it's meaningless to ping the default gateway 68.xxx address, and if it's meaningless, suggest a meaningful test. I mean, I only disclosed that I was pinging this address in my very first post in this thread, and no one has commented on it before. | |
dhar
join:2004-07-05
Baton Rouge, LA
| reply to j_r0kk
said by j_r0kk :xxwinmanxx, I'm telling ya, the problem is 100% between the ethernet card and the modem. Call Cox, have them send out a tech with a test modem and a laptop. He'll put his stuff on there and will be able to tell you which is bad. You can have this problem diagnosed in a day with a service call. -J_r0kk Like I said earlier, my nine year experience with @Home, then TCI, then AT&T, then Cox (I think that's the right branding sequence) is that the exact opposite of what you claim is true. In the first few years, I accepted several service calls for this same problem. Not one technician ever diagnosed anything wrong on my end, yet some time later, the problem would disappear, only to resurface at some future time to last for weeks. There have been at least a half dozen cycles like this, and I have documentation for the following occurrences:
3/26/01
10/15/01 - 10/22/01
11/26/2003 - 12/12/2003
2/25/2004
5/5/2004 - 5/28/2004
7/7/2004
The early dates are routerless and involve completely different hardware and software, different modem, NIC, computer, OS, and even different zip codes. The single date entries above correspond to occurrences that I thought were going to be the start of a new cycle but turned out to be so temporary that I didn't collect more statistics. | |
j_r0kk
join:2009-03-31
Metairie, LA
| Thanks dhar,
But my 10 year experience as a Home Service Tech with Time Warner Cable, a Data Tech(internet tech) with Charter Communications, and a Universal Home Tech (all 3 products) with Cox Communications tells me that if I try to ping the modem's gateway and experience packet loss, the problem is between the ethernet port of the computer and the modem itself. This is why I recommend he set up a trouble call to have a technician come to the house with a test modem and a laptop to prove my theory.
And if you don't believe what I say about pinging the gateway, disconnect your router from your modem and ping your router. You'll see that you don't need to be connected to ping the gateway.
I will NEVER give anyone inaccurate information. Based on what I read on these posts, I can offer an opinion on what I think the cause may be. However, in this case, I'm 100% sure it's between the ethernet port and the modem.
Disclaimer: This diagnosis applies ONLY if all the information presented by the original poster is accurate.
-J_r0kk | |
dhar
join:2004-07-05
Baton Rouge, LA
| said by j_r0kk :Thanks dhar, But my 10 year experience as a Home Service Tech with Time Warner Cable, a Data Tech(internet tech) with Charter Communications, and a Universal Home Tech (all 3 products) with Cox Communications tells me that if I try to ping the modem's gateway and experience packet loss, the problem is between the ethernet port of the computer and the modem itself. This is why I recommend he set up a trouble call to have a technician come to the house with a test modem and a laptop to prove my theory. And if you don't believe what I say about pinging the gateway, disconnect your router from your modem and ping your router. You'll see that you don't need to be connected to ping the gateway. I will NEVER give anyone inaccurate information. Based on what I read on these posts, I can offer an opinion on what I think the cause may be. However, in this case, I'm 100% sure it's between the ethernet port and the modem. Disclaimer: This diagnosis applies ONLY if all the information presented by the original poster is accurate. -J_r0kk I am the original poster, and I've been careful to be accurate in everything I've said.
I just performed the test you suggested and disconnected the ethernet cable between my router and modem. Pinging the same address I've been pinging all along, which I described earlier as the "IP address of the default gateway according to my router", this was the result:
Ping statistics for 68.11.159.129:
Packets: Sent = 24, Received = 0, Lost = 24 (100% loss)
When I reconnected the modem to the router, I got:
Ping statistics for 68.11.159.129:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 12ms, Average = 10ms
So as expected, you're wrong. Please leave it to CoxTech1 and his colleagues to provide support in this forum. | |
xxwinmanxx
join:2009-02-19
Baton Rouge, LA
| reply to dhar
lol dhar, i just ignore the bs. The advice of some is just like calling level one support. "OK reboot your PC" "reboot your modem" "Did that fix it?"
to be clear.
I was using an old surboard 4200 and a linksys router.
I thought my setup was getting old and flaky.
Earlier in the year, I bought a 5101 and new dlink.
Same issues.
Then around Feb or so things cleared up. I thought GREAT!? they fixed it!
Now, back to the same BS again.
also, to be clear. between 5pm and 10pm ish, this is when the problem starts. again, to be clear, THIS PROBLEM EXISTS WITH A ROUTER, NO ROUTER, OR EVEN THE CHEASY USB CONNECTION.
PLZ, no more pc to modem talk unless someone can come up with a logical explination as to why my PC would have an internal clock to say that it was going to slow down my speeds and create packet loss during that time frame.
COX tech, thx for the help. Plz try and run your tests on a monday afternoon or night. | |
xxwinmanxx
join:2009-02-19
Baton Rouge, LA
| reply to dhar
Figured I would show the difference for saturday morning while everyone is outside or still sleeping.
C:\Users\WinMan>ping 68.11.243.31
Pinging 68.11.243.31 with 32 bytes of data:
Reply from 68.11.243.31: bytes=32 time=1ms TTL=64
Reply from 68.11.243.31: bytes=32 time1ms TTL=64
Reply from 68.11.243.31: bytes=32 time1ms TTL=64
Reply from 68.11.243.31: bytes=32 time1ms TTL=64
Ping statistics for 68.11.243.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms | |
madden2k5
join:2009-04-09
Portsmouth, VA
 ·Cox HSI
| reply to xxwinmanxx
Winman, sounds like your problem might be your node in your area is getting overloaded in the evenings. If you are complaining about speed slowdowns between them times during the week. Then most likely your Node in your area is being overloaded and cant handle everyone pulling from it, so its causing your slowdowns and etc.
I was having this same issue, they put me on another Node and now my speeds are fine again. | |
dvijen
join:2008-11-11
Baton Rouge, LA
 ·VOIPo
| reply to dhar
I am in 70810 and seeing the slowdowns everyday in the evening between 6 and 10 pm (less than 2mbps down). I have tried with router/without router/usb connections, no change. I have tried recommended boot sequence, no change. Early morning (4 am) and weekend mornings (until 11 pm) speeds are great.
I asked cox customer service to come and check for the problem, they came last week and found nothing wrong, the speed saga is still the same. I am also on premier plan (9 mbps down).
It is exactly what others think it is, overcrowded node in the evening, but thats when you need the connection, not late at night or early in the morning.
Hope cox will do something to solve this, or I am going to join the list of highly dissatisfied customers.
dvijen | |
j_r0kk
join:2009-03-31
Metairie, LA
| reply to dhar
dhar,
Okay, I won't try to help you any more and I do apologize for confusing you with xxwinmanxx. I'm not familiar with his problem as he just jumped into the thread to complain about a problem he was having that is apparently similar to yours.
However, I do have one nugget for you before I stop offering advice. My instructions were clear, and you've obviously misread them. I don't mind, but I just wanted to let you know. I wrote:
disconnect your router from your modem and ping your router
And then you did the following:
disconnected the ethernet cable between my router and modem. Pinging the same address I've been pinging all along
How can you ping a default gateway of the modem with the ethernet cable disconnected? Is it going to hop through the air bouncing off oxygen atoms? C'mon, that's silly. You were instructed to ping the router.
I also said
you don't need to be connected to ping the gateway
Chances are, the default gateway of your router is 192.168.1.1 or something relatively close if it's a Netgear or a Linksys. You can go to your command prompt, type in ipconfig to find it.
So... unfortunately I'm not wrong, as expected. As you should plainly see, you don't have to be connected to ping the gateway of the router. And before you insult me please read the directions carefully. If you don't want the help simply ignore my posts. I do this because I care and all I'm trying to do is help.
-J_r0kk
P.S. If you can ping the default gateway of the router and not get packet loss, you've solved the problem because it's the ethernet port of the modem. If you still get packet loss, it's either the ethernet port of the computer or the cat5 jumper. | |
DDR329
@cox.net
| reply to xxwinmanxx
winman,
You have a different issue all together. The download speed stays high versus the upload speed going in the dirt. The exact opposite from everyone else lately. Normally when the upload is bad this indicates an issue with the modem communicating back with the server.
Since you have already checked the modem and router it would be safe to say a technician is needed to diagnose further. Make sure you specify the exact times the upload speed is dropping as there could be a noise issue in your node, this is different than just too many modems. | |
dhar
join:2004-07-05
Baton Rouge, LA
| reply to j_r0kk
said by j_r0kk :However, I do have one nugget for you before I stop offering advice. My instructions were clear, and you've obviously misread them. I don't mind, but I just wanted to let you know. I wrote: disconnect your router from your modem and ping your routerAnd then you did the following: disconnected the ethernet cable between my router and modem. Pinging the same address I've been pinging all alongHow can you ping a default gateway of the modem with the ethernet cable disconnected? Is it going to hop through the air bouncing off oxygen atoms? C'mon, that's silly. You were instructed to ping the router. I also said you don't need to be connected to ping the gatewayChances are, the default gateway of your router is 192.168.1.1 or something relatively close if it's a Netgear or a Linksys. You can go to your command prompt, type in ipconfig to find it. The only "gateway" we've been talking about is the one I identified in the first post in this thread and the one I clarified to you later as "the default gateway according to the router", the one with the address 68.11.159.129. I thought your suggestion was truly silly, especially your statement that "you don't need to be connected to ping the gateway", which I didn't need to test to know was false for the only gateway I've been talking about. I very precisely stated what I did specifically to call attention to this, and I'm glad to see you understand why. That said, I don't see the value in disconnecting the modem to ping the router itself when I have no local network issues at the times I have Internet issues (I would know if I did), and that's another reason I didn't get where you were coming from.
Despite ignoring almost everything I and others have been saying for months in this thread and asserting you know the answer with 100% certainty, an answer that is directly at odds with what has been described, if you had simply said, "Let's rule out the router as the source of the problem," it would have been clear, and I might have humored you without any sarcasm.
So... unfortunately I'm not wrong, as expected. As you should plainly see, you don't have to be connected to ping the gateway of the router. Again, that's not exactly a revelation. Pinging the router is not a problem.
And before you insult me please read the directions carefully. If you don't want the help simply ignore my posts. I do this because I care and all I'm trying to do is help. Please then take what I said above as constructive criticism.
-J_r0kk
P.S. If you can ping the default gateway of the router and not get packet loss, you've solved the problem because it's the ethernet port of the modem. If you still get packet loss, it's either the ethernet port of the computer or the cat5 jumper.
I don't follow your "P.S." In what way have I "solved the problem" if I determine it's the "ethernet port of the modem"? Seriously, I don't know if you would conclude it's the modem at fault or have reversed your stance and left open the possibility the problem exists outside the home. Either way, I guess I would have to buy a new modem to test the theory, but again, as my current modem only gets "tired" between 7-11 PM on an intermittent basis, I would be reluctant to do that given my long experience with this sort of problem, which I've previously described in some detail, not to mention reports by others having the same problem. Note also that I can state that interval with confidence because those "peak hours" are actually my "off-peak hours", and there's zero chance that this is happening all day long or late at night without my noticing. It could only be happening between 3-9 AM without my noticing, and even that's variable. | |
j_r0kk
join:2009-03-31
Metairie, LA
1 edit | dhar,
I understand your "peak hours" theory, BUT, when you ping the modem and get packet loss, the problem is within your network. It's got absolutely nothing to do with anything outside the very room in which your modem and computer lies.
I am in no way backing out of my stance. I originally stated the problem is between the ethernet card and the modem. I only used the router example because if you removed the coax from the modem you wouldn't be able to ping a gateway. I apologize for not explaining myself more thoroughly. The only thing that would make this theory not 100% accurate is if you try to ping the modem's gateway when the modem is not locked on, but you never mentioned that problem so I have unfortunately assumed that you're not having an intermittent connectivity issue. Am I correct in this assumption?
With that being said, don't go purchase another modem. Remember my original post: Simply call Cox and have them send a technician to your home. This technician should have a laptop and a test modem to help diagnose the problem.
I understand your disgust with this whole thread as you're only trying to find an answer to your packet loss. However, this is truly a problem that could have been diagnosed and repaired in a 30 minute service call weeks ago.
Your problem is not uncommon. I see this at LEAST once a month. It usually occurs after a power surge of some sort. The other posters may be having a similar problem but I will say that each problem is different in its own way. Almost 90% of the problems with video, HSI, and phone however, are from the tap to Customer Equipment.
The conspiracy theories about "peak hours" and "not enough bandwidth" are true in some cases... but most times they are repaired by a simple service call. Give these technicians a chance to do their work. This is what they're trained to do and they truly want to make sure you're happy with your service.
Good luck. I mean it. And let me know how the service call goes.
-J_r0kk | |
j_r0kk
join:2009-03-31
Metairie, LA
| reply to xxwinmanxx
xxwinmanxx,
I got you confused with dhar. Your problem is NOT between the computer and the modem. You can plainly see that when you ping the modem's gateway and receive 0% packet loss. Maybe you should open another thread to describe your problem
-J_r0kk | |
dhar
join:2004-07-05
Baton Rouge, LA
| reply to j_r0kk
said by j_r0kk :dhar, I understand your "peak hours" theory, BUT, when you ping the modem and get packet loss, the problem is within your network. It's got absolutely nothing to do with anything outside the very room in which your modem and computer lies. Why do you think I'm "pinging the modem" and the address I've been using is "within my network?" This page seem to differ with you:
»homepage.ntlworld.com/robin.d.h.···ddr.html
"On a cable network, the Default Gateway address is physically part of the UBR (head-end)."
The article goes on to talk about "public" and "private" default gateway addresses in the "Finding the UBR address" section. I would think the 10.xxx address I see as the first hop in tracert is the "private" counterpart to the "public" default gateway address 68.11.159.129 I've been using all along for my ping tests. I know they behave identically to ping and tracert. It should be obvious I do not believe the default gateway is my modem, and that I do believe the default gateway is Cox equipment outside my house, and that I've believed this all along. If this is wrong, I will need more than your say-so to establish it. No one besides you has commented on this before.
I am in no way backing out of my stance. I originally stated the problem is between the ethernet card and the modem. I only used the router example because if you removed the coax from the modem you wouldn't be able to ping a gateway. I apologize for not explaining myself more thoroughly. The only thing that would make this theory not 100% accurate is if you try to ping the modem's gateway when the modem is not locked on, but you never mentioned that problem so I have unfortunately assumed that you're not having an intermittent connectivity issue. Am I correct in this assumption?
With that being said, don't go purchase another modem. Remember my original post: Simply call Cox and have them send a technician to your home. This technician should have a laptop and a test modem to help diagnose the problem.
I understand your disgust with this whole thread as you're only trying to find an answer to your packet loss. However, this is truly a problem that could have been diagnosed and repaired in a 30 minute service call weeks ago. All I can suggest is that you reread what I've described in detail concerning my experience with this problem at multiple locations using different modems, with and without a router, and multiple service calls. To a one, the technicians would find nothing wrong at the time they showed up and declare there is no problem. I'm not accepting another service call for this unless Cox agrees to be "on call" and can show up when I'm having the problem; they would also need to be able to stay a while, as when the problem does occur, it comes and goes. I don't expect they will agree to that, which is why I continue to post here when I have the problem. I don't know what the cause of the problem is. All I know is that it will go away and performance will be great for months at a time, and the only explanation seems to be that Cox has made some improvement outside of my home. I did not have this problem the first year or so living in my new-construction home. Of course, Cox won't divulge what if anything it's done, and no explanation is ever offered for the times of good and bad performance. But I'm just restating things I've already said.
Your problem is not uncommon. I see this at LEAST once a month. It usually occurs after a power surge of some sort. The other posters may be having a similar problem but I will say that each problem is different in its own way. Almost 90% of the problems with video, HSI, and phone however, are from the tap to Customer Equipment.
The conspiracy theories about "peak hours" and "not enough bandwidth" are true in some cases... but most times they are repaired by a simple service call. Give these technicians a chance to do their work. This is what they're trained to do and they truly want to make sure you're happy with your service.
Good luck. I mean it. And let me know how the service call goes.
-J_r0kk
See above and prior messages regarding the complete lack of success of multiple past service calls. | |
-
|
