Has anyone used the Verizon network diagnostic tool before? Found here: http://my.verizon.com/services/speedtest/defaultndt.aspx
If so what were your results? I'm trying to see what a "healthy" connections results look like. If anyone from the VA metro DC or VA area could run this and show me the results I would appreciate it.
Below are mine:
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 125.93Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 125.09Mb/s
------ Client System Details ------
OS data: Name = Windows 10, Architecture = x86, Version = 10.0
Java data: Vendor = Oracle Corporation, Version = 1.8.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 = 12.9 msec; the Packet size = 1460 Bytes; and
There were 145 packets retransmitted, 3126 duplicate acks received, and 3236 SACK blocks received
The connection was idle 0 seconds (0%) of the time
S2C throughput test: Packet queuing detected: 12.66%
This connection is receiver limited 2.18% of the time.
Increasing the the client's receive buffer (470.0 KB) will improve performance
This connection is sender limited 89.17% of the time.
This connection is network limited 8.64% 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 64 Kbyte
Current Receive Buffer 64 Kbyte
Display Name = Teredo Tunneling Pseudo-Interface MTU = 1280
Display Name = Intel(R) 82579V Gigabit Network Connection MTU = 1500
Display Name = Microsoft ISATAP Adapter MTU = 1280
Server 'resfiosspeed2.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 [XXX.XXX.XXX.XXX] but Client says [192.168.1.2]
↧