[WT-support] Even more on WinTest and DX Cluster
Andrew O'Brien
andrewobrie at gmail.com
Sat Mar 1 22:03:31 CET 2008
No, that did not work.
Can anyone explain WHY , on my second PC, WIntest DX Cluster Monitor
works with what appear to be the wrong settings ? I use 192.168.1.255
in the Interface Configuration area and 127.255.255.255 in the Wintest
Network Properties area. According to the Wintest wiki, this
configuration should not work on a single computer.
Alas, this configuration does not work on my ham computer. In fact, I
tried various combinations
192.168.1.255 and 192.168.1.255
127.255.255.255 and 127.255.255.255
192.168.1.255 and 127.255.255.255
127.255.255.255 and 192.168.1.255
All with ethernet checked and same port number of 9871. I have made
sure that port 9871 is not in use by something else . Assisted op
chosen, all modes established, and all mults selected.
Maybe I should go back to my router and see if there is some
port-forwarding issue at hand.
On Sat, Mar 1, 2008 at 12:00 PM, Andrew O'Brien <andrewobrie at gmail.com> wrote:
> Worth a try, thanks.
>
>
>
>
>
> On Sat, Mar 1, 2008 at 10:08 AM, Don Beattie <g3ozf at btinternet.com> wrote:
> > Andy,
> >
> > Just one point in case it helps.
> >
> > I seem to remember a problem getting cluster spots to populate my band
> > map, and I think I traced it to having the contest set up as single op.
> > I seem to remember that WT only allows you look at the cluster if you've
> > set up the contest as multi op or Single Assisted.
> >
> > I may be wrong, but there is something at the back of my mind that this
> > was a problem here once.
> >
> > 73
> >
> > Don, G3BJ
> >
> >
> >
> >
> >
> >
> > Andrew O'Brien wrote:
> > > It is getting confusing responding to varying comments so I started a
> > > fresh thread. I am still stuck and getting a tad more puzzled.
> > >
> > > First , I do not use the PC as a network. At least the way I see it,
> > > I do not. I have a single PC connected to the internet via an
> > > ethernet cable to router and a cable modem. The instructions I have
> > > received here suggest that under these circumstances, I should use
> > > 127.255.255.255 in both set up areas, plus the IP address of the
> > > cluster I am connecting to. When I do this, I can easily connect to
> > > the DX cluster as you can see in the picture at
> > > http://www.obriensweb.com/wtcluster.jpg (note the spots from
> > > wtdxTelnet connected to an AR cluster, VE7CC). No spots appear in the
> > > WT window called DX Cluster Monitor. Using commands produced by the
> > > window that pops up after pressing ALT-T has no effect, there is no
> > > communication between WT and wtDXtelnet. The contest I set up is
> > > configured for all modes and DX cluster is set for all spots , not
> > > band/mode specific.
> > >
> > > Now consider this oddity. You may recall that on my other PC in the
> > > house .... Wt and the cluster monitor work as they should. When I
> > > double checked the settings last night I was surprised to find that I
> > > did not have 127.255.255.255 in the WT configure interfaces area.
> > > Instead I am using 192.168.1.255 and 127.255.255.255 in Wintest
> > > Network properties area. So on the second PC, with a separate
> > > install of Wintest and wtDXTelnet on it, the cluster monitor works
> > > NOT with 127.255.255.255 in BOTH areas as instructed but with
> > > 198.168.1.255 in one and 127.255.255.255 in the other. The opposite
> > > of the instructions I have received. the second PC is essentially the
> > > same PC as my ham PC, same brand, same operating system.
> > >
> > > So, one would think if the above works on the second PC, all I would
> > > have to do is configure the ham PC the exact same way ( 192.168.1.255
> > > in the Interfaces Configuration area and 127.255.255.255 Wintest
> > > Network properties area). Alas, no such luck. The ham PC does not
> > > connect WT and wtDXtelnet regardless of setting. Very baffling. By
> > > the way, I do not have "disable communication with Wintest" checked
> > > and I DO have enable ethernet network checked.
> > >
> > > Just in case it matters, here is my PC configuration
> > >
> > > Ham PC: Emachines 2.6 gig processor . OS= XP Home Edition, SP2.
> > > Connected via ethernet cable to a Linksys router which in turn is
> > > connected to a cable modem. The Linksys router is also connected via
> > > an ethernet cable to a Linksys Wireless Access Point that distributes
> > > a Wifi signal around the house.
> > >
> > > Second PC: Emachines 2.6 gig processor (different model number from
> > > ham PC) . OS= XP Home Edition, SP2. Connected to Internet via a
> > > WiFi signal from the Wireless Access point.
> > >
> > > By the way, I uninstalled 3.19 and installed 3.18, no luck
> > >
> > > Thanks for all the comments.
> > >
> > >
> > >
> > _______________________________________________
> > 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)
>
--
Andy K3UK
www.obriensweb.com
(QSL via N2RJ)
More information about the Support
mailing list