[WT-support] Network Error

Bob Wilson, N6TV n6tv at arrl.net
Wed Dec 18 07:09:01 CET 2013


I just remembered another common cause of this "Network received bad
checksum" error:

   1. In the logging window, type SETUP [Enter]
   2. In the Interface Configuration screen, look at all the COM ports that
   have a check mark next to them
   3. If any of the checked COM ports are marked "Network", uncheck those
   COM ports and the problem should disappear

I assume you are using Ethernet or WiFi networking, not legacy serial port
networking, so none of the checked COM ports should be set to "Network".
 Unfortunately, Win-Test sets every COM port to "Network" by default.
 Maybe "Other interface" would be a much better.

Bob, N6TV

On Tue, Dec 17, 2013 at 9:28 PM, Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> Geoff,
> You posted this same question five days ago.  I replied already.  Please
> read:
> http://lists.f5mzn.org/pipermail/support/2013-December/083446.html
> 73,
> Bob, N6TV
> On Tue, Dec 17, 2013 at 7:09 PM, Geoffrey Burns <ne3k at comcast.net> wrote:
>> Folks-
>> Yaesu FT-1000MP MKV Field, US Interface Navigator, home brew computer.
>> I have been getting a 'Network recieved bad checksum' error lately.
>> Win-Test used to work fine, just since CQWW this has been a problem.
>> Any ideas? It does it whether or not I am using the DX Cluster spots or
>> not.
>> Geoff, NE3K
>> Sent from my iPhone
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20131217/e663d609/attachment.html>

More information about the Support mailing list