Lynn:

Thank you so very much for your response and your offer to help. URIKA!  The
problem has been solved; how, by unplugging my router for fifteen seconds or
so then bringing it back on line; and you would *not believe how many times
I checked, rechecked and experimented with router settings!  Honestly, it
reminds me of a story that's told about a computer going haywire on one of
the Apollo missions, and after protracted discussions and analysis by all
the technicians on the ground, the final word was: "just hit it", and that
did, in fact, fix the problem.

Again, Lynn, thanks for your offer to  help.  By the way, the echolink
troubleshooter program can be found under the "support and FAQs" link.

Best 73's!

John
KW4U
Echolink node number 1789 (now capable, <smile>!)

----- Original Message -----
From: "Lynn Roberts N8LXK" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, January 29, 2004 11:37 AM
Subject: Re: Echolink Troubleshooter


> John,
> Have you tried linking to node 9999? It was a test node, where you could
> check your audio. If you will e-mail me your phone number off list to my
> n8lxk at earthlink dot net address, I might be able to help you. Also
> are you using echolink via dial up or cable or dsl?
>
> Lynn
> [log in to unmask]
>
>
> -----Original Message-----
> From: Blind-Hams For blind ham radio operators
> [mailto:[log in to unmask]] On Behalf Of John McCann
> Sent: Thursday, January 29, 2004 6:53 AM
> To: [log in to unmask]
> Subject: Echolink Troubleshooter
>
>
> Hi folks:
>
> Several months back, I did use the echolink troubleshooter; got a nice
> report; everything was fine. Now, everything is not fine; I can't
> connect for some reason (though I didn't mess with any of the port
> settings.)
>
> I don't remember how I accessed the troubleshooter. Does anyone here
> know where it is?
>
> Thanks73's,
> John
> KW4U
> Echolink node number: 1789
>
>