Merlins Rook
Merlins_Rook is the network server. Merlin was designed and built as a entry level
server. As such, is also my first computer to have multiple processors.
As a server, Merlin has several functions. The first function is a Primary Domain Controller
for Stin_Net. Everyone must log into the network before network resources become available. However,
once on the network, ALL network resources are at your fingers tips.
Other server functions include File Services and Application Services. Recently, I have found
a household server to be The Best Way to "serve out" MP3's to other systems within the Intranet.
Network Services Provided:
- Primary Domain Controller
- File Services
- Application Services
- Internal MP3 Services
- Backup and Security Services
A Growing Network:
As the number of computers on Stin_Net grew, several issues started to arise. Some of
the issues involved having users accounts on many systems. For me to access five systems
comprised Stin_Net, I had to have 5 accounts, one for eash machine. Multiply the number of
users in the house and if guests stayed for any length of time. Still other issues involved
what resources were available if a computer is turned off. Clearly, the old peer-to-peer
network was having limitations.
Account Availability:
As the number of computers grew, there came a desire to be able to centralize accounts.
This would reduce to number of accounts on each machine and allow more time for other
tasks. Under a peer-to-peer network, each computer had to have an account for each
person who can access the machine. Having an account on each machine per each family
member, meant there would be 25 users accounts spread across 5 machines, not counting
administration accounts. Everyone also had to on their machine to access their files.
Instead of having an account on each and every machine, why not centralize each
individual account on one machine? This would reduce the number off accounts from 25
to 6. That's 5 users and 1 system admin account. Now if I have 25 accounts, that means
I have 24 users and one admin. A server was the answer for Stin_Net.
Any other account on any personal computer meerly saves a user's settings.
On workstation, a network user login is not an option. The workstation will allow
standalone users, with exception of the system admin. On the server, system admins,
domain admins, and any type of server operator can logon, at a minimum, to shutdown
the system.
Account Roaming:
Another added benefit to the the server accounts is that access to personnel files is
not restricted to a single machine. I can access all of my personal files from any
computer on the network, by storing my files on a server.
File Availability:
As as the number of computers grew, availability of files became an issue. If a computer
is turned off, its files are no longer available. I tend to leave my workstation on,
so its files are always available. But what about the other systems? If a system is
turned off, not only is its files not available, any resource it hosts are also
unavailable as well. This was particularly important with Castlerock and Baileys_Keep.
If Castlerock is down, access to its files and CD-RW is lost. I would have to transfer
needed files before powering off.
Application Availability:
Some applications, such as Netscape and many Microsoft products, lend themselves
readily to being used as server application. This makes the application both available
to the user at any machine as well as the user's account settings as well. Takes a
bit more work, but pays well in the long run.
File Backup:
Hate doing backups? Try across multiple systems. Enough said.
With the knowledge gained from Short_Rook, Merlins_Rook, was designedas of January 2002. It is a dual Pentium-III processor,
multi-hard drive system that is designed to handle large graphic data as well as general computing.
This workstation is where I do the bulk of my work. Castlerock has become the family and guest's workstation.
Cathedral is my workstation.
The Need for a Server.
In this day an age, just about everyone either has email or friends online. Visiting family members and
friends were no exception. The kids' computers were available, but they do use them. Moreover, the kids have
full access to their own systems. So any and most activity on their system can be readily read, if caches
aren't cleared. Secondly, the kids' rooms don't offer privacy. Their computers don't either. Windows 95/98/Me
were designed for home use and are not as natively secure as Windows NT or 2000....or Linux.
