Ah, usually a network server has only two NICs (one WAN, one LAN) with a managed or unmanaged switch on the LAN. A router is basically three things: an internet gateway, packet routing, firewall, and switch. YoI assume you already got the internet gateway and packet routing parts covered using software and I imagine you are looking into the firewall aspects (or Windows Firewall). The switch as you suggested, could mean additional NICs in the computer or a managed/unmanaged external switch. I would always recommend the external switch because they are cheap, simple, and effective. I've been using this one for at least a year now and it is awesome (albeit hot): http://www.newegg.com/Product/Product.aspx?Item=N82E16833129025 The real disadvantage of what you are aiming for is that it will require a lot of micromanagement. If you don't have software that can act as a DHCP, you'll have to manually assign IP addresses for all NICs. Additionally, your software will probably need to be PPPoE capable in order to interface with your modem/bridge (depends on your Internet connection). If not PPPoE, you'll have to interface with the modem through a default gateway IP. ICS (the page is old) should be able to handle DHCP. What really gets me is that a good switch costs about as much as a decent router. You only need to share the connection with three computers which is what all decent routers support (less the headaches). If I were in your shoes, I'd go with a router DMZing the server if absolutely necessary (make sure it has a firewall enabled if you do). Consider this (or the router you originally suggested): http://www.newegg.com/Product/Product.aspx?Item=N82E16833127241 Just don't use the disk that comes with any router--they be worthless and create more problems than they fix.