Subject: | |
From: | |
Reply To: | |
Date: | Mon, 16 Jun 2003 00:16:26 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Steve,
Have you got record and playback audio levels set? If so try connecting to
node 9999. This is a test node which will echo back your transmissions.
Lynn
[log in to unmask]
----- Original Message -----
From: "Gary Jackson" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Sunday, June 15, 2003 11:59 PM
Subject: Re: EchoLink Frustrations
> Well Steve,
>
> I have the same configuration here. I'm not sure if mine is working
> correctly right now. Is anybody still on the air? It is around 11:00
> central.
>
> Gary
>
> Gary Jackson kk5ge
> Phone: 409-962-0353
> [log in to unmask]
> ----- Original Message -----
> From: "Steve" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Sunday, June 15, 2003 8:46 PM
> Subject: EchoLink Frustrations
>
>
> Ok, looking for any and all brilliant ideas.
>
> Running Windows XP Home Edition with cable modem and a D-Link router. I
> have supposedly listed Echolink as a special application in my router;
with
> ports 5198 and 5199 set as UDP and port 5200 set as TCP. I have Win XP
> firewall disabled, and I've disabled my Norton Firewall.
>
> Yet, when I attempt to connect to a station through echolink by
highlighting
> the station with my cursor and pressing alt-c, I get a connection time-out
> after thirty seconds. Looked at the help section in Echolink, but other
> than the port settings, I'm clueless. Any suggestions?
>
>
> Steve Pollo
> [log in to unmask]
> Lansing, MI
|
|
|