Need help with slow DSL Speeds

[hcrockville]

I have the 768kbps plan and am only receving about 170kbps downloads (day and night)

I have a Westell B90-210015-04  DSL Modem  (Rev E)

Linsys BEFW11S4 Router  (Version 4)

My operating system is Windows XP

I have logged into my router looking for statistics logs but don't see them so I can't attach any other info at this time

I have been through many of the forums but don't see reference to the slower DSL plans nor the older routers and modems. Your help/assistance would be appreciated

Thanks in advance

[hcrockville]

To clarify, I would be more than happy to find the tranceiver statistics if I knew where to look.  When I loging to 192.168.1.1 I am on the router, not the modem.  How do I get to the modem to provide the information that people need to debug the slow speeds?  A little bit of detail in the explanation would help.. Thanks

[hcrockville]

also, on the router it says that I am using PPoE with Local DHCP enabled

[LiquidFusion]

System Monitoring - Advanced Status - Transceiver Statistics

[dslr595148]

#1 In the Linksys router at Setup -> Basic Setup

a) what is the current Local IP Address?

b) What is the current Speed & Duplex ( if that applies ) ?

For example when I looked at http://ui.linksys.com/files/BEFW11S4/v4/1.52.02/index.htm

It has a Speed & Duplex setting, but perhaps your doesn't ??

#2 In the Linksys go to Wireless -> Basic Wireless Settings

#3 Is the wireless enabled?

#4 In the Linksys go to Wireless -> Wireless Security

#5 Wireless Security is enabled?

#6 If so, what level is it set to?

#7 In the Linksys go to Administration -> Management

#8 What is the current UPnP Setting?

#9 Do you have a hub or swich that is not part of a router?

#10 Does your computer have at least two NICs?

#11 If so, is one of them - a wired NIC?

[Time4Cable]

I also am seeing very slow DSL speeds. 220 kbs on the 768 kbs package. I contacted tech support live chat, who diagnosed a line problem and said they would have a tech. call me on a voice line. Hw also did a speed test and came up with the same results at which point he escalated me to his 'supervisor'. The 'supervisor' wasted no time in telling me my solution was an immediate upgrade to FIOS. Despite my protestations the only 'solution' to the problem was an immediate sign up to FIOS. You know, I got the distinct impression that the 'supervisor' was not in fact a support tech. but a salesperson, whose job was simply to upsell me. Has anyone else had similiar experience?

[hcrockville]

Thanks everyone for your responses.  I had called Verizon who just sent me a new modem  (Westell 6100 G) so I connected that up this morning.  Out of the box with computer connected directly to modem I am now getting 400kbps download  (should I expect to get a lot closer to the 768 kbps download?)

Meanwhile I can't connect the router to the modem so I have just printed off a lot of  how to's and will try that in the next day or so. Will keep everyone up to date.

[smith6612]

Back in the day when Verizon was selling the Linksys routers (I'm pretty sure they sold the BEFW11S4s), a common setup for them was to have you bridge your DSL modem if it were a Westell 2200 or a Westell 6100, and use PPPoE on the router to authenticate the connection. With this kind of setup, you would generally need to plug a PC into the modem directly, not establishing any PPPoE connectivity and then assign your PC a Static IP address so that you could log into the modem's web interface.

Like the Westell 2200s, the 6100s Verizon sends out operate in Router mode, where the modem takes care of PPPoE connectivity and also runs as a router. When this is being done, you cannot establish a PPPoE connection from your router as the modem wouldn't know what to do with it in the first place, since it is running as a router. You would need to bridge the modem in order to use PPPoE directly on the router (which is the suggested way of doing things if you aren't using a Gateway).

With the new modem, if you go to http://192.168.1.1/ and choose System Monitoring, Advanced Monitors, and then Transceiver Statistics, you should see a table with a bunch of information on it. Post that information up for us to see. If you need a Username and Password, try the following:

admin/password

admin/password1

admin/admin

admin/admin1

To obtain the Statistics from your Westell 2100, you would need to use the Westell Diagnostic Utility, or the Westell Modem Browser as it's also called to get the data from the modem. You can find it using this link to the DSLReports website:

http://www.dslreports.com/faq/7553

If you do use the tool above, your PC's Firewall must be disabled and shut down temporarilly, and any other security software should be turned off until the tool is closed. Additionally, the PC must be plugged straight into the modem.

With the 768kbps provisioning, you should be running at a Sync rate of 864kbps downstresam, 160kbps upstream on G.DMT mode. With ADSL2/ADSL2+, the numbers will be lower by no more than 4kbps of the mentioned values. Any lower would be from something else which we'll investigate once we see Transceiver Statistics. The 768kbps package should speed test at 740kbps download (~91KB/s Transfer rate) and 130kbps up (~16.5KB/s).

