Ask the Community
Groups
Cannot communicate with Linux (Redhat, Ubuntu, CentOS, Solaris, etc.) - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Cannot communicate with Linux (Redhat, Ubuntu, CentOS, Solaris, etc.)</p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p> </p> <ol><li>Please check the <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Funitrends%2Fhc%2Fen-us%2Farticles%2F360013175417%3Fq%3DSELECT%2BArticleNumber%252CId%252CSummary%252CResolution__c%252CAttachment__Body__s%252CCause__c%252CNotes__c%252CAttachment__ContentType__s%252CAttachment__Length__s%252CAttachment__Name__s%252CTitle%252CKnowledgeArticleId%252CDescription__c%2Bfrom%2BArticle__kav%2Bwhere%2BPublishStatus%253D%2527Online%2527" rel="noopener nofollow">Compatibility and Interoperability Matrix</a> and verify that the Operating System you are trying to protect is listed.<br> </li> <li>The Unitrends Client Agent is installed at <strong>/usr/bp/</strong>. If missing packages (dependencies) are encountered, it must be resolved. In some cases, you may need to resolve 32-bit and 64-bit dependencies.<br> </li> <li>A common mistake is to install the wrong package. For example, while Novel OES resides on SUSE based, the installer is NOT the same. There is a dedicated installer for Novel OES which includes the TSA security module, that is not included in the SUSE package. The Novel OES installed (oes_cnt) is all that is needed (as long as you have your dependencies).<br> </li> <li>During the installation process, the option that a Firewall exists should have been chosen which sets the port to 1745 for data transfer. If this did not occur (or if a communication/permissions issue prevented it), the change may not have been implemented. Please check the <strong>/usr/bp/bpinit/master.ini</strong> file and ensure the <strong>data=</strong> port has been set to <strong>1745</strong>. Save that file and restart the Unitrends agent (usually bpinetd <new *nix systems> but could be xinetd <older>). If you do not see it, you can issue this command from your SSH connection to create the entry for you: </li> </ol><div> <strong>/usr/bp/bin/bputil -p “Configuration Options” data 1745 /usr/bp/bpinit/master.ini</strong> </div> <ol start="5"><li>Allowing communications between your *NIX server and the Unitrends system, can eliminate firewall issues right away. At the minimum, <strong>TCP ports 1743</strong> (Unitrends to Client Agent control channel) <strong>and port 1745</strong> (data transfer, as set in step 3 above) must be allowed bidirectional. If port 1745 is not an option on the *NIX computer, you can choose a port number between1745-1844.<br> </li> <li>Once you have configured everything as needed, consider rebooting the Linux systems. Sometimes, an underlying Linux process is holding the completion of the install/setup. This is rare, but can occur.</li> </ol><p><br> </p> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p>A missed step in the configuration process or permissions issue prevented changes from being implemented.<br> <br> <br><br> </p> </article> </main>