-=> Quoting Richard Webb to Nancy Backus on 01-23-08  04:07 <=-

 RW> FIrst, sorry for not getting back to you for awhile, been out of
 RW> pocket. 

Things have been rather busy at this end, too... so it's taken a little
while to get back to you, now...  sorry..  The rest of this message is
the Wizard speaking... :)

 NB>> been pounding you with: use a POP/SMT client to download from a
 NB>> network account using DOS software to your favorite machine. Easy as
 NB>> pie to do.
 RW> Can work, so long as the machines can talk to each other sans modem
. 

You do not need a phone modem to connect to the web.  What you do need
is the correct equipment for the connection you have or plan to have.  A
phone modem is what you use if all you have is a standard telephone
line.  A DSL modem is what you use if your telephone service provides
DSL.  A cable modem is what you use if your cable service provides
broadband.  These modems (DSL and cable) expect your computer to use a
Network Interface Card (NIC) to interface to them.  Or, you can pony up
the bucks for a T1 line Wide Area Network (WAN) connection to plug into
your NIC.  A NIC is what you use to have a network.  So, if you get DSL
or broadband, you will automatically have a Local Area Network (LAN). 
Now, if you want to expand this LAN beyond one computer, you need more
equipment to connect in extra computers.

 NB>> You have suggested that you want your own mail server. To do that
 NB>> you have to rent a domain name, get registered with an outside
 NB>> server, and set up a computer as a mail server of your own. That is
 NB>> a lot of work just to exchange email. You usually only do this if
 NB>> you have your own business and need the capacity.
 RW> That's the idea, as this would be for business use as well.

If you really want your own mail server, then you are going to need a
?NIX (linux, Unix) box and a captive guru.  I'm not a ?NIX guru, so I
can't help you there.

 NB>> You have mentioned wanting to transfer files between machines. If
   (stuff snipped)
 RW> That's workable.  Main thing is the actual connection b etween
 RW> machines, and  that's where I"m not sure what i need, but was how we
 RW> were working all that  before the big lightning strike back in '02.
 RW> That's why I've been concentrating  on the connectivity issues.

Just about any NIC around today has a connector for CAT-5 cable.  Every
router, switch, or hub uses the same connector.  So, CAT-5 cable is the
cable you use.  Or, you plug in wireless cards and install a wireless
router, but, again, you are going beyond my experience.  By the way,
everything I do know about wireless suggests they have security issues I
don't want to deal with (sometime, maybe...).

 RW> I think I've seen two or three good ftp clients for dos running
 RW> around, and  have a couple of packet drivers.  SUggestions on specifics
 RW> of these for ms dos  are sure welcome however.

When you're in the "land of DOS", there's always more than one way to
skin a cat.  And each software package is unique in its own way.  Packet
drivers are about the only constant, but not every package uses them. 
So, specific answers aren't possible without knowing which specific
package you are going to use.  I prefer to use WATTCP utilities, since
they all configure the same way.  The WATTCP FTP version 0.07 (FTP07) is
the DOS FTP client we use.  I've checked out others, but didn't end up
using them. 

As to packet drivers, you probably can't get ones for the newest cards,
but most of the not so old NICs have packet drivers you can get from the
vendor's website.  3Com has packet drivers for almost all of its old
cards.

I have started setting up a LAN in our house, and decided to use DOS as
the OS on the server.  This is how I planned it, and it might contain
information that would be useful to you in your planning.

A DOS Networking Plan       RJB           jan08
Objectives:
    Low cost, non-proprietary standard network
    Text interfaces preferred over GUIs
    Local (intranet):
	File sharing and serving - all types (FTP, HTTP)
	Mail (optional) - local accounts, delivery (SMTP)
	Printing - central printer (LPD, LPR)
    World Wide Web (internet):
	Mail - remote accounts, delivery (SMTP)
	BBS - TelNet, ZModem (TelNet)
	Browsing - Browser (HTTP, FTP)
	Firewall - hardware type
    Notes:
	A local Server provides file sharing and serving through public and
	 private directories. Public directories allow sharing.
	Most services are accessed through a Web Browser. Any file that can
	 be served using a Web page is possible. FTP will transfer anything.
	Local mail accounts are on the Server, non-local mail relayed to Web
	 mail servers. Clients read directly from each of their accounts.
	The printer is connected to the Server. Client PCs are responsible
	 for generating the correct format print file (PostScript preferred).
	Local PCs can be accessed locally by name using DHCP and DNS. Local
	 PCs acting as Web BBS or Web Server are also supported.
	Client PCs are responsible for peer to peer support (if any).

Software:
    Client(s):
	Any OS - Any Clients for: FTP, Mail, TelNet, Web Browser, LPR, etc.
	 This is the same stuff for both Local and Web
    Server:
	DOS - EZ-NOS (FTP, HTTP, SMTP, DNS) and LPD
	 pros: free, easy setup; cons: 2GB drives, 8.3 filenames, flexability?
	LINUX - several distros, Apache, etc.
	 pro: free or almost; cons: no spaces in filenames, complex setup
    Notes:
	Local net should support text Browsers (KISS).
	Low cost means no purchased software, text means not Windows Server.
	I have: DOS, EZ-NOS, Lynx, FTP, Pegasus + POPSMT, TNPort + ConEx
	I need: LPD, LPR

Hardware:
    Client(s):
	Any PC - NIC, cat5 cable to switch
    Server:
	386+ PC - lots of disk space and memory, NIC, cat5 cable to switch
	Switch/Hub - to connect Local PC cables together (stackable)
         must have 1 port per PC and 1 for the Router
        Router - to isolate Local net and interface to the Web
    Web modem:
        DSL, Cable - supplied by ISP, service specific
    Notes:
        Modern routers often contain a Switch, DHCP, and Firewall.
        Low cost means wired, not wireless.
        I have: PCs, Switch, Router, cables, DSL, Printer.
        I need: Server PC disk drives.

Action:
 Acquire hardware and software, verify legal licenses
 Configure Router DHCP and Firewall
 Configure Server and Client PCs
 Implement a Server backup plan (files and hardware)

Me again...  Hope this is helpful.  :)

ttyl      neb

... Age needn't necessarily be a bar to immaturity.

___ Blue Wave/QWK v2.20
--- SBBSecho 2.12-Win32