| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: CA Beacon |
| From: | Maren Purves <[email protected]> |
| To: | Mark Rivers <[email protected]> |
| Cc: | TechTalk EPICS <[email protected]> |
| Date: | Thu, 05 Jul 2007 10:57:58 -1000 |
Another one is if you have recently moved an IOC onto a different subnet or to a different IP address. The DNS cache can do weird things (both on the network/router/DNS server and on the IOC itself) - I remember seeing similar problems at some point, and you can probably find that thread in the tech-talk archives searching for DNS cache.
Mark Rivers wrote: [...]
I believe those are multicast message, i.e. sent to the broadcast address with with a specific port, in this case 5064. I think I have seen that message when some device on the network is not ignorring the multicast as it should, but is replying with a "Connection refused" message. In our case it was a terminal server that was doing that.
Mark
________________________________
From: [email protected] on behalf of Heinrich du Toit Sent: Thu 7/5/2007 1:26 AM To: TechTalk EPICS Subject: CA Beacon
Hi
We have a local control net. This is the first time I run an IOC on it:
I get the following message:
../online_notify.c: CA beacon (send to "172.16.255.255:5065") error was "Connection refused"
What does this mean? Why is it trying to connect to the broadcast address?
-Heinrich