Converting Windows 2003 Server to router...how?

[CK804]

I currently have a file/print server using Windows 2003 Server and would like to convert it into a router while still retaining its file/print serving duties. I'll be purchasing two Intel PCIe dual port gigabit cards for it. How would I go about replicating the exact functions of a router, including security features, on my server? Also, which would be the better choice for wireless connectivity: attaching an AP to one of the server's ethernet ports or installing a PCI 802.11g card onto the motherboard? Would I also need crossover ethernet cables to connect between the server and the client computers?

 

[mcmilljb]

You're wanting to use Windows 2003 Server's Routing and Remote Access features. A link to some more information about what's available.

 

[RebateMonger]

How many different subnets and client PCs are you planning on working with? Your purchase of two dual-port ethernet card implies four different networks and a large office. But then you asked a question about connecting the ethernet NICs directly to client PCs with crossover, which sounds more like just a couple of PCs, total.

Normally you'd come out of each ethernet NIC and go to a switch, which would connect the client PCs on that subnet. No crossover cable would be used.

 

[CK804]

For the time being, there will only be two client PCs connected to the network and a few laptops connected wirelessly, but I'd like to keep options open for as many as 10 wired PCs for occassions such as LAN parties. If possible, I'd like for the 2 client PCs connected directly to the server so as to reduce one obstacle for them to pass through on their way to the WAN.

 

[drebo]

Buy this.

 

[JackMDS]

CK804, I hope that you have a good reason for such a cumbersome arrangement for one small Private LAN.

http://www.windowsnetworking.c...03-act-NAT-router.html

http://www.windowsnetworking.c...rver_Windows_2003.html

 

[CK804]

JackMDS, I have gone through at least 5 routers within the past 3 years. No router I buy ever wants to last longer than a year. I bought a D-Link DGL-4300 about a month ago and the wireless connection is already starting to drop. I know that if I turn my server into a router, it would be far more reliable and powerful since the hardware in my server is superior to anything that comes with a standalone home router.

 

[RebateMonger]

My main suggestion would be to forego the purchase of the dual-port NICs. Get a single Intel NIC (as your "LAN-side" NIC) and a good gigabit switch. Hook a WiFi router up to the switch, along with your client PCs. Use your Windows Server as your only DHCP server and as your DNS server for all your PCs (including the Windows Server itself). Turn off the DHCP server in your WiFi router and don't connect anything to the WAN port on the router.

 

[drebo]

Originally posted by: CK804
JackMDS, I have gone through at least 5 routers within the past 3 years. No router I buy ever wants to last longer than a year. I bought a D-Link DGL-4300 about a month ago and the wireless connection is already starting to drop. I know that if I turn my server into a router, it would be far more reliable and powerful since the hardware in my server is superior to anything that comes with a standalone home router.

I always have to question the operating environments (usually the claims themselves) of people who claim that their routers fail all the time. Are you in a 100 year old house with wiring from the 1920's or something? Is your house powered from a windmill with a crappy rectifier that doesn't output constant voltage?

I've used the same router for almost 3 years without issue. I'm currently using a second-hand router that's about 5 years old.

I suppose that I could say that if you can afford Server 2003, you should be able to afford a Cisco PIX or ASA or something. Those almost never die.

 

[JackMDS]

CK804, on the other hand I have systems in few places set with variety of Routers (Buffalo, Netgear, Linksys, Zyxell, SMC,and others), as well as stand alone WAP (D-Link, SMC, Belkin, and others).

The SMC WAP was one time RMAed, and the Netgear currently works Ok with DSL but its WAN port does not like Cable Internet.

Otherwise, all of these are working OK for years, and Rarely need a Reboot (As a note I have No use for torrent).

I.e. it is hard for me to relate to claims of people that try variety of Routers and they all fail.

That means that it something that has to do with your specific environment, or the way it is used.

However it can be fun playing with Windows 2003 too.

I would configure it the way Rebate Monger posted above.

This page describes how to use a Wireless Router as an Access Point.

http://www.ezlan.net/router_AP.html

 

[RebateMonger]

Originally posted by: JackMDS
However it can be fun playing with Windows 2003 too.

Since he's already got Server 2003 in place, might was well use it. I've got several sites where Server 2003 (with ISA Server 2004) is installed as the only router. It's certainly reliable and I can't envision even Torrents taking it down.

I have noticed, though, that NTBackup running late at night on my personal SBS 2003 Server does interfere with simultaneous Vonage VOIP phone calls. I only have a P4 Celeron CPU in that Server and it's pretty busy creating and verifying those backups at the same time as routing VOIP traffic (that also passes through my Server). I suppose I could just move the Vonage modem in front of the Server, but I never seem to get around to it.