ndt-users list created

[Richard Carlson <>]

Lize;

Try updating the server to v3.6.3.  There are some alarm() function 
calls in the v3.6.1 server code that can cause this type of behavior.

Rich


On 7/12/2010 3:12 AM, Lize wrote:
> today connect to internet with 3G adapter to test ndt server
> but i got the following messages
>
> TCP/Web100 Network Diagnostic Tool v3.6.1
> click START to begin
>
> =========================================================
> ** Starting test 1 of 1 **
> Connecting to '140.113.87.235' [/140.113.87.235] to run test
> Connected to: 140.113.87.235  --  Using IPv4 address
> Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done
> checking for firewalls . . . . . . . . . . . . . . . . . . .  Done
> running 10s outbound test (client-to-server [C2S]) . . . . . Protocol error!
> Expected test data, got:     instead
> C2S throughput test FAILED!
> running 10s inbound test (server-to-client [S2C]) . . . . . . Protocol error!
> Expected prepare, got:      instead
> S2C throughput test FAILED!
> Protocol error!  Expected test results, got:      instead
> =======================================================
>
> it could work if i use wifi or wireline network
> but while i using 3G to test the server, it failed
> is it the problem of NDT server?

--
Richard Carlson
DOE ASCR  --  SC-21.1 / GTN
1000 Independence Ave. SW
Washington, DC   20585
P: (301) 903-9486