Re: client not defined error
Hi Debbie,
I have updated my beacon central server to v1.3. So now the server and
the client have the same version. But I continue receiving the log
message 'client not defined' in my client and in central loss server
page both of them appear like blind beacons. I don't know what I am
doing wrong. With version 0.9 it worked.
Any idea?
Thanks in advance,
Maribel.
> >Dear all,
> >
> >
> >I have the same problem, but I have reviewed the connection between the
> >server and the client and there is no filters that could throw away the
> >packets. Maybe the reason could be the versions? The server is beacon
> >1.1.0 y the client is beacon 1.3.0.
>
> the server and client versions must match, if they don't the server
> ignores the client data received by TCP (it wont put it on the
> central_loss page) although if the multicast group and port
> information is the same, it will show up on the local_loss page.
>
> >
> >Any idea?
> >
> >Thanks in advance,
> >
> >Maribel.
> >
> >
> >> "what exactly does a "client not defined" error indicate?
> >> i was unable to find any documenation on this error. one of=20
> >> my beacon clients keeps doing this:
> >>
> >> client not defined
> >> Opening client connection
> >>
> >> thanks
> >> -b"
> >>
> >> This means that your local Beacon was unable to successfully open a TCP
> >> connection back to the Central Beacon Server you're pointing at in your
> >> .../src/beacon.conf file.
> >>
> >> Could be a firewall, could be a number of reasons, but the bottom line is
> >> your Beacon says, "Hello?" to the Central Server, and gets no answer back.
> >>
> >> Hope this helps!
> >>
> >> Mitch
> >> --
> >> Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
> >> Project: http://dast.nlanr.net | Personal: http://hobbes.ncsa.uiuc.edu
> >>
>