<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/css" href="http://morison.biz/technotes/feeds/rss.css" ?>
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/" 
	xmlns:dc="http://purl.org/dc/elements/1.1/" 
	xmlns:icbm="http://postneo.com/icbm/" 
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/" 
	xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" 
	xmlns:wfw="http://wellformedweb.org/CommentAPI/" >

<channel>
	<title>Comments for: The Internet Server Project - Part II - Planning

</title>
	<link>http://morison.biz/technotes/articles/37</link>
	<description>Let's break down the top level parts for the project...

Introduction

Here's a planning list of things you'll need (some you may already have):
 A connection to the internet
 A computer, your server-to-be
 A registered domain name
 A router
 A set of operating system disks (or a bootable network install disk)
 Disclaimer: This set of articles does not provide detailed step-by-step instructions. They are a &quot;here's the project and the big pieces you'll need, you fill in the details. A disposition towards rolling up your sleeves, figuring things out, and solving problems is decidedly required. Caveat emptor.


Planning Your Server's Connection to the Internet

I'll assume you're doing this out of your house, apartment, or a wired cave, and that you have one or more broadband internet access options: DSL and cable being the most common, satellite and fiber being less common, at least for residential use. Serving email over dialup is possible (and very old school, anyone remember UUCP?), but I don't recommend it unless it's your only option.

If you already have broadband, the current service might suffice. Then again, it might not, especially if it's cable broadband. Following are several key questions to ask your current or potential broadband provider. 

Q: Do the terms of use for the service allow multiple computers on the connection simultaneously and are network server applications like web &amp; email allowed. I've seen contracts that specifically outlaw such use. 

Q: Does the provider have a an option for static IP address (rather than a dynamic IP)?

Q: Does the service provider allow SMTP (port 25) outbound to the rest of the Internet? (This differentiator turns out to be significant as fewer and fewer providers allow port 25 &quot;up&quot;.) Port 25 up is required for mail server operation: more on this ...</description>
	<language>en</language>
	<copyright>2006-2008, Rod Morison Software</copyright>
	<managingEditor>technotes@morison.biz</managingEditor>
	<lastBuildDate>Wed, 08 Feb 2012 05:48:42 GMT</lastBuildDate>
	<generator>Yet Another Community System</generator>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>70</ttl>

</channel>
</rss>
