nellie2 Posted March 12, 2005 Report Share Posted March 12, 2005 This is a free service that uses a Java applet running from your browser to quickly test the reliability and status of your computer’s network connection. It works by sending test data to and from your computer and the site's server and analyzing the results. It's a relatively simple test but it allows you to diagnose a range of problems from faulty cables and duplex mismatch to wrongly specified TCP parameters. I ran a test.... here are my results. Worth popping in your favourites I think!Link Quote Link to comment Share on other sites More sharing options...
scuzzman Posted March 12, 2005 Report Share Posted March 12, 2005 Wow - this thing is very thorough!WEB100 Enabled Statistics:Checking for Middleboxes . . . . . . . . . . . . . . . . . . Donerunning 10s outbound test (client to server) . . . . . 381.53Kb/srunning 10s inbound test (server to client) . . . . . . 3.57Mb/s ------ Client System Details ------OS data: Name = Linux, Architecture = i386, Version = 2.6.9Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0 ------ Web100 Detailed Analysis ------45 Mbps T3/DS3 link found.Link set to Full Duplex modeNo network congestion discovered.Good network cable(s) foundNormal duplex operation found.Web100 reports the Round trip time = 124.12 msec; the Packet size = 1368 Bytes; and No packet loss - but packets arrived out-of-order 18.86% of the timeThis connection is receiver limited 87.14% of the time. Increasing the current receive buffer (64.0 KB) will improve performanceThis connection is network limited 12.83% of the time. Contact your local network admin and report excessive packet reordering Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ONRFC 896 Nagle Algorithm: ONRFC 3168 Explicit Congestion Notification: OFFRFC 1323 Time Stamping: ONRFC 1323 Window Scaling: ONInformation: Network Middlebox is modifying MSS variableServer IP addresses are preserved End-to-EndClient IP addresses are preserved End-to-EndThanks Nel! :D Quote Link to comment Share on other sites More sharing options...
catgate Posted March 12, 2005 Report Share Posted March 12, 2005 Nell,It certainly is an interesting thing. It confirmed what I knew....my machine is very pedestrian, but it also told me that my receiving buffer was not big enough. I then realised there were only two things stopping me trying to improve matters. 1) What the ***** is my receiving buffer and 2) how do I find it and alter it? Under these circumstances I find it reassuring that it was you who pointed it out, because you are likely to know the answers to my questions. Quote Link to comment Share on other sites More sharing options...
mark2 Posted March 12, 2005 Report Share Posted March 12, 2005 You might like to look at this catgate it may help a little.alsoanother tester here but they do provide hints to help at the end Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted March 13, 2005 Report Share Posted March 13, 2005 Very cool Nel! Thanks for the link! I'm going to pin it. Quote Link to comment Share on other sites More sharing options...
deuces wild Posted March 13, 2005 Report Share Posted March 13, 2005 So what does this mean?WEB100 Enabled Statistics:Checking for Middleboxes . . . . . . . . . . . . . . . . . . Donerunning 10s outbound test (client to server) . . . . . 368.94Kb/srunning 10s inbound test (server to client) . . . . . . 4.21Mb/s ------ Client System Details ------OS data: Name = Windows XP, Architecture = x86, Version = 5.1Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_01 ------ Web100 Detailed Analysis ------Cable modem/DSL/T1 link found.Link set to Half Duplex modeNo network congestion discovered.Good network cable(s) foundNormal duplex operation found.Web100 reports the Round trip time = 124.24 msec; the Packet size = 1380 Bytes; and No packet loss was observed.This connection is receiver limited 97.07% of the time.This connection is network limited 2.90% of the time. Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ONRFC 896 Nagle Algorithm: ONRFC 3168 Explicit Congestion Notification: OFFRFC 1323 Time Stamping: OFFRFC 1323 Window Scaling: ONInformation: Network Middlebox is modifying MSS variableServer IP addresses are preserved End-to-EndInformation: Network Address Translation (NAT) box is modifying the Client's IP address[edited by homecomputeraid]Server says [15.31.21.70] but Client says [192.168.1.104]Doh! Quote Link to comment Share on other sites More sharing options...
nellie2 Posted March 13, 2005 Author Report Share Posted March 13, 2005 Sorry guys... I just found the site and thought you lot might find it interesting. I was hoping someone else could come up with the explanations!! :blush: Quote Link to comment Share on other sites More sharing options...
Boris Posted March 13, 2005 Report Share Posted March 13, 2005 I've tried this about 30 times since Nel posted it - but every time I get exactly the same message !TCP/Web100 Network Diagnostic Tool v5.3.3aclick START to beginChecking for Middleboxes . . . . . . . . . . . . . . . . . . Donerunning 10s outbound test (client to server) . . . . . Server busy: Please wait 30 seconds for previous test to finishclick START to re-testOther than click START - what else can you do ? Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted March 13, 2005 Report Share Posted March 13, 2005 Boris,It worked fine for me several times. Maybe you were trying at a busy time of day for their server?Here's what some of it means:WEB100 Enabled Statistics:Checking for Middleboxes . . . . . . . . . . . . . . . . . . Donerunning 10s outbound test (client to server) . . . . . 368.94Kb/srunning 10s inbound test (server to client) . . . . . . 4.21Mb/sTests your speed to upload and download data. The upload speed for Cable is usually significantly slower than download speed, but home users are much more interested in downloading things anyway. In the above quote, the upload speed was 368.94 Kilobits/Second. The download speed was 4.21 Megabits/Second. Pretty good download speed.------ Client System Details ------OS data: Name = Windows XP, Architecture = x86, Version = 5.1Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_01Just some stuff about your Operating System and Java version.------ Web100 Detailed Analysis ------Cable modem/DSL/T1 link found.Link set to Half Duplex modeNo network congestion discovered.Good network cable(s) foundNormal duplex operation found.Some information about your connection type. Half duplex means communication only occurs in one direction at a time. The computer is either sending or receiving data. Full duplex would mean that it can send and receive at the same time.Web100 reports the Round trip time = 124.24 msec; the Packet size = 1380 Bytes; and No packet loss was observed.This connection is receiver limited 97.07% of the time.This connection is network limited 2.90% of the time.Round trip time is not that meaningful unless there's huge variation in the time in milliseconds. No packet loss is significant because a network with problems will most likely experience packet loss. I believe the receiver limited and network limited indicate where the software believes some "throttling" of the network is taking place. ISP's will limit bandwidth. Your speeds could also be slower because the server at the far end can is only providing a certain amount of bandwidth per customer, or because it's overloaded.Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ONRFC 896 Nagle Algorithm: ONRFC 3168 Explicit Congestion Notification: OFFRFC 1323 Time Stamping: OFFRFC 1323 Window Scaling: ONInformation: Network Middlebox is modifying MSS variableServer IP addresses are preserved End-to-EndInformation: Network Address Translation (NAT) box is modifying the Client's IP addressServer says [15.31.21.70] but Client says [192.168.1.104]RFC's are Requests for Comment: see RFC 2018 for an example. RFC's are how standards are requested, worked through, and eventually implemented for Networking Protocol's. The only significant part for most home users is Network Address Translation. This probably means that the home user has a router that is 'translating' an internal IP (192.168.1.104 in this case) to a valid Internet IP (24.131.211.78). Some routers say in their documentation that NAT will act as a firewall. Remember, this is NOT true! A true firewall will do Stateful Packet Inspection along with NAT. NAT does help a little bit, in that the outside world can't directly 'see' the inside network. Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted March 13, 2005 Report Share Posted March 13, 2005 Deuces Wild,I modified your post to alter your Internet IP Address. It is my opinion that posting your internal network scheme is relatively safe, especially if you use the very popular 192.168.1.0 255.255.255.0 network, but if you couple that with your valid Internet IP, you're providing potential attackers with too much information. 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.