×

Switch Account

153/35...... i could us some help actually achieving those speeds

Reply
Highlighted
Contributor
Contributor
Posts: 1
Registered: ‎03-08-2013

153/35...... i could us some help actually achieving those speeds

Message 1 of 3
(699 Views)

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

 

Broadband Speed Test


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]

2 REPLIES 2
Highlighted
Platinum Contributor II Platinum Contributor II
Platinum Contributor II
Posts: 3,149
Registered: ‎09-15-2009

Re: 153/35...... i could us some help actually achieving those speeds

Message 2 of 3
(629 Views)

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.

--
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

"All knowledge is worth having."
Highlighted
Platinum Contributor III
Platinum Contributor III
Posts: 5,881
Registered: ‎07-22-2009

Re: 153/35...... i could us some help actually achieving those speeds

Message 3 of 3
(613 Views)

also make sure to test at http://speedtest.verizon.net/fios300

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Covid19


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.