- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
so ive seen posts about people not seeing the speeds that there paying for. ive tried the some of the solutions and ive increased my speeds quite a bit but there still nowhere near what im paying for. my computer is http://us.toshiba.com/computers/laptops/satellite/C850/C855-S5239/ its nothing special but it is capable of wireless N speeds.so i figured hey my computer may not be able to handle the full speeds to i purchased this http://www.newegg.com/Product/Product.aspx?Item=N82E16833320089, between adjusting my router(mi424wr rev.i) settings WAP2 and changing it to wirless n performance mode ive gotten my speeds from 41/40 to 70/61 . while this is great ..... its not what im paying for.i plan on getting another router and bridging it becasue this one pretty much seems to suck .but until then i could use some help with my setup now
thanks
this is my speed test results
Analysis information:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 79.45Mb/s
running 10s inbound test (server to client) . . . . . . 59.89Mb/s
------ Client System Details ------
OS data: Name = Windows 8, Architecture = x86, Version = 6.2
Java data: Vendor = Oracle Corporation, Version = 1.7.0_17
------ Web100 Detailed Analysis ------
Client Receive Window detected at 1439488 bytes.
100 Mbps FastEthernet link found.
Link set to Half 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 = 40.61 msec; the Packet size = 1460 Bytes; and
There were 304 packets retransmitted, 2738 duplicate acks received, and 3036 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 2.37% of the time.
This connection is sender limited 74.77% of the time.
This connection is network limited 22.86% 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
Packet size is preserved End-to-End
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.9]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
First, you need to test with a wired connection. Make sure you are getting the speeds you pay for from Verizon before you make sure they are translating to your wireless network.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
also make sure to test at http://speedtest.verizon.net/fios300