first thing: XP Pro is a workstation OS, not a server. It has a limit set to the number of concurrent connections - I think 10. That means that only 10 people can view your site at a time. The proper OS for Windows is Windows Server 2003 - that is what should be used. Win2k3 is designed for this and is, IMO, way more secure than WinXP.
And scarabaeus - he will need the .Net Framework to host/develop an ASP .Net site, which I'm sure is what he meant in his line - ASP 2.0 site - as classic ASP version 2 is nearly a million years old, especially if he's also talking about SQL Server Express.
Next thing: not sure what kind of Internet connection you have, but most ISPs won't allow you to host sites through a home connection - too much bandwidth usage and they may come knocking. Plus you wouldn't have near the connection speed that a hoster would most likely have.
Hosting is cheap, why would you want to host your own site? Are you going to be around 24/7 in case your server goes down? You plan on taking a vacation or go away for the weekend? hosting your own will really tie you down...
Thanks guys for the input. My bad on the ASP 2.0, I meant ASP.Net. .Net Framework is 2.0.
" Hosting is cheap, why would you want to host your own site? Are you going to be around 24/7 in case your server goes down? You plan on taking a vacation or go away for the weekend? hosting your own will really tie you down... "
I realize this but it'll be much easier to manage the DataBase if I can connect to the site from local network for udating.
The boxed site will have dedicated line from the ISP and it's for a limited number of people. I first thought Windows Server 2003 but then said "Why not XP, I already have it and won't have to spend $400 or more.
I didn't realize there was a 10 user limit. Although at this time, I'd be lucky to get 10 users but that could change in the future. It's not exactly open to the public and you can't get much use out of it unless you're logged in. Anonymous users can't sign up as a member. Members are a private group with assigned usernames and passwords.
I should probably go wit Windows Server 2003. So, here's the revised list. Will it get me off the ground or do I need more?
1. Windows Server 2003
2. .Net Framework 2.0
4. SQL Server Express
5. Static IP on a high-speed connection.
I'd like to be able to control everything, I'm getting deeper and deeper and becoming a junky with this stuff. I do have a shared host for my main site.
Is it cool to run IIS and SQL Server Express simultaneousy? Will there be any clash?
Adding fuel to the flame, here's what I'd REALLY like to do:
Connect my three local desktops to a machine runnig WS2003 and use WS2003 as a file server for the three desktops. Also use the same server machine to run IIS as the Internet server. Of course, I'd want to run .Net FX 2.0 and SQL Server Express.
Is this feasible or should I back up and re-group?