Discussion Locked

Network Server/LAN Design

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I recently switched from Cable to ADSL. Prior service was Dynamic, however, new service is Static. I have 3 PC's on my LAN (2-W2KPro, 1-W2KServer Eval). Currently, I have all PC's accessing the Net via a Netgear Router/Gateway, it is config'd asa DHCP to provide IP's to my PC's, and the Netgear Router/Gateway is connected to the DSL Modem which is supplying the IP addy to the Netgear device via DHCP. I got a static IP so I can host services (FTP, Gaming) and to create a Domain for my LAN (thinking about registering for a Domain Name). I just started studying some material for an MCP cert with a goal of obtaining the MCSA and/or MSCE. I'm just not positive on how I could configure my Network and any suggestions on how you would do itwill be appreciated. Here's my thinking; place two NIC's in the server - one direct to DSL modem with Static IP, other to Netgear Router for LAN. Disable DHCP on DSL modem and Netgear Router, and allow server to act as DHCP for LAN. Does this sound close, am I on the right track? I'm also concerned about security for my server and LAN so I don't want to open a lot of ports if possible. If any of my options or concerns sound dumb, or off the wall, I apologize - keep in mind I'm new at this.Thanks in advance for any advise!!

7 replies

by cg it

My only thing(s) would be why a router for the LAN? The other is that I would have my clients connect to the server via the internal NIC via a multiport switch with an uplink port. I would then place a firewall/packet filter between the DSL modem and server. IP addressing scheme has a couple of choices. NAT, DHCP or static. NAT allows clients to connect to the internet without revealing the private IP address. DHCP relieves you of the burden of having to keep track of IP addresses for a large # of clients where a static scheme would be just to much work. Static is that, having to assign an IP, submask, gateway, DNS WINS addresses for all clients.

by mrjay67

Basicly what you and answer 1 said will work. However for just a different point you could hook the router to the DSL modem and then hook all the computers to the router. This keeps from loosing internet if the server goes down and is much simplerto setup.

If you go with your initial thought then using a switch between server and rest of PCs would be simpler. There are any number of ways to do things in this situation. These are probally the most common. Also as answer 1 suggested, you may want to think about a firewall between DSL connection and either the router or the server depending on how you go. Some routers will have built in firewalls that could simplify the physical side of your LAN config.

Personally, since you are using a router, I would setup the DSL through it and connect all the machines to it. This way all systems have a hidden private address. You could setup a DMZ or use port forwarding to access the server(depends on netgear options.

Just thought id throw out my 2 cents

Jason

by rhaines2

Thanks for the replies received thus far. It appears as though I have more than a few choices. I have not decided on which option to use but, I may try a few different setups just to see which one works better. Besides, I just might learn a think or two in the process. Thanks!

This discussion is closed to new replies.