I’m responsible for operating the server for a small startup game developer based at my university for my placement year – mostly because I’m the only one of us with any network knowledge to speak of. Everything is working at the moment, but it relies on an incoming rule for port 8181 in the server firewall (as does Perforce, on 1666). Research of other stackoverflow questions indicates that’s far from a secure option, but does not provide any alternatives. What should I be doing?
Additional information: Server is running WAMP with Mantis and MediaWiki on Windows Home Server 2011, workstations are mostly using Windows 8.1 and 10. Server connects to the internet via a Catalyst 2950 provided by the university. Five other workstations connect to that, with the remaining seven or so connected via the university’s wireless.
Answer
there’s no need to open ports or forward traffic on the network’s firewall to the server for the purpose of accessing the server locally.
on the server itself it’s required as you intend to connect to it.
clients should connect to the local adress of the server (in your local network) and not any public address.
if wireless network is passing through the catalyst you may add ACLs to allow only the wireless subnets to pass the firewall and be forwarded to the actual server.
Attribution
Source : Link , Question Author : Ded10c , Answer Author : Daniel Nachtrub