[hcrockville]

Sorry about the delay in getting back.  Takes awhile to get free time around the house with little kids.  Anyway I converted my 6100 back to a modem/router from just bridging the modem.

With the Westell 6100 my download speeds are 450kbps and upload is 130kbps  on a line that is supposed to be 768kbps down load

My Trasceiver stats are:

Transceiver Statistics Transceiver Revision 3.3.6.10.0.1 Vendor ID Code 4D54 Line Mode ADSL_G.dmt Data Path INTERLEAVED
Transceiver Information Down Stream Path Up Stream Path DSL Speed (Kbits/Sec) 512 160 Margin (dB) 25.2 31.0 Line Attenuation (dB) 46.2 31.5 Transmit Power (dBm) 9.8 11.9

My Log info is


1. Mar 18 10:58:49         user.err        syslog:         WSTLIB_HTTP: Failed to parse URL:
2. Mar 18 10:41:58         user.err        syslog:         WSTLIB_HTTP: Failed to parse URL:
3. Mar 18 10:39:30         user.err        syslog:         WSTLIB_HTTP: Failed to parse URL:
4. Mar 18 10:36:29         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
5. Mar 18 10:36:29         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:6 CONNECTION REQUEST
6. Mar 18 10:36:29         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
7. Mar 18 10:36:29         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
8. Mar 18 10:36:25         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
9. Mar 18 10:36:21         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:6 CONNECTION REQUEST
10. Mar 18 10:36:21         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
11. Mar 18 10:36:21         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
12. Mar 18 10:36:18         daemon.info     cwmpd[180]:     CWMP: Connection request from ACS succeeded
13. Mar 18 10:36:18         daemon.info     cwmpd[180]:     CWMP: Connection request from ACS succeeded
14. Mar 18 10:36:17         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
15. Mar 18 10:36:17         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:0 BOOTSTRAP,4 VALUE CHANGE
16. Mar 18 10:36:17         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
17. Mar 18 10:36:17         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
18. Mar 18 10:32:10         daemon.info     dnsmasq[152]:   DHCPACK(br0) 192.168.1.18 00:21:86:9a:0f:59 COHENH2
19. Mar 18 10:32:10         daemon.info     dnsmasq[152]:   DHCPREQUEST(br0) 192.168.1.18 00:21:86:9a:0f:59
20. Mar 18 10:32:09         daemon.err      net_mgr[173]:   PPPKICK: pppoe_getstate failed
21. Mar 18 10:31:50         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 401
22. Mar 18 10:31:47         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:6 CONNECTION REQUEST
23. Mar 18 10:31:47         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
24. Mar 18 10:31:47         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
25. Mar 18 10:31:44         daemon.info     cwmpd[180]:     CWMP: Connection request from ACS succeeded
26. Mar 18 10:31:41         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
27. Mar 18 10:31:40         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:0 BOOTSTRAP,4 VALUE CHANGE
28. Mar 18 10:31:40         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
29. Mar 18 10:31:40         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
30. Mar 18 10:31:36         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
31. Mar 18 10:31:35         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:6 CONNECTION REQUEST
32. Mar 18 10:31:35         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
33. Mar 18 10:31:35         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
34. Mar 18 10:31:31         daemon.info     cwmpd[180]:     CWMP: Connection request from ACS succeeded
35. Mar 18 10:31:31         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
36. Mar 18 10:31:31         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:2 PERIODIC
37. Mar 18 10:31:31         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
38. Mar 18 10:31:31         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
39. Mar 18 10:30:33         daemon.err      net_mgr[173]:   PPPKICK: pppoe_getstate failed
40. Mar 18 10:28:07         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
41. Mar 18 10:28:07         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:0 BOOTSTRAP,4 VALUE CHANGE
42. Mar 18 10:28:07         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
43. Mar 18 10:28:07         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
44. Mar 18 10:28:03         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 401
45. Mar 18 10:28:01         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:6 CONNECTION REQUEST
46. Mar 18 10:28:01         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic
47. Mar 18 10:28:01         daemon.info     cwmpd[156]:     CWMP: Inform Sent Successfully
48. Mar 18 10:27:58         daemon.info     cwmpd[180]:     CWMP: Connection request from ACS succeeded
49. Mar 18 10:27:57         daemon.info     cwmpd[156]:     CWMP: Final Http Return Code = 204
50. Mar 18 10:27:55         daemon.info     cwmpd[156]:     CWMP: Inform (200). The following events are true:0 BOOTSTRAP,4 VALUE CHANGE
51. Mar 18 10:27:55         daemon.info     cwmpd[156]:     CWMP: SSL Status = SSL Connection Succeeded,TCP Status = TCP Connected,Authentication Type = Basic

