<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;font-size:13px"><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr">In case it is of help to others, I have solved the problem reported below in my earlier mail. </div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr"><br></div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr">Bob, N6TV offered some words of help and confirmed that I had looked at the obvious issues. So I reinstalled the TCP/IP network stack (see <a href="http://mikedixson.com/2015/01/reinstalling-tcpip-network-stack-windows-7/" id="yui_3_16_0_1_1431514167921_3383">http://mikedixson.com/2015/01/reinstalling-tcpip-network-stack-windows-7/</a> )</div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr">and after resetting the network adaptor TCP/IP back to the ones needed locally, and authorising WT in the firewall approved list, everything started to work. I suspect some legacy network setting had not been properly overwritten.</div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr"><br></div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr">Thanks to Bob, and now I can get on with preparing for CQWPX.</div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr"><br></div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr">73</div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr"><br></div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr">Don, G3BJ / G5W</div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr"><br></div><div class="" style="" id="yui_3_16_0_1_1431514167921_3514"><o:p class="" style=""> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3516"><a name="_MailOriginal" class="" style="" href=""><b class="" style=""><span lang="EN-US" class="" style="">From:</span></b></a><span lang="EN-US" class="" style="" id="yui_3_16_0_1_1431514167921_3515"> Don Beattie [mailto:don@g3bj.com] <br class="" style="">
<b class="" style="">Sent:</b> 12 May 2015 12:51<br class="" style="">
<b class="" style="">To:</b> 'support@win-test.com'<br class="" style="">
<b class="" style="" id="yui_3_16_0_1_1431514167921_3632">Subject:</b> NETWORK/BAND-MAP ISSUE<o:p class="" style=""></o:p></span></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3520"><o:p class="" style=""> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3517">I wonder if anyone
can suggest where I might look to fix the following issue.<o:p class="" style=""></o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3519"><o:p class="" style=""> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3518">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).<o:p class="" style=""></o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3538"><o:p class="" style=""> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3539">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. <o:p class="" style=""></o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3633"><o:p class="" style=""> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3540">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.<o:p class="" style=""></o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3548"><o:p class="" style=""> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3549">Has anyone seen
this problem before and can point me in the right direction?<o:p class="" style=""></o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3635"><o:p class="" style="" id="yui_3_16_0_1_1431514167921_3634"> </o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3636">73<o:p class="" style=""></o:p></div>
<div class="" style="" id="yui_3_16_0_1_1431514167921_3637"><o:p class="" style=""> </o:p></div>
<div id="yui_3_16_0_1_1431514167921_3330" dir="ltr"><b class="" style="" id="yui_3_16_0_1_1431514167921_3638">Don, G3BJ</b> </div><div id="yui_3_16_0_1_1431514167921_3330" dir="ltr" class="" style=""> </div></div></body></html>