From aec31f89a28851c72082c4e08117423310c5d721 Mon Sep 17 00:00:00 2001
From: Jeff Hill <johill@lanl.gov>
Date: Wed, 11 Sep 2002 20:50:26 +0000
Subject: [PATCH] added client does not see server's beacons troubleshooting
 hyperlink

---
 src/ca/CAref.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/ca/CAref.html b/src/ca/CAref.html
index c5a369e98..278f151d9 100644
--- a/src/ca/CAref.html
+++ b/src/ca/CAref.html
@@ -67,6 +67,7 @@ height="31" width="88"></a></p>
   <li><a href="#Unicast">Unicast Addreses in the EPICS_CA_ADDR_LIST Does not
     Reliably Contact Servers Sharing the Same UDP Port on the Same
   Host</a></li>
+  <li><a href="#Client1">Client Does not See Server's Beacons</a></li>
 </ul>
 
 <h3><a href="#Function">Function Call Interface Guidelines</a></h3>
@@ -762,6 +763,11 @@ weakness of most IP kernel implementations) only one of the servers will
 typically receive UDP search requests sent to unicast addresses (i.e. a
 single specific host's ip address).</p>
 
+<h4><a name="Client1">Client Does not See Server's Beacons</a></h4>
+
+<p>See <a href="#Dynamic">Dynamic Changes in the CA Client Library Search
+Interval.</a></p>
+
 <h2><a name="Function">Function Call Interface General Guidelines</a></h2>
 
 <h3><a name="Flushing">Flushing and Blocking</a></h3>