Hope this helps

[smith6612]

Your log is showing what would be the remote management software running on the modem, which Verizon uses to log into your modem to perform tasks such as Technical support and firmware upgrades. Other than that, it isn't showing anything useful. If that's the complete log from the "All" category, then I suppose that would really be it in that perspective.

So as to the speeds, those sync rates suggest that your line for some reason was lowered in speed under Verizon's Optimization system. Your margins are very high and attenuation is good, so I don't see a reason as to why it was optimized unless it ran at a time where there was a noise spike. Again, without having a complete set of logs, I can't say for sure. The Optimization System runs once every few weeks it seems, so it should turn the speed back up to normal rates if the line remains stable. Additionally, what might bypass the wait all together is to ask Verizon (Billing Department) to upgrade your line profile from the 768kbps/128kbps profile to the 1Mbps/384kbps profile, as they fall within the same plan and will not cost you anything more.

[hcrockville]

Your log is showing what would be the remote management software running on the modem, which Verizon uses to log into your modem to perform tasks such as Technical support and firmware upgrades. Other than that, it isn't showing anything useful. If that's the complete log from the "All" category, then I suppose that would really be it in that perspective.

     It was the "all" category from which I took the stats.  I will try again after I reset the modem to not being a bridge and letting it run for a day or so

So as to the speeds, those sync rates suggest that your line for some reason was lowered in speed under Verizon's Optimization system. Your margins are very high and attenuation is good, so I don't see a reason as to why it was optimized unless it ran at a time where there was a noise spike. Again, without having a complete set of logs, I can't say for sure. The Optimization System runs once every few weeks it seems, so it should turn the speed back up to normal rates if the line remains stable. Additionally, what might bypass the wait all together is to ask Verizon (Billing Department) to upgrade your line profile from the 768kbps/128kbps profile to the 1Mbps/384kbps profile, as they fall within the same plan and will not cost you anything more.

    Spoke with Verizon last night. They said that my 440kbps falls in their acceptable limits for throughput, for which that has been the steady value so far since the new modem was installed. Do I have any leg to stand on that I should have to accept a 40% degradation off a plan?

   Verizon is upgrading me to the 1Mbps/384kbps as you suggested (actually cheaper than what I am paying right now by $2 per month). I will check the throughputs once I see that occuring and report back.

[hcrockville]

Your log is showing what would be the remote management software running on the modem, which Verizon uses to log into your modem to perform tasks such as Technical support and firmware upgrades. Other than that, it isn't showing anything useful. If that's the complete log from the "All" category, then I suppose that would really be it in that perspective.

     It was the "all" category from which I took the stats.  I will try again after I reset the modem to not being a bridge and letting it run for a day or so

So as to the speeds, those sync rates suggest that your line for some reason was lowered in speed under Verizon's Optimization system. Your margins are very high and attenuation is good, so I don't see a reason as to why it was optimized unless it ran at a time where there was a noise spike. Again, without having a complete set of logs, I can't say for sure. The Optimization System runs once every few weeks it seems, so it should turn the speed back up to normal rates if the line remains stable. Additionally, what might bypass the wait all together is to ask Verizon (Billing Department) to upgrade your line profile from the 768kbps/128kbps profile to the 1Mbps/384kbps profile, as they fall within the same plan and will not cost you anything more.

    Spoke with Verizon last night. They said that my 440kbps falls in their acceptable limits for throughput, for which that has been the steady value so far since the new modem was installed. Do I have any leg to stand on that I should have to accept a 40% degradation off a plan?

   Verizon is upgrading me to the 1Mbps/384kbps as you suggested (actually cheaper than what I am paying right now by $2 per month). I will check the throughputs once I see that occuring and report back.

[techmessiah]

Hi,

-The modem that you have (Westell 2100) is a bridge modem with an IP address of 169.xx.x.xxx and hence you wont be able to access the modem page, but the router page only.

-Check speedtest.net to check your download and upload speeds.

-Swapping ends of the grey cable (RJ11) connecting your modem to the wall jack, while the modem is off, helps to increase speeds.

-If you have phone service also from verizon, unplug all phone lines from the jacks and check speed

-if all these steps to not work, call verizon and set up appointment for technician visit

-they will ask you to do all these steps, just talk and act like you ARE doing these steps (verizon has very strict policies about sending out technicians without troubleshooting and reps are heavily marked down if caught sending techs to customers without troubleshooting)

-Tech will come to your service address within usually 24-48 hrs.