https://community.splunk.com/t5/Monitoring-Splunk/Search-Peer-unreachable/m-p/749651#M10974 <P>How do I resolve authentication or pass4SymmKey mismatch between search head and peer?<BR />Also getting a situation where 0 clients phone home.</P> Fri, 11 Jul 2025 18:38:30 GMT gitau_gm 2025-07-11T18:38:30Z https://community.splunk.com/t5/Monitoring-Splunk/Search-Peer-unreachable/m-p/749651#M10974 <P>How do I resolve authentication or pass4SymmKey mismatch between search head and peer?<BR />Also getting a situation where 0 clients phone home.</P> Fri, 11 Jul 2025 18:38:30 GMT https://community.splunk.com/t5/Monitoring-Splunk/Search-Peer-unreachable/m-p/749651#M10974 gitau_gm 2025-07-11T18:38:30Z https://community.splunk.com/t5/Monitoring-Splunk/Search-Peer-unreachable/m-p/749653#M10976 <P>That's two different things.</P><P>To resolve a pass4SymmKey mismatch, update the plain-text pass4SymmKey value in server.conf and restart the Splunk instance.&nbsp; Splunk will encrypt the value when it restarts.&nbsp; Repeat for each SH and peer.&nbsp; Do NOT copy an encrypted pass4SymmKey from another Splunk instance.</P><P>Peers do not phone home so you must be referring to forwarders contacting the Deployment Server (DS).&nbsp; Ensure all clients have the correct DS info in deploymentclient.conf and that the network permits connections from each client to the DS.</P><P>With more information about the problem(s) we can be more specific about the solution(s).</P> Fri, 11 Jul 2025 20:04:05 GMT https://community.splunk.com/t5/Monitoring-Splunk/Search-Peer-unreachable/m-p/749653#M10976 richgalloway 2025-07-11T20:04:05Z