<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial><FONT
color=#0000ff><FONT size=2><SPAN class=365403606-25062008>I imaging your problem
is</SPAN> running windows XP.</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2>We had this problem. Spread is a highly efficient lazy
protocol,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2>it doesn't send pings, only detecting failure on an attempt
to send.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2>Windows XP doesn't detect cable disconnection, where
as most other OS/s do.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2>You can fix this with a registry edit.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2>Thanks to Steve Duff for finding this
fix.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=001512306-25062008>
<P><FONT size=2><SPAN class=001512306-25062008>"</SPAN>Just to feed back a quick
workaround to the list, Microsoft have documented a method to disable the Media
Sensing feature which causes the problem with Spread under XP. You can find it
here:</FONT></P>
<P><A href="http://support.microsoft.com/kb/239924/"><U><FONT
size=2>http://support.microsoft.com/kb/239924/</FONT></U></A><FONT
face=Arial><FONT color=#0000ff><FONT size=2> <SPAN
class=001512306-25062008> </SPAN></FONT></FONT></FONT></P>
<P><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=001512306-25062008>"</SPAN></FONT></FONT></FONT></P></SPAN></DIV></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-au><FONT face=Arial size=2>----</FONT></SPAN> <BR><SPAN
lang=en-au><FONT face=Arial size=2>Dr Michael Pilling</FONT></SPAN> <BR><SPAN
lang=en-au><FONT face=Arial size=2>C3I Division</FONT></SPAN> <BR><SPAN
lang=en-au><FONT face=Arial size=2>DSTO</FONT></SPAN> <BR><SPAN lang=en-au><FONT
face=Arial size=2>PO Box 1500</FONT></SPAN> <BR><SPAN lang=en-au><FONT
face=Arial size=2>Edinburgh SA 5111</FONT></SPAN> <BR><SPAN lang=en-au><FONT
face=Arial size=2>Phone: 08 8259 7017 Fax: 08 8259 5589</FONT></SPAN> <BR><SPAN
lang=en-au><FONT face=Arial size=2>email:
Michael.Pilling@dsto.defence.gov.au</FONT></SPAN> </P><BR>
<P><SPAN lang=en-au><FONT face=Arial size=2>IMPORTANT: This email remains the
property of the Australian Defence Organisation and is subject to the
jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this
email in error, you are requested to contact the sender and delete the
email.</FONT></SPAN></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> spread-users-bounces@lists.spread.org
[mailto:spread-users-bounces@lists.spread.org] <B>On Behalf Of </B>Leandro Sales
Holanda Pinto<BR><B>Sent:</B> Wednesday, 25 June 2008 10:33<BR><B>To:</B>
spread-users@lists.spread.org<BR><B>Subject:</B> [Spread-users] Failure
Detection of members on same segment<BR></FONT><BR></DIV>
<DIV></DIV><BR>I'm having a problem with failure detection on members that are
configured on the same segment.<BR><BR>This is my scenario:<BR><BR>I Have two
different nodes connected to the same daemon that is hosted on one of the nodes.
<BR><BR>When, for example, the network cable from the node, that is not hosting
the daemon, is disconnected, the other node is not notified about this failure
and the disconnected node freezes when trying to send a message. <BR><BR>Some
suggestions? What am I doing wrong?<BR><BR>ps. If the nodes are connected to
different daemons then the notifications are going ok (it detects a network
partition).<BR><BR>Leandro<BR></BODY></HTML>