elinvesti8 Posted June 9, 2007 CID Share Posted June 9, 2007 WHAT DOES ALL THIS MEAN. IS IT GOOD OR BAD? WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 1.91Mb/s running 10s inbound test (server to client) . . . . . . 1.21Mb/s ------ Client System Details ------ OS data: Name = Windows XP, Architecture = x86, Version = 5.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_07 ------ Web100 Detailed Analysis ------ 10 Mbps Ethernet 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 = 125.25 msec; the Packet size = 1460 Bytes; and There were 7 packets retransmitted, 162 duplicate acks received, and 136 SACK blocks received The connection stalled 5 times due to packet loss The connection was idle 1.75 seconds (17.5%) of the time This connection is network limited 99.97% 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 Quote Link to comment Share on other sites More sharing options...
mudmanc4 Posted June 9, 2007 CID Share Posted June 9, 2007 Overall I would sat you are doing pretty good ! As for the " network congestion ", at those speeds, my best assumption would be that is the router or firewall breaking down the packets for the internal network, something like this. ( very basic ) Data from application > TCP packets > IP packets > Subnet packets > Link packets then transmitted into physical signal into a series of " pulses " then as recieved vice versa. They all contain : An Application layer Transport Layer Internet Layer Subnet Layer Link Layer Which become the " physical Layer " This requires quite a bit of work from your hardware, therefore at your sppeds , It could be possible that your actual router is the bottleneck. Just my lame ass thoughts, I'm sure there is someone here that knows much better to explain . Quote Link to comment Share on other sites More sharing options...
elinvesti8 Posted June 10, 2007 Author CID Share Posted June 10, 2007 Mudmanc4 thank you for that explanation! Router, hmmmm Quote Link to comment Share on other sites More sharing options...
elinvesti8 Posted June 10, 2007 Author CID Share Posted June 10, 2007 Oh and what about these ping times to Google are they ok? Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and Settingsuser>ping google.com -n 25 Pinging google.com [72.14.207.99] with 32 bytes of data: Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=85ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=89ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=88ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=88ms TTL=236 Reply from 72.14.207.99: bytes=32 time=90ms TTL=236 Reply from 72.14.207.99: bytes=32 time=89ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=89ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=87ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Reply from 72.14.207.99: bytes=32 time=86ms TTL=236 Ping statistics for 72.14.207.99: Packets: Sent = 25, Received = 25, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 85ms, Maximum = 90ms, Average = 87ms Quote Link to comment Share on other sites More sharing options...
Guest kamil234 Posted June 10, 2007 CID Share Posted June 10, 2007 not the best ping but anything under 100ms is acceptable to me. Quote Link to comment Share on other sites More sharing options...
mudmanc4 Posted June 10, 2007 CID Share Posted June 10, 2007 Try to ping " 67.18.179.85 " Which is testmy.net Post results. Quote Link to comment Share on other sites More sharing options...
elinvesti8 Posted June 10, 2007 Author CID Share Posted June 10, 2007 Ok here it is! Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and Settingsuser>ping 67.18.179.85 Pinging 67.18.179.85 with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=46ms TTL=45 Reply from 67.18.179.85: bytes=32 time=47ms TTL=45 Reply from 67.18.179.85: bytes=32 time=47ms TTL=45 Reply from 67.18.179.85: bytes=32 time=46ms TTL=45 Ping statistics for 67.18.179.85: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 47ms, Average = 46ms Quote Link to comment Share on other sites More sharing options...
mudmanc4 Posted June 10, 2007 CID Share Posted June 10, 2007 Those are good ping times to TMN, If your gonna get much more out of your connection, you may want to upgrade your nic to a bit more expensive one , but even then , what are you gonna do w/ the slight speed increase ? lol look here http://www.intel.com/network/connectivity/wizard/ Quote Link to comment Share on other sites More sharing options...
elinvesti8 Posted June 10, 2007 Author CID Share Posted June 10, 2007 mudmanc4 Thanks again for checking out my WEB100 and Ping stuff. I will be happy with what I got. Thanks again...Oh and everyone else who chimed in, Thanks.. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.