Closed ports on an open firewall w/ port forwarding enabled.

Question

I'm running a closed network for my game development club and I need to be able to have each computer be able to communicate with each other for when the group tests out their new multiplayer games.
I decided to set up Arch as the operating system since they use Lenovo Thinkcentre M92p's right now. I also set up a seperate network server with Arch to take care of networking issues between the computers and because we aren't allowed to use the campus bandwidth.
The server has its own dhcp server running (dhcpd) and iptables set up to allow any and all connections. The computers have exactly the same iptables setup as well.
I've done basic scans of the computers using nmap and it always comes back with
Nmap scan report for localhost.localdomain (127.0.0.1)
Host is up (0.00033s latency).
All 1000 scanned ports on localhost.localdomain (127.0.0.1) are closed
If I try to scan the other computers, the report is no different. I've set iptables to accept incoming connections, wouldn't nmap say all ports are open?
Last edited by Jakkin (2014-11-04 03:09:56)

Answer 1

I know dhcp servers don't open ports, mainly they just provide IP addresses to computers on the network.
I have ssh installed on all the computers (including the server), but the only computer that shows up on nmap is the server itself.
Its kinda embarrassing, but how I found out about the port problem was from testing the network using TF2. When I used my Netgear router as the dhcp server, TF2 worked perfectly. Since I've migrated to the new server and disabled dhcp on my router, TF2 hasn't worked. The computers can see each other, but, other then sshing into the server, they can't seem to connect to each other.
Last edited by Jakkin (2014-11-04 05:15:00)