| |
N9SEO > BPQ 23.12.24 18:54l 101 Lines 3565 Bytes #299 (0) @ WW
BID : 28647_N9SEO
Subj: Re: Connection isn't recognized by QtTermTCP
Path: IW8PGT<IZ3LSV<DB0ERF<DK0WUE<DK0WUE<VK5RSV<VK5LEX<VE3KPG<VE3CGR<GB7YEW<
KE0GB<K0WAV<N9SEO
Sent: 241223/1752Z 28647@N9SEO.#NAR.AR.USA.NOAM LinBPQ6.0.24
On Mon, 23 Dec 24 17:29:00 Z
WG3K wrote:
> R:241223/1730Z 23855@WW6Q.#NEIN.IN.USA.NOAM LinBPQ6.0.24
> R:241223/1730Z 55190@KA1VSC.#CCT.CT.USA.NOAM LinBPQ6.0.24
> R:241223/1729Z 11246@WG3K.#SMD.MD.USA.NOAM LinBPQ6.0.24
>=20
> Good day all,
> 'm running QtTermTCP64 version 0.0.0.77 Beta 1 and have it connected
> to my Kenwood D-74 in KISS mode. When I try to connect to my home
> node I see the connection happen but QtTermTCP doesn't ever recognize
> it as connected. Anyone have any ideas?
>=20
>=20
> 17:00:46T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:00:54T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:00:56R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:00:56R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:01:00R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:00T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:00R CBEACH>WG3K,K3CAL-1* <I C P R0 S0>
> Welcome to WG3K Node in Chesapeake Beach, Maryland. Use =E2=80=9C?=E2=80=
=9D for Help
> menu. CBBBS:WG3K}
> 17:01:00T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:01R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:01T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:02T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:03R WG3K>CBEACH,K3CAL-1* <DM R F>
> 17:01:03R WG3K>CBEACH,K3CAL-1* <DM R F>
> 17:01:03R WG3K>CBEACH,K3CAL-1* <DM R F>
> 17:01:03R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:01:07R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:07T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:10T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:11R WG3K>CBEACH,K3CAL-1* <DM R F>
> 17:01:11R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:01:15R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:15T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:15R CBEACH>WG3K,K3CAL-1* <I C P R0 S0>
> Welcome to WG3K Node in Chesapeake Beach, Maryland. Use =E2=80=9C?=E2=80=
=9D for Help
> menu. CBBBS:WG3K}
> 17:01:15T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:18T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:26T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:28R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:01:31R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:31T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:32R CBEACH>WG3K,K3CAL-1* <I C P R0 S0>
> Welcome to WG3K Node in Chesapeake Beach, Maryland. Use =E2=80=9C?=E2=80=
=9D for Help
> menu. CBBBS:WG3K}
> 17:01:32T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:34T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:42T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:46R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:01:47R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:01:49R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:49T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:49R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:01:49T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:01:50T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:01:58T WG3K>CBEACH,K3CAL-1 <SABM C P>
> 17:02:01R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:02:01R WG3K>CBEACH,K3CAL-1* <SABM C P>
> 17:02:04R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:02:04T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:02:05R CBEACH>WG3K,K3CAL-1* <UA R F>
> 17:02:05T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:02:06T WG3K>CBEACH,K3CAL-1 <DISC C P>
> 17:02:08R WG3K>CBEACH,K3CAL-1* <DM R F>
> 17:02:08R WG3K>CBEACH,K3CAL-1* <DM R F>
> 17:02:09R WG3K>CBEACH,K3CAL-1* <DISC C P>
> 17:02:11R CBEACH>WG3K,K3CAL-1* <DM R F>
> 17:02:11T WG3K>CBEACH,K3CAL-1 <DM R F>
> 17:02:13R WG3K>CBEACH,K3CAL-1* <DM R F>
>=20
> 73,
> Eric WG3K
>=20
>=20
Eric,
Are you using your CALL (no SSID) in more than one place?
My guess is that you are and that there are two things on the same
network medium answering to that call. Easy fix is to put on your
qttermtcp a unique SSID not used elsewhere.=20
I could be wrong but when I've seen this happen to me it was becuase I
forgot about something else using that call.
Hope that helps...
73 Kayne
Read previous mail | Read next mail
| |
