Location New York City
Date:Jan.15.2015
Time :09:30 Pm
After the optimization :
Location New York City
Date:Jan.15.2015
Time :09:30 Pm
The Network Diagnostic Tool results below will be used by our Verizon Technical Support Team to review your computer settings.
Analysis information:
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 34.22Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 9.18Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_71
------ Web100 Detailed Analysis ------
2.4 Gbps OC-48 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 27.27 msec; the Packet size = 1460 Bytes; and
There were 54 packets retransmitted, 530 duplicate acks received, and 578 SACK blocks received
The connection was idle 0 seconds (0%) of the time
S2C throughput test: Packet queuing detected: 71.41%
This connection is sender limited 61.28% of the time.
This connection is network limited 37.89% 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
Current Send Buffer 8 Kbyte
Current Receive Buffer 8 Kbyte
Display Name = Microsoft ISATAP Adapter MTU = 1280
Display Name = Teredo Tunneling Pseudo-Interface MTU = 1280
Display Name = Microsoft ISATAP Adapter #2 MTU = 1280
Display Name = Realtek PCIe GBE Family Controller MTU = 1500
Display Name = Realtek PCIe GBE Family Controller #2 MTU = 1500
Server 'nyfiosspeed1.west.verizon.net' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Information: Network Middlebox is modifying Window scaling option
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.1.153]
@Predator wrote:
Location New York City
Date:Jan.15.2015
Time :09:30 Pm
Current Send Buffer 8 Kbyte
Current Receive Buffer 8 Kbyte
From your results page it shows you aren't optimized properly and that your PC is limiting your speed. Send buffer should be 255k
So try to run the optimizer, or go to speedguide.net and use their optimizer
Verizon Online -- FiOS Speed Optimizer
SpeedGuide.net :: TCP Optimizer / Downloads
either should fix that
I'm having slow download speeds. I created my own thread, but I see that this is the thread that actually gets results. I'll post the same thing here, hoping for some help.
I have been experiencing an extreme drop in my download speeds every night around 5pm and it continues until 6am. This happens every single day. I'm currently downloading at 1656 KB/s during the day, I'm able to reach speeds of 100114 KB/s. (On a wired connection).
I worked with a very beginner technician via chat that basically asked me to reset my router so he could login and check some settings and when he finished he basically set it's a problem with my computer. I had to go back in and reconfig my router properly after he was done. It's not my computer, I'm transferring data from my computer to my internal NAS at the same speeds I have always been.
It's seems impossilbe to get a skilled technicain on the phone to assist. I need to get the speeds I pay for or I'll have to start looking for another provider.
I think a majority of people get their wired speeds, and even some extra.
When you're hardwired test at speedtest.verizon.net post those results, and also click on the network diagnostic tool at the bottom of the page and post those results here.
Try to do one for each scenario. one for when it's working well and one for when it's not working well. and if you're familiar with Traceroute, then I would suggest downloading WINMTR
(basically traceroute on steroids) and choose a couple target destinations, and do a similar test, one for when it's working and one for when it's not.. Here's a nice write up on interpreting the results: https://www.linode.com/docs/networking/diagnosing-network-issues-with-mtr#analyzing-mtr-reports
Also if no one has rebooted your main Terminal, sometimes it can be something as simple as that.
Try to reboot the main terminal the next time the problem happens.
Thank you for the help Hubrisnxs.
The speed tests always seem to come back fantastic 83/91. It's when I start to download large files and watch video that speeds drop. I've run tests using the same files during the day and night and there's a huge difference in speed.
Here's the results from the NDT. I actually ran the optimizer and then ran the NDT to make sure I had ideal settings.
I'm curious about the statement "This connection is sender limited 90.84% of the time".ta.
Analysis information:
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 27.20Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 82.02Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_71
------ Web100 Detailed Analysis ------
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 = 43.61 msec; the Packet size = 1460 Bytes; and
No packet loss - but packets arrived out-of-order 0.85% of the time
S2C throughput test: Packet queuing detected: 15.59%
This connection is receiver limited 7.37% of the time.
Increasing the the client's receive buffer (767.0 KB) will improve performance
This connection is sender limited 90.84% of the time.
This connection is network limited 1.79% 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
Current Send Buffer 255 Kbyte
Current Receive Buffer 8 Kbyte
Display Name = Intel(R) Ethernet Connection (2) I218-V MTU = 1500
Display Name = Microsoft ISATAP Adapter MTU = 1280
Display Name = Teredo Tunneling Pseudo-Interface MTU = 1280
Display Name = TAP-Win32 Adapter V9 MTU = 1500
Display Name = Microsoft ISATAP Adapter #2 MTU = 1280
Server 'nyfiosspeed2.west.verizon.net' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Information: Network Middlebox is modifying Window scaling option
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [] but Client says []
After the FIOS Optimization :
The Network Diagnostic Tool results below will be used by our Verizon Technical Support Team to review your computer settings.
Analysis information:
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 40.85Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 11.62Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_71
------ Web100 Detailed Analysis ------
2.4 Gbps OC-48 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 23.82 msec; the Packet size = 1460 Bytes; and
There were 97 packets retransmitted, 677 duplicate acks received, and 755 SACK blocks received
The connection was idle 0 seconds (0%) of the time
S2C throughput test: Packet queuing detected: 63.84%
This connection is sender limited 65.82% of the time.
This connection is network limited 32.98% 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
Current Send Buffer 255 Kbyte
Current Receive Buffer 8 Kbyte
Display Name = Microsoft ISATAP Adapter MTU = 1280
Display Name = Teredo Tunneling Pseudo-Interface MTU = 1280
Display Name = Microsoft ISATAP Adapter #2 MTU = 1280
Display Name = Realtek PCIe GBE Family Controller MTU = 1500
Display Name = Realtek PCIe GBE Family Controller #2 MTU = 1500
Server 'nyfiosspeed2.west.verizon.net' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Information: Network Middlebox is modifying Window scaling option
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.1.153]
After the optimization :
According to Verizon Service Ticket Another Tech Svc. supposed to be come on Jan.16.2015 but nobody showed up!!!!
If Verizon can't or unable to fix this issue why not just say "We are not capable of fixing this issue." I can respect that!!!
Or best question is why Verizon are promising speed that they can't support it? Am I missing something here? Where is Verizon Supervisor?
Did you call them back and ask when they could make another appointment?
Start a new topic or ask questions in the open forum.
