Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
What would be the proper way to set things up? Let me know if there are any issues with this setup please...
ISP > Router (No DHCP) > Server NIC1 (WAN Port on Router, DHCP On, Static IP) > Server NIC2 (LAN Port on Switch) > Switch > Workstations
The server will have the static IP assingned by the ISP along with the DNS information from the ISP. The workstations will get there IP from the server and DHCP. The DNS server for the workstations will be the server IP, which is the statically assigned one.
Does this all seem good to go? Am I missing something?
Could be, but that depends. What are you main objectives for you network?
Jason
Jr. Level Support
http://www.BrandedTechnology.com
0 
It is for a Church, so the domain controller is setup to give various access levels, etc... They all need Internet, email, etc...They will also all share an accounting program which uses a single DB file housed on the server. It is a smaller sized network, maybe 10 - 15 users. Any other details you were looking for?
0
Are you planning on creating a domain or leaving it as a workgroup? If it were me, in a 10-15 user environment, I would give serious consideration to creating a domain if you haven't already decided on that.
When you say The server will have the static IP assingned by the ISP you mean a static IP address, right?
Are you planning on hosting your own web site on your server?
The company I worked for last year had one church as a client. They had less than 10 users so we set them up with a workgroup and a "server" running XP. They had a statically assigned IP address on a business class DSL connection. Their setup was as follows:
ISP >> Router >> Switch
with all client PC's plugged into the switch. Their router had DHCP enabled and provided all clients with IP addressing information. The router also had a built in firewall.
It doesn't matter much which you use for DHCP, the server or the router, but, you don't need to multihome your server (have more than one NIC in it) in either case. You just need it plugged into the same switch as all the other PC's. They should still be able to communicate with the server and get their DHCP assignments and access the internet. The only thing is, you would have to list the router's internal IP address as the gateway on all clients. I would definately use a statically assigned internal IP address on the server.
Keep the setup as simple as possible (KISS)!
0
Also, when you say email, are they going to run their own messaging server, or is their ISP gonna provide email services?
The connections should be Net -> Router (WAN), which receives the public static IP -> Router LAN ports to switches/computers.
The rest of the config really depends on a lot of issues. If you're gonna go domain based network, DHCP should be provided by the 2003 server, not the router. This is because DHCP servers need to be authorized in Active Directory, and also DHCP services in a 2003 supports dynamic updates to DNS.
Should you go domain? Well, if the church is gonna run it's own messaging services via Exchange, your hand is pretty much played that you're going domain, but with 15 users already, domain really should be the direction you take anyway.
Also, for such a small organization, and particularly if the church is going to run it's own messaging server, I would be looking at Windows Small Business Server 2003, which includes Windows 2003 and Exchange 2003, along with Sharepoint services. It's also easy enough to admin once setup by non-techies.
"President Bush is doing everything he can to lower gas prices, including...making the oil companies so rich that maybe they'll get sick of money."
0
Great. Thanks for all the input. The email wil be setup using Outlook and a POP account via the web which is housed elsewhere. This server is for only internal data per se. Yes a domain will be used as will DHCP via the server. So would you still give the router the static public IP? OR give that to the server? I guess my question is more of the connectivity, rather then the "setup" of the server itself at the moment.
So from what we know, we go ISP/WALL -> Router (WAN) -> Server/Workstations (Plugged In Router LAN)
Assign the public IP to the server or the router?
Thanks So Much Folks!!!
0
You'll want to set your public IP on your router. Your router will provide NAT for all your workstations/servers on your LAN. If you need more assistance, you can contact me at
Response Number 7
Sponsored Link
Extend Windows 2003 prima...
Port Forwarding 
Post LockedThis post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Windows Server 2003 Forum Home
Sponsored links
Ads by Google
Results for: Proper setup of server....setup 2003 serverSummary: Hello! i have recently installed windows 2003 standard server on my pc. the next thing i want to do is to make a website and host it on to my own server. now the problem is how to setup the server.......
www.computing.net/answers/windows-2003/setup-2003-server/2347.html
Setup of Windows 2003 ServerSummary: Advise me to get out of the typical problem, I am encountering. (A) Configuration Details of my System: · Intel P4 processor (System Bus = 400 MHz, 256 KB L2-Cache, Hyper Pipelined Technology) · Int...
www.computing.net/answers/windows-2003/setup-of-windows-2003-server/2665.html
How to setup 3 serversSummary: In a hyperphetical situation, if one has 3 departments in a company Sales Personnel I.T Would i need to use 3 servers to keep active directories on each department and to things secure so other depar...
www.computing.net/answers/windows-2003/how-to-setup-3-servers/3199.html
