Andrei, you were correct in thinking it might have been firmware related. After flashing the BIOS (which included the firmware for the network controllers). The second NIC is now recognised as eno2 and both are working perfectly. The BIOS I flashed was a new download of the same version already installed. I have done some more testing and discovered that the BIOS that was installed on the board was modified by the OEM (I assume in order to put their logo on it). I re-flashed this version and the problem came back. So I can only assume they messed up somewhere. However I have decided to update it to the latest BIOS as recommended on Intel's release notes and all is well. What a pain in the unmentionables! As soon as I re-read your message Andrei where you mentioned Firmware I though hmmm.. and it clicked! I remember a similar problem at my old job. Looking at my old notes I had almost the exact same problem. The board was an Intel DH61DL and the network controller did not get detected by the OS and was called eth0 not enp0s0 (OpenSUSE 12.3). The fix was BIOS update. The funny thing is that this board was from the exact same OEM (OEGStone) Stone Computers. They supplied the computers to my old employer. However this is quite a coincidence seeing as I bought this machine second hand over 3 years later. Makes you think right...? Anyway thank you all for your help. I have learned a lot on this one. Next job... :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org