35/35/Internet plan but only 8M upload

Wanted to pick the brains of this community to see if they can help resolve this. Here are the results of my FIOS speed test, it looks like the upload speed is sender limited but I've no idea on what changes I can do that may impact this. I'm running Windows 7 64bit and I've replaced my old Verizon D Link router (one of the originals with the NIM box) with a Dlink DIR-655 to get wireless N in the home. :

Broadband Speed Test

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 8.07Mb/s
running 10s inbound test (server to client) . . . . . . 42.18Mb/s

------ Client System Details ------
OS data: Name = Windows Vista, Architecture = x86, Version = 6.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_10

------ Web100 Detailed Analysis ------
Client Receive Window detected at 248064 bytes.
45 Mbps T3/DS3 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 33.39 msec; the Packet size = 1452 Bytes; and
No packet loss - but packets arrived out-of-order 0.01% of the time
This connection is receiver limited 2.0% of the time.
This connection is sender limited 97.54% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [71.240.xxx.xx] but Client says [192.168.0.141]

Any ideas gratefully received, Andy

Accepted answers

Andygiddings

Got the Westell router drop shipped today and hooked it up. Problem solved and am now getting upload speeds in to 30M range. Must be some config setting on the Dlink DIR-655 that was causing the issue. Might need to go over to their support boards and see if there is a solution but for now am good to go. Thanks to all those that provided suggestions on resolving this, Andy

All comments

eljefe2

Y'know, I only get 5.2 mb/s upstream on that Argone Labs test, yet on all other speed tests I'm seeing ~33 mb/s upstream, which is confirmed by real world measurements to a few different servers.

What do you get with the FiOS speed test at http://my.verizon.com/micro/speedtest/broadband/ and/or a couple of servers near you on www.speedtest.net ?

Hubrisnxs

1. Make sure you are is hardwired

2. Make sure you re-runs the Verizon Optimizer »my.verizon.com/micro/speedoptimi···ult.aspx

3. Make sure you are testing at »speedtest.verizon.net

what does it look like with those conditions?

For running the optimizer, you have to open Internet explorer in administrator mode. so right click on internet explorer, and hit run as administrator, then go to the verizon optimizer website.

Andygiddings

Eljefe and Hubrisnxs, thanks for your responses. My comments - yes am hardwired, have already run the optimiser and am using the Verizon speedtest. Have also used Speedtest.net with a variety of servers and get approx the same results.

eljefe2

Ok....a few more thoughts.

Take a look at your registry, this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AFD\Parameters

I found the optimizer didn't tweak that right and I manually set mine thusly (I'm also running Win 7 Pro x64):

DefaultSendWindow 261360

Do you have another PC you can try? A laptop maybe? Same results?

In your oriignal post you mention the DIR-655. Is that your only router? Ethernet between your ONT and the DIR-655? If that's the case I wonder if you could get Verizon to send you an Actiontec or Westell router. I don't think they'll give you any tech support with the DIR-655 as your primrary router and it might be worth swapping in an Actiontec or Westell as a troubleshooting step. If the problem is on the WAN side or your router you'll have to involve Verizon tech support anyway.