[WT-support] Dx Cluster

Andrew O'Brien andrewobrie at gmail.com
Sun Feb 24 04:59:33 CET 2008


Thanks Bob, I will try those suggestions.  I

2008/2/23 Bob Wilson, N6TV <n6tv at arrl.net>:
> Andy,
>
> Try this:
>
> In wtDXTelnet
> Options | Win-Test Network Properties
> Make sure that you have NOT checked "Disable communication with Win-Test".
>
> Note the IP address and port number
> In Win-Test
> Setup [Enter]
> Make  sure "Enable Ethernet network" is checked.
> Make sure *both* the broadcast address and port number are *exactly* the
> same as you saw in wtDXTelnet.
> Under "Network Protocol", click the [Advanced Settings] button and then
> press [Default] and [OK]
> Press [Alt-A] to view the Announcements Window
> Right click, Displayed Bands, make sure all bands are checked
> Make sure "Multipliers only" is *not* checked.
> Option | Bandplans
> At the bottom, try unchecking "Use this current bandplan for the current
> log" to temporarily disable all spot filtering
> Once you get things working, you will probably want to go back and check
> this box
> If it's still not working, Options | DX cluster  | Local wtDXTelnet, Stop /
> Start.
>
> You may want to check "Start/Stop automatically" if you always want to
> connect to packetcluster whenever you start Win-Test.  Win-Test will exit
> and reopen the wtDXTelnet app. each time it stops and starts.  Hopefully you
> have already configured wtDXTelnet to sign in automatically.
>  If you have done all this and there are still no spots in the Announcement
> Window or Radio 1/2 Band Maps, press [Alt-O] to see if any cluster  activity
> is showing up in that window.  If not, and you're really sure you're using
> the local loopback address (127.255.255.255 port 9871) as the broadcast
> address in *both* Win-Test and wtDXTelnet, then perhaps your firewall
> software (ZoneAlarm?) is blocking communications between Win-Test and
> wtDXTelnet.
>
> If you running Windows Vista, perhaps the Vista firewall will need to be
> reconfigured.  I didn't have to do anything to get it to work with the
> Windows XP Firewall.
>
> 73,
> Bob, N6TV
>
>
>
>
> On Sat, Feb 23, 2008 at 5:25 PM, Andrew O'Brien <andrewobrie at gmail.com>
> wrote:
>
> > Thanks Bob.  I have WtDX Telnet configured correctly because I am
> > getting plenty of spots in the Telnet application.  I configured
> > 127.255.255.255 with port 9871 and application ID = Telnet.  IP
> > address is the same for both but the test fails , no communication
> > sent to the cluster or received by Wintest's cluster monitor.
> >
> >
> >
> >
> >
> > 2008/2/23 Bob Wilson, N6TV <n6tv at arrl.net>:
> >
> >
> > > This is a common problem for new users.
> > >
> > > See http://docs.win-test.com/wiki/DX_Cluster/Telnet for the details on
> how
> > > to get it working.
> > >
> > > Pay particular attention to the "broadcast address" and port number in
> both
> > > Win-Test and DXTelnet.  They have to be the same, as shown in the Wiki.
> > > Then it should start to work.
> > >
> > > Note:  spots are automatically "filtered" according to the currently
> > > selected Bandplan, so you won't see every spot in the announcement
> window or
> > > band maps.
> > >
> > > 73,
> > > Bob, N6TV
> > >
> > >
> > >
> > > On Sat, Feb 23, 2008 at 1:40 PM, Andrew O'Brien <andrewobrie at gmail.com>
> > > wrote:
> > > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I am a new Win-test user.  All appears to be working well.  I have not
> > > > figured out how to get DX Cluster spots to show in the DX Cluster
> > > > window.  I have successfully connected to a cluster via telnet in
> > > > Wintest but the spots from the Telnet cluster do not appear in the
> > > > wintest cluster window  .  How do I accomplish this ?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Andy K3UK
> > > > www.obriensweb.com
> > > > (QSL via N2RJ)
>
>
>
> _______________________________________________
>  Support mailing list
>  Support at win-test.com
>  http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>



-- 
Andy K3UK
www.obriensweb.com
(QSL via N2RJ)


More information about the Support mailing list