FiOS Internet

[#1]

Your Computer is Optimized!
Your system's settings are already optimized for Verizon FiOS Internet Service. There are no changes needed.

Notes:

• Optimize each PC using any type of connection the PC normally uses to connect to the network (wired or wireless). If you use both types of connections on a PC
  (such as on a laptop), you must run the optimizer twice on that PC. First, run the optimizer while connected by wire, plugged directly into your router. Then, remove
  the wired connection, restart the PC, establish the wireless connection, and re-run the optimizer.

Important! For the optimization settings to take effect, you must power off your computer and then turn it back on again (do NOT use the Restart option).

I have all the duplex set to the highest settings 1 gig full duplex 

[#2]

---

 Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [522720]
running 10s outbound test (client to server) . . . . . 39.39Mb/s
running 10s inbound test (server to client) . . . . . . 150.30Mb/s

---

MUCH better.   so now 150/40 down/up roughly. 

now with your pc properly optimized, I would expect it's verizon's turn if you really need that extra 20 mb upload.  Do you do anything with upload that warrants 60 vs 40 mb upstream?  is it worth you going through more trouble to get that?   if not then I think you're in a good spot.  

[#3]

ya because thats what im paying for if they give me discount then it wil be fine. also it says alarm duplex i have everything the same but stikk get the.

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [522720]
running 10s outbound test (client to server) . . . . . 39.28Mb/s
running 10s inbound test (server to client) . . . . . . 152.62Mb/s

------ Client System Details ------
OS data: Name = Windows Vista, Architecture = x86, Version = 6.0
Java data: Vendor = Oracle Corporation, Version = 1.7.0_05

------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
45 Mbps T3/DS3 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Alarm: Duplex mismatch condition found: Host set to Full and Switch set to Half duplexD

Web100 reports the Round trip time = 12.12 msec; the Packet size = 1452 Bytes; and 
There were 17 packets retransmitted, 471 duplicate acks received, and 280 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 4.42% of the time.
This connection is sender limited 94.55% of the time.
This connection is network limited 1.03% 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 say 

[#4 · Accepted solution]

Have someone in the Fiber Solutions Center in Verizon check your provisioned speed. It sounds like your ONT might not be provisioned correctly if you are in fact getting 150Mbps/40Mbps and cannot get higher. Lots of other factors at play here but the NDT tests are also known to mis-diagnose issues as well since they make deterministic decisions based on how the traffic flows to and from the client and server. Bursty traffic can goof up their results.

The best way to check though, is to run multiple uploads at once and use a Network Meter program to measure the upload speed. If it locks at 40 and refuses to go higher and you are not using QoS on the router or on the system (Netlimiter?) the ONT probably needs to have it's provisioning fixed.

[#5]

just got down with the tech online took him an hour but he got it done. He said the system had to erased and a new one implemented and I have no clue what that means. Everything works good now and hopelly it stays that way.

[#6]

Glad to hear it's all fixed!