ndt-users - Re: NDT "Protocol error"
Subject: ndt-users list created
List archive
- From: Richard Carlson <>
- To: Matt Crawford <>,
- Cc: Vladimir Bravov <>
- Subject: Re: NDT "Protocol error"
- Date: Fri, 15 Jun 2007 13:09:12 -0400
Vladimir;
Matt Crawford and I looked at this some more and we see that the server is failing at various points. Looking at the code it may be that there is a problem with the access to the web100 connection information. This may be due to an interaction between the kernel and the userland library.
I'll dig into this some more.
Rich
At 02:01 PM 6/14/2007, Matt Crawford wrote:
We've updated NDT and now see "protocol error" messages. Does the
following fit a known syndrome?
TCP/Web100 Network Diagnostic Tool v5.4.12
click START to begin
Connected to: shasta.fnal.gov -- Using IPv4 address
Another client is currently being served, your test will begin within
45 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 11.51Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . .
Protocol error!
click START to re-test
------------------------------------
Richard A. Carlson e-mail:
Network Engineer phone: (734) 352-7043
Internet2 fax: (734) 913-4255
1000 Oakbrook Dr; Suite 300
Ann Arbor, MI 48104
- NDT "Protocol error", Matt Crawford, 06/14/2007
- Re: NDT "Protocol error", Richard Carlson, 06/15/2007
- <Possible follow-up(s)>
- RE: NDT "Protocol error", Clint Simmons, 06/14/2007
Archive powered by MHonArc 2.6.16.