Good Day oldman-ga,
Sounds like you already have the basics figured out. I'm going to
present you with a couple of scenarios, and things you should
consider. I will elaborate on all my suggestions a little bit too, but
because there is a lot to consider I won't go into great detail on
everything: once you have read my answer and decide on a course of
specific action, I can give you more information that will be relevant
to your decision.
WHAT YOU WILL NEED:
-------------------
You will need a static IP. A static IP will ensure that your computer
is always at the same virtual address. Without a static IP, your
server would be "moving around virtually".
With a static IP, users can type in the IP address into their web
browser which will connect them to your computer. Of course, you can
link up an IP address to a domain name using a DNS server, creating a
web server that is accessible via a regular domain name like
www.oldman.com rather than IP address. Not all Win2K versions have the
built in capability for running a DNS server. Please check my
references listed at the bottom of the answer for more details. You
will need to somehow access a DNS server or build one if you wish to
use a domain name vs. direct IP address access.
A static IP can be purchased from your Internet provider, or "you
might get one by default". My cable company offers dynamic IPs to
residential customers, but my IP has changed only once in over a year.
The IP expires every 48 hours, but I am reassigned the same IP every
time. Technically, because the IP address I have is assigned
automatically by a server every 48 hours it is considered dynamic.
However, it behaves like a static IP in the sense that it never
changes.
This means you might be able to save some money if you just purchase a
regular high speed internet connection and watch to see if the IP
changes upon expiry. If it does change occasionally, you can always
reconfigure your server, but until you do make the update after a
change, your server will experience down time. Of course, depending on
how often this happens, this may or may not be an option. Your best
bet is probably to talk to someone who has been using the Internet
Provider you intend to use for your server. Ask them how often their
IP is changing (note that most people won't know, so you will have to
ask around until you find someone who has been keeping an eye on their
IP address).
Of course, you can save yourself the trouble and just ask for an
account with a static IP. However, this option generally costs twice
as much as a dynamic IP account.
OTHER THINGS YOU SHOULD CONSIDER:
---------------------------------
Server reliability is going to be hard to achieve. There are tens, if
not hundreds of reason why you will experience down time, and here are
just a few:
- Power Outages
BIG BOYS: Have generators for back up power.
- Internet Service Interuptions
BIG BOYS: Have multiple feeds.
If one feed goes down, another picks up the traffic.
- Hardware failure
BIG BOYS: Most run a network of Unix and Linux servers.
Hardware can be replaced without shutting down, while
other
machines on the network keep working to provide the
service.
These servers keep on running, without even needing a
reboot
on 95% - 99% of upgrades.
- Virus attacks / hacks
BIG BOYS: Have dedicated personnel to keeping the system upgraded
daily
with newest patches.
If you are providing service to clients with multiple work shifts, or
across multiple time zones, you will not be able to shut your server
down in the evening to upgrade, repair, or maintain.
If you are providing service to 9-5 clients in one time zone, you can
always shut down the server in the evening for any repairs or
maintenance that is required.
In either case, hardward malfunction will be a problem sooner or
later, and so will the other issues I mentioned above.
What I am getting at is that by industry standards you will not be
able to create a "reliable service" without a huge investment.
Many web hosting companies will allow you to bring in your machine
into their environment. This means you would not have to worry about
power outages and Internet Outages experienced by your Internet
Provider. You still would have to maintain the software to keep your
server as secure as possible and deal with maintenance of hardware.
This setup only solves a portion of the problem, and will cost quite a
bit (the going rate in my city starts at about $200 Canadian Dollars
per month - that's about $140US Dollars).
I think your best route is still hosting with someone. Define your
needs on paper, and start E-mailing web hosts. Tell them your needs
and if the web host can meet them, ask how much they will charge you.
Tell them you need access to install tools in your web space, and
access to be able to trouble shoot some of your new programs. I think
you will be surprised on how much you can do remotely.
I STILL WANT MY OWN SERVER! WHAT DO I NEED?
-------------------------------------------
- non-changing IP address: static, or a dynamic address that you get
to keep for an extended period of time
- a reliable machine, preferably with good speed if you are expecting
a lot of traffic
- server software like Win2K, WinNT, Linux, or Unix.
- know-how on configuring a web/DNS server
Technically that is everything you need for the most basic setup.
AFTER WORD
----------
You were already aware of most of the needs to run a server, so there
wasn't much I could add there. I hope to have provided you with some
decision making knowledge that will help you determine a best course
of action. Once you have decided on a course of action, I will be
happy to provide more details on how to complete the steps along your
chosen way. If required, please ask for a clarification at such time.
I have helped setup a few servers, and have seen what goes into
preparation. I am by no means an expert. I have setup one server by
myself, and it was a Linux server. There is little involved in
creating a machine that can be accessed over the Internet. Maintaining
it, and having it do what you need done is a whole separate issue that
is much bigger then anything else involved.
Based on my experience and having heard your needs, I feel that you
are much better of finding a web host that will work with you at a
reasonable cost. It doesn't sound like you will need that much, and
you should be able to get everything from a web host for about $50-75
(Canadian Dollars, based on the City of Winnipeg, Manitoba prices). If
this seems like too much money, I can tell you that the piece of mind
you will get at night is worth it. There is nothing worse then 15
clients calling you in the middle of the night saying "the system is
down, fix it... and fix it fast or give us our money back and get
lost".
RESOURCES
---------
Website: How to setup Win2K for Web Server and DNS Server
URL: http://www.experts-exchange.com/Operating_Systems/Win2000/Q_20704130.html
Website: How does a web server work?
URL: http://thewhir.com/find/web-hosts/articles/webserver.cfm
SEARCH STRATEGY:
----------------
Google search for: "web server"+"setup"+"how"+"internet"+"windows
2000"
"web server"+"setup"+"how"+"internet"
Thank you for choosing Google Answers. Again, please do not hesitate
to ask for a clarification at any time. I will be very glad to further
assist you.
Regards,
slawek-ga |
Clarification of Answer by
slawek-ga
on
08 Sep 2003 16:59 PDT
Hi oldman-ga,
I have done a quick search for:
"IIS 5.0 limitations"
"IIS 5.0"+"maximum"+"traffic"
and a few other similar search queries. They did not turn up anything
about user limitations. I don't know if I should take that as a no
limitations theory, or something else.
From past experience, hardware is more of a limiting factor then
software. The software can handle a lot more then the hardware it is
running on. Of course, as I mentioned, most of my experience is from
the world of Linux and Unix. However, Linux and Unix servers are
overall much less intensive on hardware usage, and I imagine that
based on that, the same rule would apply to the Windows servers?
I have sent off a couple of quick E-mails and posts to a few people
that might know more and be able to give me some extra insight into
the matter. I will be sure to post any additional notes I receive on
the subject, as soon as they come in. If I don't receive anything by
tomorrow evening, I will try to sign in and just post an update
anyway.
If my theory is right, and hardware is more of a limiting factor, your
question can be best answered by the web host. The web host might tell
you that by the time you use up the server limit (should there be
one), you'd be out of bandwidth, or their hardware would melt.
Regards,
slawek-ga
|
