<div dir="ltr">Some other possibilities: <div><ol><li>Clock is wrong (use a master PC to sync all clocks).</li><li>One computer has faulty or misconfigured firewall or anti-spyware software that blocks some packets<br></li><li>One computer is running different version of Win-Test</li><li>wtDxTelnet is out of date</li><li>SETUP, Network Advanced Protocols, click Default button to reset</li></ol><div>More info about WiFi problems here:</div><div><br></div><div><a href="http://lists.f5mzn.org/pipermail/support/2013-April/082829.html" target="_blank">http://lists.f5mzn.org/pipermail/support/2013-April/082829.html</a><br><div class="gmail_extra"><br></div><div class="gmail_extra">Please share what you discover.</div><div class="gmail_extra"><br clear="all"><div><div>73,<div>Bob, N6TV</div></div></div>
<br><div class="gmail_quote">On Tue, May 12, 2015 at 3:05 PM, Bob Wilson, N6TV <span dir="ltr"><<a href="mailto:n6tv@arrl.net" target="_blank">n6tv@arrl.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">In addition to having the same broadcast address, all computers must be on the same subnet. That means if some of your computers have a local wired IP address of 192.168.0.<i>xx</i> and others have a WiFi address of 192.168.1.<i>xx</i>, (third number in address is different), some (or all) of the broadcast packets won't make it from one to the other, no matter what you enter as the broadcast address. Some routers are configured to assign separate subnets for WiFi and Wired. Some routers are configured to block WiFi packets from reaching Ethernet ports. Check the security settings on the router.<div><br></div><div>Another possibility is that you're having a lot of WiFi collisions or dropped packets due to interference (use 5 GHz WiFi instead of 2.4 GHz WiFi if available). See</div><div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><a href="http://www.pcworld.com/article/227973/six_things_that_block_your_wifi_and_how_to_fix_them.html" target="_blank">http://www.pcworld.com/article/227973/six_things_that_block_your_wifi_and_how_to_fix_them.html</a></div></blockquote><div><br></div><div>Finally make sure that you don't have two Ethernet adapters, or one WiFi, one Ethernet enabled on the same computer at the same time, as broadcast packets could be generated by both at the same time, perhaps colliding. 100% wired is best. </div><div><br></div><div>Disable WiFi via the hardware switch located on the side of many modern notebooks if you can use 100% wired.</div><div><br></div><div class="gmail_extra"><div><div>73,<div>Bob, N6TV</div></div></div>
<br><div class="gmail_quote"><div><div>On Tue, May 12, 2015 at 2:47 PM, Don Beattie <span dir="ltr"><<a href="mailto:g3ozf@btinternet.com" target="_blank">g3ozf@btinternet.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div><div style="color:rgb(0,0,0);font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:10px;background-color:rgb(255,255,255)"><div><font size="2">I wonder if anyone can suggest where I might look to fix the
following issue.<u></u><u></u></font></div><div><u></u><font size="2"> </font><u></u></div><div><font size="2">I have upgraded to WT 4.16 and most everything is fine. I
have three computers on a little network for the M2 entry we will do in CQWPX
at G5W. Two are connected to the FT5000’s, the third is connected to the web
via wifi, and simply runs WT-DX Telnet. (I have Telnet on a separate computer
in CW contests to avoid any issue of slowing the CW sending from the computer).<u></u><u></u></font></div><div><u></u><font size="2"> </font><u></u></div><div><font size="2">All the broadcast addresses are properly set, as are the
station names, etc etc. Logging works fine, as does gab. The problem is the
band-map. <u></u><u></u></font></div><div><u></u><font size="2"> </font><u></u></div><div><font size="2">On one of the workstations, the band map works fine –
everything that appears on WTDX Telnet appears in the band map. On the second
station, it’s not so good. I get about 50% of the spots appearing in the band
map. I’ve checked the band-map settings (properties and display) and they are
identical on both computers. It suggests that it is a network problem, but
everything is OK with the network adaptor settings. I have checked to see what
registers on the DX cluster window in WT at each station, and the same
callsigns are missing from the one station as are missing in the band map,
whereas the other workstation call list aligns exactly with WTDX Telnet
callsign list on the telnet server machine. So two machines are working
perfectly together, whilst the third seems to take only 50% of the spots.<u></u><u></u></font></div><div><u></u><font size="2"> </font><u></u></div><div><font size="2">Has anyone seen this problem before and can point me in the
right direction?<u></u><u></u></font></div><div><u></u><font size="2"> </font><u></u></div><div><font size="2">73<u></u><u></u></font></div><div><u></u><font size="2"> </font><u></u></div><div>
</div><div dir="ltr"><b><font size="2">Don, G3BJ<u></u><u></u></font></b></div><div><br></div></div></div><br></div></div>_______________________________________________<br>
Support mailing list<br>
<a href="mailto:support@win-test.com" target="_blank">support@win-test.com</a><br>
<a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div></div>