Help, Drowning in Network Options
Hi all you networking gurus and thanks in advance.
I got my WinServer2K3 trial copy yesterday and loaded it successfully. Now the hard part -- what type server! And please assume I know absolutely nothing about how to do this!
A) Is the cost of using WinServer2K3 after the trial period going to be too expensive compared to just using WinXP Pro? I'd not anticipate exceeding more than the 10 users WinXP Pro can handle.
B) What's the best way to set things up hardware-wise? Use a router or switch behind my cable modem and plug my main system and server into it?
My simple requirements, in priority order, that would dictate server type:
1)Network my only other system to my server. (See sig.)
2)Establish a firewall either at the server (prefered) or main system.
3)I don't need a shared printer or HD but would like to allow all valid users (remote family members ans close friends) to download and upload data/images/pics to/from the server. I've no requirement to provide website services.
4)Ensure that nobody can get to my main system, even those allowed to get to the server.
5.Will I need to apply and pay for a URL/domain name? How would someone get to the server without a URL/Domain name? Via IP addr?
I'm surfing the net to gain knowledge about networking and would be interested in your favorite "Networking 101" sites, thanks!
Re: Help, Drowning in Network Options
Quote:
Originally posted by OS-Wiz
A) Is the cost of using WinServer2K3 after the trial period going to be too expensive compared to just using WinXP Pro? I'd not anticipate exceeding more than the 10 users WinXP Pro can handle.
Compared to XP Pro, Windows Server 2003 is expensive. Windows XP has a limit of 10 concurrent connections (not 10 users!). If you don't plan on exceeding that, or don't need any of Windows Server's other functions, then you'd be fine sticking with XP.
From pricegrabber.com:
Windows Server 2003 w/ 5 Client Licenses: $644
Windows Server 2003 w/ 10 Client Licenses: $845
Windows Server 2003 w/ 25 Client Licenses: $1694
When looking at the price difference between XP and Server 2003, you need to keep in mind you're paying for all the functions the server version adds, like Active Directory, DNS, DHCP, unlimited client connections, support for more than 2 processors, etc. If you don't need all those, don't pay for 'em.
If you need more concurrent client connections but don't want to spend that kind of money, there's always Linux & Samba. :)
Quote:
Originally posted by OS-Wiz
B) What's the best way to set things up hardware-wise? Use a router or switch behind my cable modem and plug my main system and server into it?
Some of your needs are better served by different configurations, and you'll need to evaluate some pros & cons. You'll probably need to make a compromise. I've talked a little about some of them below.
Quote:
Originally posted by OS-Wiz
My simple requirements, in priority order, that would dictate server type:
1)Network my only other system to my server. (See sig.)
2)Establish a firewall either at the server (prefered) or main system.
3)I don't need a shared printer or HD but would like to allow all valid users (remote family members ans close friends) to download and upload data/images/pics to/from the server. I've no requirement to provide website services.
4)Ensure that nobody can get to my main system, even those allowed to get to the server.
5.Will I need to apply and pay for a URL/domain name? How would someone get to the server without a URL/Domain name? Via IP addr?
I'm surfing the net to gain knowledge about networking and would be interested in your favorite "Networking 101" sites, thanks!
1) No problem.
2) Normally, you would want your server completely behind a firewall, not used as a firewall. If your server box is also your firewall, security can't be quite as tight.
3) An FTP server seems like your best bet. You can use IIS built into Windows or download a freeware/shareware FTP server app from a site like tucows.com. Another option would be to set up a VPN server and allow file sharing access, but that might violate #4 depending on how you configure VPN access.
4) Using a broadband router's port forwarding or DMZ features, you can allow direct outside access to one machine and not others. But broadband routers don't have a "real" DMZ, so someone can use access to one machine to get to others on your LAN. In order to prevent that, you would need a router that supports a real DMZ, like SmoothWall. That way, you can allow restricted access to your server from the Internet by placing it in the DMZ, and only allow limited access from your DMZ to machines on your LAN.
5) You don't need to register a domain name if you can just point people to your IP address. If you don't have a static IP address, though, you would have to tell people every time your IP address changed. A better idea might be to use a dynamic DNS service like dyndns.org. They issue you hostnames like yourcomputer.dyndns.org and your computer runs a client program that updates their DNS records whenever your IP address changes.
Re: Re: Help, Drowning in Network Options
Quote:
Originally posted by SkyDog
Compared to XP Pro, Windows Server 2003 is expensive. Windows XP has a limit of 10 concurrent connections (not 10 users!). If you don't plan on exceeding that, or don't need any of Windows Server's other functions, then you'd be fine sticking with XP.
From pricegrabber.com:
Windows Server 2003 w/ 5 Client Licenses: $644
Windows Server 2003 w/ 10 Client Licenses: $845
Windows Server 2003 w/ 25 Client Licenses: $1694
When looking at the price difference between XP and Server 2003, you need to keep in mind you're paying for all the functions the server version adds, like Active Directory, DNS, DHCP, unlimited client connections, support for more than 2 processors, etc. If you don't need all those, don't pay for 'em.
If you need more concurrent client connections but don't want to spend that kind of money, there's always Linux & Samba. :)
Some of your needs are better served by different configurations, and you'll need to evaluate some pros & cons. You'll probably need to make a compromise. I've talked a little about some of them below.
1) No problem.
2) Normally, you would want your server completely behind a firewall, not used as a firewall. If your server box is also your firewall, security can't be quite as tight.
3) An FTP server seems like your best bet. You can use IIS built into Windows or download a freeware/shareware FTP server app from a site like tucows.com. Another option would be to set up a VPN server and allow file sharing access, but that might violate #4 depending on how you configure VPN access.
4) Using a broadband router's port forwarding or DMZ features, you can allow direct outside access to one machine and not others. But broadband routers don't have a "real" DMZ, so someone can use access to one machine to get to others on your LAN. In order to prevent that, you would need a router that supports a real DMZ, like SmoothWall. That way, you can allow restricted access to your server from the Internet by placing it in the DMZ, and only allow limited access from your DMZ to machines on your LAN.
5) You don't need to register a domain name if you can just point people to your IP address. If you don't have a static IP address, though, you would have to tell people every time your IP address changed. A better idea might be to use a dynamic DNS service like dyndns.org. They issue you hostnames like yourcomputer.dyndns.org and your computer runs a client program that updates their DNS records whenever your IP address changes.
Thanks bunches! That gets me a lot further down the networking road to bliss than I was :D If you don't mind, let me check out WinXP's vs WinServer2K3's capabilities and get back with a followup question or two. WinServer2K3's costs aren't prohibitive for me, but I wonder, due to small number of concurrent users, whether I'd even need it. Again, T H A N K S :) :cool:
