Re: DAST: Multicast Beacon - Configuring a central server - raul.fernandez --at-- mci.com
Hi, Raul -- This error means that the Beacon can't open a TCP connection to
the Central Server. Could be a firewall issue, could be a network problem,
but for whatever reason, your local Beacon is trying to open a TCP
connection back to the Central Server and it's failing.
Hope this helps!
Mitch
At 10:24 AM 10/15/2005 -0500, you wrote:
>
> Contacting DAST re: Request for information about Multicast Beacon
> From: Raul Fernandez <raul.fernandez --at-- mci.com>
>
> Subject: Configuring a central server
>
> Question/Comment:
> Mitch et al,
>
> I have configured a box a as central server. I have another box
connectiong to it. I changed the necessary parameters in beacon.conf for
the client and the server.
>
> On the client I changed the group, kept default rtp port of 10002, and the
> central server name.
>
> On the central server I changed the group, kept default port, changed the
central server name, and activated the BECENTRALSERVER option.
>
> I am getting some noise form the client:
>
> "client not defined"
> and I cant see the client on the central_loss html output on the central
server nor can I see the client on the beacon_info html output. I do see
the client on the local_loss. Any ideas on what maybe causing this?
>
> We are running the lastest version of Beacon 1.3 on FreeBSD.
>
> Very Respectfully,
>
> Raul F. Fernandez
> MCI
>
>
>
--
Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
http://hobbes.ncsa.uiuc.edu/