[WriteLog] Networking issue

[Ed Muns]

I setup some networked WriteLog PCs using a mix of OSs and confirm what KK4A
and W2SC are reporting.  I cannot get the XP machine to act as a common
Telnet machine where the other networked machines do a Packet connect to it
via LAN.  The Win7 and Win8 machines work fine in the role of common Telnet
provider for the WriteLog network.

When a PC attempts a Packet connect via LAN to the XP machine running
Telnet, an error box titled "Wlogpkt32" reports "Failed to connect to remote
node."

All machines perform all other WriteLog network functions both directions
between each other.

Ed W0YK

_____________________________________________________________________

-----Original Message-----
From: WriteLog [mailto:writelog-bounces at contesting.com] On Behalf Of
john at kk9a.com
Sent: 05 November, 2015 18:31
To: writelog at contesting.com
Subject: Re: [WriteLog] Networking issue

I had a similar issue networking the packet cluster when setting up for the
2015 WPX RTTY contest in February. Ed and I exchanged a number of emails and
I carefully followed his instructions but I had no success. Both PCs use XP
Pro and otherwise are networked perfectly. I have not operated assisted from
my station since then and have not made an effort to resolve the problem.
Please keep us informed Tom.

John KK9A


Subject:	Re: [WriteLog] Networking issue
From:	"Ed Muns" <ed at w0yk.com>
Reply-to:	ed at w0yk.com
Date:	Thu, 5 Nov 2015 10:08:36 -0800
List-post:	<writelog at contesting.com">mailto:writelog at contesting.com>
I also use the VE7CC ccuser application when I setup for Packet access on
WriteLog (RTTY) or Win-Test (CW and SSB).  The user interface for spot
filtering, node control, propagation updates, etc is very powerful.

However, it is an incremental layer of complexity that is unlikely to solve
the basic problem of Packet connection via LAN to a single Telnet computer
on the WriteLog network.  All ccuser does is enrich the Telnet connection.
It will not solve the original problem of some PCs not getting Packet via
LAN to the PC with the Telnet connection.

Assuming WriteLog networking is configured as I outlined in my prior post,
I've never had the problem Tom describes.  However, I always have the Telnet
connection on the "Master" PC.  I don't know for sure that that is
necessary, but the LAN connection through the Telnet PC always works in that
configuration.

So, here is how I would set up Tom's 3 PCs ...

1.  Decide which PC I want the Telnet connection on and label it the
"Master" for the WriteLog networking setup.

2.  Register each PC to the network (Tools/Register to accept network
connections).

3.  On each of the non-Master PCs, link them to the Master PC (Tools/Link to
Network).  Do not link the Master PC explicitly.  It becomes linked to the
others by virtue the other PCs linking to it.

4.  Setup the Telnet connection on the "Master" PC.

5.  Setup Packet via LAN on the other two PCs.

I have had exactly the same problem Tom describes with LAN Packet access not
working.  I solved it with the procedure above.

Still, there may be an additional issue, perhaps at the Windows level
(nothing to do with WriteLog), particularly since each PC has a different
Windows version.

Ed W0YK

_______________________________________________
WriteLog mailing list
WriteLog at contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/