can i connect modem to SERVER and then to switch?

[giantbucket]

I have a situation at the office which needs a solution.

currently, I have a DSL modem (static IP, bridge mode) connecting to router (which does the PPPoE login stuff) which connects to a 48port switch, and on that switch are my server (which does DHCP and all sorts of login for clients) as well as the 12 clients (employee computers)

HOWEVER, the router is being annoying and it regularly for no reason fails to connect (it shows my login credentials, but seems to forget them or not use them). it's annoying as hell, and the only redeeming feature is that this router is giving us 2.5G and 5G wifi access for clients and 2 laptops.

CAN I pretty please get that router out of the path? can I connect modem to server and then server to switch and hang all my clients off the switch? possibly make the router a client there too and set it up to function ONLY as an access point.

OR can I connect modem to switch, have server do the login details for our internet, and hang the clients + router (as access point only) off the switch?

basically I NEED to be able to remove the f'n router from the signal path. the server has 2 LAN ports so I hope I can use it like that...

 

[USAFRet]

CAN I pretty please get that router out of the path? can I connect modem to server and then server to switch and hang all my clients off the switch? possibly make the router a client there too and set it up to function ONLY as an access point.

No. The modem gives up one and only one IP address. The first system that connects...that's it.

Just get a better router.

 

[Alabalcho]

You can do that if you put another NIC into your server, and configure your server to do routing / NATting as well. For Windows servers, this is done with "Routing and Remote Access Services". For Linux servers, you will have to read something about iptables and pppd daemon.

 

[McHenryB]

As Alabalcho says it is certainly possible to use the server as a router as you already have two ethernet connections. Depending upon the operating system this may be fairly easy or it may be a pain. But, whatever, it is adding an additional load on the server, and making life more complicated all round. And you also want to use your existing router for wireless connections - yet another complication.

Why bother with all that? Just bite the bullet and buy a replacement router; they are not that expensive and it will soon pay for itself in time saved.

 

[giantbucket]

would I need a separate NIC card? the current server mobo has 2 network ports on it already... I thought maybe one would go to the modem and the other would go to the switch. we're running Windows Server 2012R2 Standard edition.

if I do decide to simply get a better router, what do I buy? I need reliability far more than I need speed. reliability first. speed irrelevant. really, emails aren't that data heavy. we do far more traffic between employee computer and server / printer / plotter than to the outside world.

 

[USAFRet]

would I need a separate NIC card? the current server mobo has 2 network ports on it already... I thought maybe one would go to the modem and the other would go to the switch. we're running Windows Server 2012R2 Standard edition.

Then you have to configure the server to do all the DHCP, firewall, and DSL connection services.

Or, just get a better router.

What do you use the server for now?

 

[giantbucket]

currently server is already doing DHCP, file server, user logins, and VPN for one person who connects from home on evenings / weekends. the current router has DCHP turned off.

 

[Alabalcho]

would I need a separate NIC card? the current server mobo has 2 network ports on it already... I thought maybe one would go to the modem and the other would go to the switch. we're running Windows Server 2012R2 Standard edition..

I missed the part with your configuration. If you decide to go server-only route, check Microsoft site about RRAS. Make sure you have hardened your server, at least disable all services on the external interface.

Configuring RRAS is more or less point-and-click, but I haven't done it on 2012 (we went traditional router route).