Write-only network on new Linux Mint machine?
 

I am trying to add a new Linux Mint 18 machine to the network and so far I'm failing. The machine is a Supermicro Xeon with (2) gigabit ethernet adapters. It was an old Fedora machine which worked fine. So far I've built the base OS and added a LAMP stack. Both network adapters are active with dedicated ipaddrs. I can ping out either adapter - either inside my network or the internet. However I can't ping into the machine from anywhere else on my network and a port scan comes up empty. The firewall is not yet enabled on that machine. The rest of the network is a mixture of Windows, OS X and Linux machines - although I haven't tried all systems the failure to reach the new system is wide spread. What am I missing?

Here are some queries that may help:

ifconfig
eno1 Link encap:Ethernet HWaddr 00:25:90:25:d8:15
inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f54d:cd28:8c5f:66af/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:238747 errors:0 dropped:36241 overruns:0 frame:0
TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31186381 (31.1 MB) TX bytes:20461 (20.4 KB)
Interrupt:20 Memory:fba00000-fba20000

enp2s0 Link encap:Ethernet HWaddr 00:25:90:25:d8:14
inet addr:192.168.0.15 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:90ff:fe25:d814/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:471165 errors:0 dropped:36241 overruns:0 frame:0
TX packets:5287 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:80245841 (80.2 MB) TX bytes:444168 (444.1 KB)
Interrupt:16 Memory:fb900000-fb920000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:459 errors:0 dropped:0 overruns:0 frame:0
TX packets:459 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:43018 (43.0 KB) TX bytes:43018 (43.0 KB)

lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller (rev 09)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 05)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation C202 Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)

netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 enp2s0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eno1
link-local * 255.255.0.0 U 0 0 0 enp2s0
192.168.0.0 * 255.255.255.0 U 0 0 0 enp2s0
192.168.0.0 * 255.255.255.0 U 0 0 0 eno1

You have multiple routes for the same network through different adapters. This is a bad thing unless you're bonding the adapters.

Take a read of http://superuser.com/questions/32512...of-inbound-tra though, it might help

Disabling port ...15 fixed it, thanks. I thought by targeting a specific ip it would reply on that ip - obviously an erroneous assumption. I'll just update the bindings and it looks like I am good. Thanks!