Skip to Content.
Sympa Menu

ndt-users - Re: causes of Protocol error!

Subject: ndt-users list created

List archive

Re: causes of Protocol error!


Chronological Thread 
  • From: Richard Carlson <>
  • To: ,
  • Subject: Re: causes of Protocol error!
  • Date: Wed, 27 Feb 2008 08:48:24 -0500

Hi Larry;

I'm the developer of the NDT system but I don't have physical access to the ANL server (miranda.ctd.anl.gov now renamed ndt.anl.gov). The NDT server and Java applet client have a simple communications protocol that maintains the status of each test. The "Protocol error!" message indicates that the client and server have slipped out of sync and they aren't communicating properly. Are you saying that this client successfully runs the Middlebox and SFW tests, but then fails on the C2S test?

If so, then my first action would be to look at the client PC's TCP window configuration settings. It is possible that the TCP send window is too large and the client is queuing up a lot of data. In this case the client would still try and send data while the server is attempting to move on to the S2C test. The result is the "Protocol error!" failure message.

If you point your client to the Internet2 public NDT server http://ndt.internet2.edu:7123 I can look at the test results in more detail.

Rich
At 10:00 PM 2/26/2008,

wrote:
Hello,

We have a customer who is a EE running Miranda (which we recommend) from his 802.11b connection to our wireless (RURAL) network who is experiencing the error below the sig.

A search using Google wasn't very productive.

What are the likely causes?

Kind regards/ldv

Larry Vaden
Internet Texoma, Inc.
ASN 4963 Since 1995

running 10s outbound test (client-to-server [C2S]) . . . . . Protocol error!
C2S throughput test FAILED!
Protocol error!

------------------------------------



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



Archive powered by MHonArc 2.6.16.

Top of Page