Ask the Community
Groups
Testing the health of an on-board NIC - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Testing the health of an on-board NIC</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>Rule out the on-board NIC on physical systems as the root cause of network problems</p> <h3 data-id="description">Description</h3> <p>If you’re having problems connecting to clients, one possible cause could be a non-functioning NIC on the physical appliance. Running the command in the Resolution section may help to rule this out as a possibility.</p> <h3 data-id="cause">Cause</h3> <p>There are many things that can cause loss of network connectivity, including faulty Ethernet cables, improper switch/router configuration, or faulty hardware. This command will help you rule out the on-board NIC on the Unitrends physical system being the root cause of the issue.</p> <h3 data-id="resolution">Resolution</h3> <p><b>***NOTE: This command should NOT be run remotely. It will cause the network service to stop, so it must be run from the console.***</b></p> <p>ethtool –t eth0</p> <p>The output of the command tells you the health of the NIC. After you’re returned to the command prompt, run the following command to start the network service:</p> <p>service network restart</p> <p> </p> <h3 data-id="third-party-sources">Third-Party Sources</h3> <p> </p> <p> </p> </article> </main>