Skip to Content.
Sympa Menu

ndt-users - Re: Protocol Error

Subject: ndt-users list created

List archive

Re: Protocol Error


Chronological Thread 
  • From: Richard Machida <>
  • To: "" <>
  • Subject: Re: Protocol Error
  • Date: Mon, 19 Nov 2012 07:12:52 -0900

Jason,
Since I had to leave the site on Saturday evening, I threw the live CD back in and running from that now. That particular system has been running the CD version for years and I thought that the drive may be wearing out by now.

I won't get back to the site for a couple of months and didn't want to leave a broken system. 

Maybe I grabbed the wrong CD to do the install. 

Thank you for replying. 

Richard

--
Richard Machida
University of Alaska Fairbanks
Office of Information Technology
v: 907.474.7102     m: 907.460.6312

On Nov 19, 2012, at 3:27 AM, Jason Zurawski <> wrote:

Hey Richard;

Its extremely odd to see the 'v5.5.4a' in your output - that would be indicative of a software release that is about 4 years old and wouldn't be in use on v3.2.2 of the pSPT.  I ran a test to your server from home and got the attached screen shot - things appeared to work for me which makes the error even more strange (and I did see the 'correct' version string in the process).  

Thanks;

-jason

<Screen Shot 2012-11-19 at 7.14.47 AM.png>

On Nov 17, 2012, at 6:52 PM, Richard Machida <> wrote:

I just installed 3.2.2 and when I try and run NDT, I get:

TCP/Web100 Network Diagnostic Tool v5.5.4a
click START to begin

** Starting test 1 of 1 **
Connected to: 199.165.125.40 -- Using IPv4 address
Protocol error!

click START to re-test

I re-installed the host using a net-install after turning up IPv6 on the network.

On another workstation, I just get "Initializing" and nothing else.

The only error in the logs are:
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs.class
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs.properties
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs.properties
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs_en.class
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs_en.properties
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs_en.properties
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /Tcpbw100_msgs_en_US.class
[Sat Nov 17 14:25:06 2012] [error] [client 199.165.125.177] Permission denied: path not allowed: /favicon.ico
[Sat Nov 17 14:26:00 2012] [error] [client 199.165.125.179] Permission denied: path not allowed: /Tcpbw100.jar.pack.gz
[Sat Nov 17 14:26:01 2012] [error] [client 199.165.125.179] Permission denied: path not allowed: /favicon.ico

Where the .177 host is getting just "Initializing" and the .179 host is getting the "Protocol Error".

Both of these hosts are able to access another dual stack host running the same software back in my office.

Thank you
Richard

--
Richard Machida
Office of Information Technology, University of Alaska
101A Butrovich Building, PO Box 755320, Fairbanks, AK 99775-5320
v:907.474.7102 m:907.460.6312 f:907.450.8381 PGP Key ID: 0xA0C92C28 CCNP CCAI



Archive powered by MHonArc 2.6.16.

Top of Page