somebody PLEASE help
up until midday I get 35 to 40mbit upload no problems, then at evenings it goes down! DOWN DOWN! I was lucky on this one I've had it as low as 0.5mbit..
I've contacted verizon multiple times, they swaped the ONT, balanced the BON and still NOTHING
I'm in an area where the only provider is either FIOS or , and I'm considering satellite if they can fix my low upload speeds!
Analysis information:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [32768]
running 10s outbound test (client to server) . . . . . 5.85Mb/s
running 10s inbound test (server to client) . . . . . . 83.77Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11
------ 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
Normal duplex operation found.
Web100 reports the Round trip time = 23.15 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 4.93% of the time.
This connection is sender limited 94.6% 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 [{edited for privacy}] but Client says [192.168.xxxxx]
Analysis information:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [32768]
running 10s outbound test (client to server) . . . . . 2.73Mb/s
running 10s inbound test (server to client) . . . . . . 54.84Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11
------ Web100 Detailed Analysis ------
Client Receive Window detected at 261120 bytes.
45 Mbps T3/DS3 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 = 23.75 msec; the Packet size = 1360 Bytes; and
There were 71 packets retransmitted, 2086 duplicate acks received, and 2121 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 8.32% of the time.
This connection is sender limited 82.02% of the time.
This connection is network limited 9.66% 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 [xxxxxxxxxxxx] but Client says [192.168.xxxxxx]
your send buffer is really REALLY low. You may want to run the fios optimizer, and see if you can increase it
my send buffer is fine for what I do and the type of data I upload, as I said in the 1st post, I can get the 35mbit upload no problem during the day, the problem is towards the afternoon and evening!
Fios Bandwidth Restrictions? - Verizon Fiber Optics | DSLReports ...
According to a senior VZ tech
A properly optimized Windows PC will have a default send window size of 261360 bytes (called SendBufferSize in the Verizon Speedtest results screen).
I keep losing my forum post.
ok, still, could anyone please explain why, with my meagle 32k sendwindow I get 35mbit up during the day but cannot get more than 10mbig up towards the evening and it goes down to less than 1mbit at midnight?
so this isn't a provisioning problem, it's a load problem in my area, I've contacted verizon multiple times and they can't fix it!! I'm out of ideas honestly
if you're using windows auto size feature, then that would explain it.
if you think it's a load problem then what you want to do is post some traceroutes.
Do traceroutes during the day when everything is wonderful. and then do some at night when it's bad.
compare and contrast.
here we go, 10:20pm: also set the SendBufferSize to recommended so people would get off my back about it. Analysis information:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 955.59Kb/s
running 10s inbound test (server to client) . . . . . . 42.84Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11
------ Web100 Detailed Analysis ------
Client Receive Window detected at 66792 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 = 10.96 msec; the Packet size = 1452 Bytes; and
No packet loss - but packets arrived out-of-order 0.02% of the time
This connection is receiver limited 39.35% of the time.
This connection is sender limited 60.15% 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
This also stands out to me. 45 Mbps T3/DS3 link found.
Link set to Full Duplex mode
45 is a little low of a link to be handling a 75 mb connection.
Unfortunately that isn't something peers in a forum can fix, you might have to re-engage Verizon.
Point out that you've been sent a new router, you are hardwired, you have optimized and are testing at their site, and getting poor speeds, and that this sticks out to you "45 Mbps T3/DS3 link found."
then ask if they have network tech's available that can look into that, A network tech won't likely speak with you, they are there to support other tech's, but I think it wouldn't hurt for one to take a look. So that means either a call or a chat support session, or if you've had bad luck both ways, try their twitter support. it's exceptional.
the connection I have is a gigabit to my router and the router is connected to the ONT as 100 full duplex, no clue where this this 45 is coming from.
I'm just trying to figure out if anyone else is suffering the same problems as me, which is, perfect network during the day and awful at night 😞
Start a new topic or ask questions in the open forum.
