FiOS Internet

[#1]

My issue is I currently get 52 down/34 up instead of 75/35.

Here is what i tried:

1) Actiontec MI424wr2 connected via cat 5 to the ont. My computers are hardwired to the router.  i've restarted both ONT (removed battery) and restarted the router. Both computers get rougly 50 down 35ish up.

2) Airport extreme to the ont. computers hardwired to the router. I get the same speeds.

3) direct connect via cat 5 to the ont. no change.

I have contacted verzion and scheduled a technician to arrive on 7/28. Instead, The technician claimed he "replaced my router" on 7/27 and closed the ticket. At this point i'm tempted to reduce my plan to the 50/25 just so i can get the speeds i'm paying for and not have to deal with verzion support.  Has anyone ever run into this issue? What was the solution?

Here is the log from the latest speed test.

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [131768]
running 10s outbound test (client to server) . . . . . 34.87Mb/s
running 10s inbound test (server to client) . . . . . . 52.56Mb/s

------ Client System Details ------
OS data: Name = Mac OS X, Architecture = x86_64, Version = 10.8
Java data: Vendor = Apple Inc., Version = 1.6.0_33

------ Web100 Detailed Analysis ------
Client Receive Window detected at 524288 bytes.
2.4 Gbps OC-48 link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 47.68 msec; the Packet size = 1448 Bytes; and
There were 54 packets retransmitted, 1678 duplicate acks received, and 1701 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 3.15% of the time.
Increasing the the client's receive buffer (512.0 KB) will improve performance
This connection is sender limited 90.32% of the time.
This connection is network limited 6.52% 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: ON
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 [96.245.254.242] but Client says [192.168.1.3]

[#2]

I am not that familiar with MAC OS network tuning.

But one bad thing i see is link set to Half-duplex.

There is a suggestion of increasing buffering in the data.

But this section also sounds bad.

  There were 54 packets retransmitted, 1678 duplicate acks received, and 1701 SACK blocks received
 ...

  Increasing the the client's receive buffer (512.0 KB) will improve performance

[#3]

Thanks for the info. I reconnected my airport extreme and set both router and computer to full duplex mode only.

here is an updated speed test

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [131768]
running 10s outbound test (client to server) . . . . . 36.78Mb/s
running 10s inbound test (server to client) . . . . . . 55.36Mb/s

------ Client System Details ------
OS data: Name = Mac OS X, Architecture = x86_64, Version = 10.8
Java data: Vendor = Apple Inc., Version = 1.6.0_33

------ Web100 Detailed Analysis ------
Client Receive Window detected at 451072 bytes.
2.4 Gbps OC-48 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 = 61.08 msec; the Packet size = 1448 Bytes; and
No packet loss was observed.
This connection is receiver limited 2.74% of the time.
Increasing the the client's receive buffer (440.0 KB) will improve performance
This connection is sender limited 96.75% of the time.
This connection is network limited 0.51% 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: ON
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 [96.245.254.242] but Client says [192.168.1.50]

Anyone know which link is set to half duplex? 

[#4]

I found some instructions online to "optimize" the network speed.

http://rolande.wordpress.com/2010/12/30/performance-tuning-the-network-stack-on-mac-osx-10-6/

It now shows a full duplex connection.

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [131768]
running 10s outbound test (client to server) . . . . . 36.13Mb/s
running 10s inbound test (server to client) . . . . . . 55.46Mb/s

------ Client System Details ------
OS data: Name = Mac OS X, Architecture = x86_64, Version = 10.8
Java data: Vendor = Apple Inc., Version = 1.6.0_33

------ Web100 Detailed Analysis ------
Client Receive Window detected at 449616 bytes.
622 Mbps OC-12 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 = 61.22 msec; the Packet size = 1448 Bytes; and 
No packet loss was observed.
This connection is receiver limited 2.32% of the time.
Increasing the the client's receive buffer (439.0 KB) will improve performance
This connection is sender limited 97.26% 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: ON
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 [96.245.254.242] but Client says [192.168.1.50]

at this point, i'm going to try and alter the client buffer. I'll post back my findings.

[#5]

I think the client buffer isnfine, you need to do the send buffer.   That is what looks low to me

[#6]

the send buffer size should be 522720 or better.

[#7]

My connection is much slower than promised too.

How do you set the link to 'full duplex'??

[#8]

So i tested out the connection with a Windows computer and received a slightly faster speed 55/35. At this point i'm convinced the problem is with the ONT or the connection to the pole. I've replaced the computers, routers, ethernet cables with little change. I guess i now have to contact verizon. Hopefully they show up this time around.

[#9]

make sure the windows machine is also set that high with it's sendbuffer.   if it isn't then it's possible you have multple machines  that are not optimized, but other than that, yes get vz out there. 

[#10]

just gonna throw out my 2 cents here

I would go to speedguide.net run the tcp/ip analyzer and check the RWIN needs to be over a 1 million

what your getting for a download not necessarily the send which is your upload