<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 10"> <meta name=Originator content="Microsoft Word 10"> <link rel=File-List href="cid:filelist.xml@01C3D50F.16AEB540"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="time"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="date"/>  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'> <div class=Section1> ok,looking at the code, the nsca 2.1 server is checking:<o:p></o:p> <o:p> </o:p> if(ntohs(receive_packet.packet_version)!=NSCA_PACKET_VERSION_2)<o:p></o:p> <o:p> </o:p> while the nsca 2.4 client is sending NSCA_PACKET_VERSION_3<o:p></o:p> <o:p> </o:p> <o:p> </o:p> However..i don’t see _any_ difference in the packet structure…<o:p></o:p> so..can I modify the nsca 2.1 server to allow either NSCA_PACKET_VERSION_2 or NSCA_PACKET_VERSION_3 ??<o:p></o:p> <o:p> </o:p> <o:p> </o:p> -Mark<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> -----Original Message----- From: nagios-users-admin@lists.sourceforge.net [mailto:nagios-users-admin@lists.sourceforge.net] On Behalf Of Mark Musone Sent: <st1:date Month="1" Day="7" Year="2004">Wednesday, January 07, 2004</st1:date> <st1:time Hour="11" Minute="3">11:03 AM</st1:time> To: Nagios-users@lists.sourceforge.net Subject: [Nagios-users] nsca version problems? <o:p> </o:p> hi all, I recently upgraded to nsca 2.4 from nsca 2.1 …but heres the rub..<o:p></o:p> the nsca server is running 2.1, and I have most servers currently running nsca 2.1<o:p></o:p> <o:p> </o:p> I have some new servers running 2.4 ..<o:p></o:p> <o:p> </o:p> but the nsca 2.4 clients cant seem to communicate with the nsca 2.1 server.<o:p></o:p> <o:p> </o:p> I’m getting the following error in the server logs: <o:p></o:p> Received invalid packet type/version from client - possibly due to client using wrong pass<o:p></o:p> word or crypto algorithm?<o:p></o:p> <o:p> </o:p> however the 2.1 clients, 2.1 server and 2.4 clients all have decryption_method=1 (simple XOR)<o:p></o:p> <o:p> </o:p> was there a change in the simple xor method??<o:p></o:p> is there a reason why a 2.4 client cant work with a 2.1 server?<o:p></o:p> <o:p> </o:p> what if I make the server 2.4? will 2.1 clients work with a 2.4 server?<o:p></o:p> <o:p> </o:p> any help is greatly appreciated!<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Mark<o:p></o:p> <o:p> </o:p> </div> </body> </html> --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.557 / Virus Database: 349 - Release Date: 12/30/2003 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.557 / Virus Database: 349 - Release Date: 12/30/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.557 / Virus Database: 349 - Release Date: 12/30/2003