Chapter 13
Client Issues
CONTENTS
While contemplating the necessary decisions regarding your server
or servers, including what connections to set up for your machines,
keep in mind what clients you will connect to the intranet. This
chapter will help you develop the basis for your current client
infrastructure, and, if you already have client applications in
place, it should help you narrow down your shopping list of upgrades.
The client hardware currently in use (or that will be used) likely
will dictate what server hardware and software you choose. This
chapter discusses various client hardware and software options
and shows how these options influence server and connectivity
applications. Becoming knowledgeable about the myriad options
available to build an intranet will determine your intranet's
functions and ultimate purpose.
The largest cost of building your intranet probably will be for
client hardware, software, and upgrades. The types of server hardware
and software, as well as the functions you include on your intranet,
will likely be based on the client hardware on hand.
For users working on a contained LAN or WAN only, this assessment
means a simple inventory. There will be more considerations for
users who are planning to open their LAN or WAN to remote users
and for users who are building an intranet specifically for remote
users. Whatever the case, the client hardware will require one
or possibly several definite minimum levels of compatibility with
the server software. All users should be able to access and understand
the functions at the basic level. An additional, more advanced
level is recommended for more advanced users to utilize the intranet
more fully.
As you build the foundation for your intranet with upgrades and
purchases, carefully consider the display, processor speed, memory,
storage (hard drive space), and peripherals, because these factors
determine how complex and functional your server software will
be. As you choose your framework, keep upward compatibility in
mind. For example, a 386 or 486 computer with a slow processor
usually doesn't require more than 12 to 20 MB of RAM (memory).
More memory after that won't make the system as fast as upgrading
to a faster processor would. As a client machine, a 486 or slower
processor should have at least 4 MB of RAM to perform any of the
applications discussed here. A 486 or slower processor is most
effective with 12 to 20 MB. At the other end of the speed spectrum,
a faster processor, such as a Pentium, will operate with 8 MB
but would be more effective with 16 to 24 MB.
If you're working in a Macintosh environment, consider that a
Performa or Quattra with 6 to 16 MB of RAM is roughly equivalent
to the minimum PC machine just discussed. A PowerMac or clone
should have at least 16 MB of RAM for optimal performance.
Likewise, when you're considering multimedia applications to add
to your intranet, client costs will play a significant role. For
example, even though installing server software that incorporates
sound and/or video into your intranet can be relatively inexpensive,
equipping all the client machines with multimedia peripherals
can be very expensive. Although some personal computers sold within
the last two years have sound and video capabilities, many do
not. Also, Internet-based phone conferencing requires a high-quality
microphone and speakers. Additionally, video conferencing requires
a high-quality video card and a fast processor. Client machines
expected to handle video conferencing should have Pentium or faster
processors, as well as video cards with at least 1 MB of video
RAM. The cost of preparing and maintaining a user base of qualified
machines is a primary factor to consider when you're building
your intranet.
Client-side software costs will vary widely, depending on the
functions you want to perform on the intranet. Most new operating
systems come prepackaged with several TCP/IP clients. Windows
95 comes with a Telnet client, a command-line FTP client, a mail
client, and a Web browser. OS/2, MacOS, and Windows NT also come
with various clients.
Also, many TCP/IP clients are available on the Internet for free
or for less than $50 per license. Some cost as little as $10 or
$15. These applications-known as freeware or shareware-typically
aren't quite ready for commercial sale, either because they don't
have as many features as commercially available software, or because
they aren't as visually attractive (but still are acceptable clients
for many users). The availability and cost of these clients are
neither steady nor consistent. Intranet administrators might find
that some users will want to use different clients, depending
on the users' own preferences, skills, and job functions. Therefore,
allowing users to utilize a basic freeware client and then find
and install their own personal favorites might be a good option.
Typically, no technical support is available for freeware or shareware.
Of course, if you want to purchase a full suite of products for
your users, many such suites are available. Netcom, SPRY, Chameleon,
FTP Software, and many other large Internet Service Providers
(ISPs) and software makers offer such suites, as well as the suites
available with operating systems such as Windows 95, Windows NT,
OS/2, and Linux. This will probably reduce your technical support
and training costs but will increase your up-front software costs.
These suites can run as much as $150 to $350 per license, but
they come with free or inexpensive technical support. In fact,
with some of these suites, you wouldn't need a full-time systems
administrator. Figure 13.1 shows an example of a suite of products.
Figure 13.1: Chameleon's suite of products.
The following is a list of a few suites and their contact information:
Distinct
12901 Saratoga Ave.
P.O. Box 3410
Saratoga, CA 95070
Telephone: (408) 366-8933
Fax: (408) 366-0153
ftp.distinct.com
www.distinct.com
EveryWare Development Corp.
7145 West Credit Ave.
Building 1, Suite 2
Mississauga, Ontario L5N 6J7
Canada
Telephone: (905) 819-1173
Fax: (905) 819-1172
info@everyware.com
FTP Software, Inc.
100 Brickstone Square
Andover, MA 01810
Telephone: (508) 685-4000
Fax: (508) 794-4488
ftp.ftp.com
gopher.ftp.com
www.ftp.com
NETCOM On-line Communications, Inc.
3031 Tisch Way
San Jose, CA 95128
Telephone: (408) 983-5950 or (800) 353-6600
Fax: (408) 241-9145
info@netcom.com
www.netcom.com/support
NetManage, Inc.
10725 North De Anza Blvd.
Cupertino, CA 95014
Telephone: (408) 973-7171
Fax: (408) 257-6405
sales@netmanage.com
ftp.netmanage.com
gopher.netmanage.com
SPRY
CompuServe Internet Division
3535 128th Avenue SE
Bellevue, WA 98006
Telephone: (206) 957-8000
Fax: (206) 957-6000
Spyglass, Inc.
1240 E. Diehl Road
Naperville, IL 60563
Telephone: (708) 505-1010
Fax: (708) 505-4944
www.spyglass.com
When you're adding new functions to your intranet, an important
consideration is the cost of upgrading your client hardware and
software. Keep in mind the lowest common denominator-the least
technologically savvy machine that will utilize the new functions
and the cost of running the application on this machine. Consider
the cost of the software, whether the client will require new
hardware such as speakers or a new video card, and how much it
will cost to install any hardware. Also, consider other hardware
upgrade requirements, such as memory, hard drive storage space,
and a faster processor. Is an operating system upgrade or replacement
necessary? If so, how will a new or upgraded operating system
affect other uses for the client machine? For example, some TCP/IP
software isn't made for Windows 3.1 anymore, and some Windows
3.1 products don't run well or at all on Windows 95. Upgrading
your operating system to lower costs for TCP/IP solutions might
increase your costs if you need to upgrade a whole range of other
products in order to be compatible with the new operating system.
Finally, don't forget the necessary evil: How much will it cost
to maintain this new hardware and software? Who will provide technical
support for the hardware and software? Do you have the infrastructure
in place to handle calls from remote users who are having problems?
Keep in mind that there are companies that provide technical support
on a contract basis.
Although it's likely that the biggest factor in the client arena
is software applications, it might make sense, especially if an
infrastructure doesn't exist, to weigh the benefits and drawbacks
of the different hardware platforms at the same time. One of the
most challenging tasks in building an intranet can be connecting
clients, but hardware and operating system choices can be important
factors in easing that challenge.
| MCKEON & JEFFRIES
|
| McKeon & Jeffries runs a Windows for Workgroups operating system almost exclusively. In deciding which client software to incorporate, one of the biggest issues was cost. This company intends to eventually upgrade to Windows 95, so
free or cheap clients that work well on Windows 3.1 are a good short-term answer because of the expected use of Microsoft Explorer, which comes free with Windows 95.
The accounting firm wanted a feature-rich but inexpensive browser. The answer seemed to be NCSA's Mosaic. For 150 users, the cost of equipping each machine with Mosaic saved thousands of dollars over Netscape's price and didn't lose a lot of features. Of
course, users at home were encouraged to use whatever browser they wanted to purchase or download. NCSA Mosaic was very easy to install, and it left a very light footprint on the client machines, so memory upgrades weren't necessary. (A footprint is
the amount of system resources, such as memory and processing power, that a program takes up on your computer.)
For some time, McKeon & Jeffries had been using Groupwise mail for internal e-mail, and with an inexpensive add-on, they could continue to use it with the new intranet.
The firm decided to use the freeware of CuteFTP to transfer files to and from the server. A feature-rich FTP program, CuteFTP lets users configure multiple hosts, meaning that they can easily put files in their own space on the server, in public space, or
in a specific area with just a click of the mouse.
|
Although the Macintosh enjoys much less popularity in the business
environment, it's much more popular in educational institutions,
where the basis of TCP/IP and client/server applications originated.
Many of the best and most user-friendly client applications were
made originally or exclusively for the Macintosh environment.
The MacOS 7.0 and upgrade versions come with an easy-to-use and
stable TCP/IP stack that gives the user almost plug-and-play connectivity
that is far superior to IBM-compatible PCs. As an example, when
I was preparing a demonstration for a conference, I set up 12
Macs in a TCP/IP network with fully functioning clients in two
hours. The following weekend, when I set up a two-computer LAN
in my home, it took me more than 20 hours to get the network up
and running. Macintoshes are currently a little more expensive
than PCs, but prices have been getting closer to PC standards
over the past year as a result of Apple's trying to increase its
position in the home PC market.
The Macintosh is no doubt the simplest computer system to connect
to the Internet or an intranet, because most models come with
network and modem ports. Users can merely plug in a modem or a
network cable, follow some simple instructions, and be networked
in no time. The Macintosh makes it relatively easy to add hardware
such as modems, additional hard drives, SCSI devices, speakers,
and microphones-as long as that hardware is external. However,
adding internal memory or additional video or sound cards internally
is more difficult than with the average PC. Macintoshes offered
sound capability long before PCs, and they seem to have a better
grasp of how to integrate sound and video into the operating system.
However, Macintosh sound and video quality is no better than on
high-end PCs.
One drawback of choosing a Macintosh system is the limited availability
of commercial software. At most computer superstores, the Macintosh
section is relegated to a remote corner. Also, Macintosh's parent
company, Apple Computers, has experienced financial and management
problems lately, and its future remains uncertain. One good sign
is that Apple has finally licensed its operating system and chip
set to clone makers. Now users don't have to rely on a single
source for OS and hardware upgrades, or even new machines. It's
unlikely that the Macintosh will go away anytime soon, but finding
software applications won't get any easier. Macintoshes have been
able to create a Windows environment and run Windows programs
with limited success.
MacOS is a very stable operating system, and System 7.0 runs well
on 8 MB of RAM. A Macintosh Powerbook that I use with increasing
frequency has 8 MB of RAM, but I wouldn't dare try that on a Windows
95 machine. It does allow for multitasking, meaning that users
can perform several operations at once. Its multitasking is much
better than that of Windows 3.1, and a little better than Windows
95, but not quite as good as Linux or Windows NT.
IBM compatibles, commonly referred to as PCs, are by far the most
common business environment in existing computer infrastructures
and are probably the most common hardware platforms of remote
clients. This is because a number of operating systems are available
for IBM compatibles-all with some form of TCP/IP compatibility.
However, they aren't without disadvantages. Until about a year
ago, it was unusual for PCs to be sold with sound capabilities,
and it's still possible that many remote users won't have sound
or high-quality video capabilities. Also, it's much more difficult
to set up a network socket with a modem, although some operating
systems provide for much easier local network connections (on
a LAN). Plan to spend some serious time supporting remote users
who attempt to connect using a Windows 3.1 or Windows 95 client
and a modem. Troubleshooting network sockets on these two operating
systems is difficult. Dozens of factors, including hardware, network
software, extraneous software, and operating system configurations,
can get in the way of setting up a remote network connection.
When it comes to internal upgrades, including internal hard drives,
video cards, and memory, IBMs are much easier to upgrade than
Macintoshes. However, upgrading with SCSI devices, sound, and
incoming video is more difficult on the PC. Keen competition for
hardware, accessories, and software in the PC market keeps prices
lower and the selection fatter than for similar products for the
Macintosh.
Operating Systems
There are many operating systems for use with IBM-compatible machines.
Some are more limited than others, and some have specific strengths
regarding TCP/IP applications. Depending on what applications
will be used, it's possible for certain users to work on one operating
system while others utilize another. For example, someone who
is administering an intranet might want to use Linux, while a
casual user who requires a suite of other products might want
to use Windows 3.1 or Windows 95. For instance, a user whose primary
occupation is accounting or word processing might want to use
Windows, MacOS, or OS/2 because of the strong applications for
those uses. However, a user who spends most of her time using
intranet or Internet applications might choose Linux because of
its flexibility and stability, even though the word processing
and spreadsheet applications aren't as rich.
Windows 3.1
Although Windows 3.1 (shown in Figure 13.2) is without a doubt
the most widely used operating system in the corporate environment,
it's relatively archaic by modern software standards, especially
given the difficulty it has creating network connections through
modems and LANs. However, much software and many support services
are available for Windows 3.1. Although it's a relatively unstable
platform (it's been known to freeze up when confused, as anyone
who is familiar with General Protection Faults will tell you),
Windows 3.1 runs well on 386 or 486 machines with 4 MB of RAM.
It is a 16-bit operating system that doesn't offer true multitasking,
meaning that you can't perform more than one operation at once
effectively.
Figure 13.2: A Windows 3.1 desktop.
Windows NT
Windows NT, shown in Figure 13.3, is used primarily by high-end
users on high-end machines. It's a 32-bit operating system that
requires a minimum of 16 MB of RAM to run efficiently. It's been
around since 1993 and is the parent of Windows 95. It has exceptional
multitasking capabilities, and it can run most Windows 95 software.
Some of its drawbacks, however, include its difficulty in configuring
for networking and its lack of technical support, except for expensive
support packages. It's very expensive, and it requires a proficient
systems administrator to maintain. NT is currently a favorite
of network administrators and high-powered users with high-end
machines. Microsoft seems intent on supplanting Windows 95 with
Windows NT. In fact, NT 4.0, released in August 1996, uses Windows
95's interface and NT's features.
Figure 13.3: A Windows NT desktop.
Windows 95
Windows 95, shown in Figure 13.4, is probably the most prevalent
operating system for current TCP/IP network clients. By the time
you read this book, there probably will be more clients that work
on Windows 95 platforms than on all the other platforms combined.
Windows 95, a 32-bit operating system, has reasonable multitasking
and connects fairly well to TCP/IP networks on a LAN. It's a little
more difficult to configure Windows 95 for dial-up networking
than for direct networking. In fact, many Internet Service Providers
have complained that Windows 95 makes it difficult for users to
configure modem connections for networks other than the Microsoft
Network. Although Microsoft claims it can run well with 8 MB of
RAM, I have found that it's unbearably slow with less than 12.
Windows 95 probably will be the prevalent operating system for
the next five to 10 years.
Figure 13.4: A Windows 95 desktop.
OS/2
IBM's OS/2 is a little-used but versatile operating system. It's
32-bit, runs well on 8 MB of RAM, and has excellent multitasking
capabilities. It's difficult to configure, but it comes with a
stable TCP/IP stack that works with many ISPs when configured
correctly. OS/2 has its own mail, FTP, Telnet, and Web browser
client, and many Windows 3.1 and Windows 95 clients work well
(although slowly). This operating system lacks supporting software
applications, which is why it's not widely used. However, for
those who would rather line the pockets of Big Blue than Bill
Gates, OS/2 is an acceptable alternative.
Linux
Linux is a versatile noncommercial operating system created mainly
by Internet users, who are constantly upgrading it. It runs efficiently
on a 486 with 8 MB of RAM. It's a true 32-bit multitasking OS,
and it's the most popular graphical interface for UNIX currently
in use. It's available on the Internet for free (even though some
publishers have packaged it with books). Linux is supported by
a vast network of users on Usenet newsgroups. Although non-UNIX
experts find Linux difficult to configure, it's the operating
system of choice for many programmers and systems administrators.
For people who know what they're doing, Linux is the fastest and
most easily customized operating system available. You can find
Linux itself, along with useful installation information, at the
Linux Home Page, located at http://www.linux.org.
| Note |
| Linux was originally developed several years ago by Linus Torvalds, who was looking for a version of UNIX that could be more easily configured, that was able to run on x86 machines, and, most of all, that was free. Linux was built with
UNIX in mind. In fact, many users would be hard pressed to tell the difference. This UNIX system has been developed and debugged as a group effort by volunteers-no single organization is responsible. Anyone with a new convention can send it to Torvalds,
who will test it and possibly include it in the next version. Here is his contact information:
Home address:
Linus Torvalds
Pretarinkatu 2 A 2
00140 Helsinki:
Finland
Work address:
PL 26 (Teollisuuskatu 24)
00014 Helsingin yliopisto
Finland
Telephone number:
+3580 70844265
Home e-mail address:
torvalds@kruuna.helsinki.fi
Work e-mail address:
Linus Torvalds@helsinki.fi
|
Other Operating Systems
A whole host of other operating systems are options for intranet
clients, from archaic Amiga machines to Sun Sparc stations and
Silicon Graphics workstations. Client machines range in price
from less than $1,000 per workstation to more than $20,000 per
workstation. However, unless a systems administrator has extensive
knowledge of the hardware and software being considered, it's
probably not wise to choose an operating system or hardware configuration
that isn't widely used. Although I know that there is an extensive
and fiercely loyal network of Amiga users on the Internet, they
probably don't use their machines for the reliable transmission
of important corporate data.
| THE SPORTING GOODS AND APPAREL ASSOCIATION
|
| The SGAA had very little decision-making authority over what client hardware and software their users would implement to access the intranet. The ISP with whom the SGAA coordinated to provide access to members who needed it also provided
a rudimentary suite of TCP/IP applications. Basic Telnet, FTP, Web browser, and mail clients were included. However, it was recommended that-due to the additional features that are available in these applications-users purchase Netscape as a Web browser,
Eudora for mail, and WSFTP for PC users and Fetch for Mac users as the FTP client.
The differences between the applications that come in the rudimentary suite and the other applications can be likened to the differences between Microsoft WordPad and Microsoft Word. Although WordPad is a capable word processor, it doesn't have the full
features of Word, which means that the user just doesn't get much out of it. For example, with the basic Web browser, users can't view pages in the same style in which Netscape lets them view pages. With FTP, you can do preconfigurations with WSFTP that
you can't do with rudimentary FTP. And, with Eudora, users get an easier and more efficient mail program than those that come with basic packages, which mainly tout their functional attributes. Also, because the SGAA's users work on many platforms, the
company wanted applications that were available on both Windows and Macintosh operating systems
|
As soon as you've chosen client hardware and a network connection,
it's time to consider client software needs. Client software is
what interacts with the server to complete a TCP/IP transaction.
All the software packages discussed here translate requests or
input into a language the server can understand and communicate
with the server via TCP/IP protocol.
If your intranet will host a Web server, users will need a Web
browser client. The Web browser's function is to send file requests
to the Web server and display the information to the client. Browsers
typically show text and images. Some can transfer sound, video,
and other files to the client machine. Many browsers also can
send information back to the server using embedded forms. Users
also can utilize a browser by typing data into online forms to
transmit to the server. New browsers can even run certain applications,
such as Java or ActiveX.
Netscape
Netscape (shown in Figure 13.5) has been, and probably will be
for some time, the single most popular TCP/IP application available.
It's available for MacOS, Windows 3.1, Windows 95, Windows NT,
and most UNIX platforms, including Linux. It runs well on 8 MB
of RAM, and because it incorporates FTP, e-mail, and a newsreader
into the browser, it requires fewer applications to run simultaneously
when performing several functions. Netscape costs about $50 per
user and can be downloaded from the Internet. Beta versions typically
are available for free downloads, although these beta versions
expire occasionally, leaving thousands of users scrambling to
get on the server to download the latest version.
Figure 13.5: Netscape's home page.
Netscape incorporates Sun's Java language into its browser so
that Java applications (or applets) may run inside the browser,
which means that regardless of what operating system the client
is using, an applet can be written to work equally well. Java
is like running an application using Netscape as the operating
system.
Explorer
Explorer, shown in Figure 13.6, is Microsoft's answer to Netscape.
It has many of Netscape's features (see Chapter 19, "Browsers:
Viewing Corporate Information with HTML"). It is free with
Windows 95, and it runs efficiently on 12 MB of RAM. There is
little argument that Netscape is the better browser by almost
any standard. It's fast, it has many features, and it offers more
flexibility to Web content providers. However, Explorer is catching
up. The Web world is still watching to see which application will
dominate the market. Although Explorer has all the power of Microsoft
behind it, some users think it will go the way of eight-track
tapes.
Figure 13.6: Explorer's home page.
OS/2
The OS/2 browser is free with OS/2 and runs efficiently on 8 MB
of RAM. It's primitive compared to Netscape and Explorer (see
Figure 13.7), but it's the only browser to run natively on OS/2.
Figure 13.7: OS/2's home page.
Mosaic
The National Center for Supercomputing Applications' (NCSA) Mosaic
is a relatively full-featured low-end browser (see Figure 13.8).
It's rich enough to cover all the basics, and it runs well on
4 MB of RAM. Mosaic is the basis for many browsers that come with
commercial TCP/IP stacks. It's available on the Internet and costs
about half as much as Netscape. Comparing Netscape to Mosaic is
like comparing Microsoft Word to Microsoft Works: Although Netscape
offers more features and extras, some users just don't need them,
and therefore will find Mosaic suitable.
Figure 13.8: Mosaic's home page.
Probably the most important piece of client software is the e-mail
client. E-mail, used to exchange messages and files, already has
established itself as a commonplace application in many work environments.
The differences among e-mail packages are mainly in their interface
capabilities. All Internet mail is exchanged via Simple Mail Transfer
Protocol (SMTP), a common format for sending mail messages and
files. Most e-mail software uses little of a system's resources,
and some e-mail programs run on the server computer. Applications
running on the client computer download the mail onto the client
computer and allow the user to compose mail locally and then send
it to the server. The current standard for mail servers is Post
Office Protocol 3 (POP3), a mail server that holds mail in an
inbox spool on the server to be either downloaded to the client
machine or read by a server mail tool such as Pine. Pine is an
application that resides on the server and that can be accessed
using Telnet.
The next standard for mail, which is still relatively new, is
Interactive Mail Access Protocol (IMAP). IMAP allows a remote
client to manipulate mail messages in remote folders on the server.
Currently, using POP3, only the inbox on the server can be accessed
by the remote client. IMAP is more useful than POP3 because it
lets remote users manipulate their mail on the server in a graphical
environment using cut-and-paste features on any client while storing
mail on the server instead of on a single client machine.
Eudora
Eudora, shown in Figure 13.9, is the most popular TCP/IP e-mail
package on the market. It's feature-rich and flexible. (See Chapter
30, "E-Mail: The Basic Model.") A freeware version of
Eudora is available, but to access most of the advanced features,
you must purchase the software. Eudora is available for both the
Macintosh and various Windows environments.
Figure 13.9: Eudora's mail package.
Netscape
Netscape's Web browser comes with a mail reader included at no
extra charge. It isn't as feature-rich as Eudora, but it does
provide the basics, such as message composition and storage, address
books, message sorting, and mailbox compression (see Figure 13.10).
Netscape's plus is its savings in system resources, especially
if the user plans to utilize mail and Web browser applications
concurrently. Netscape's Web browser is available for the various
Windows operating systems, the Mac, and most UNIX operating systems.
Figure 13.10: Netscape Mail.
Groupwise
Groupwise, shown in Figure 13.11, is a popular LAN e-mail system
that has a simple add-on for Internet mail. For offices currently
using Groupwise mail, it's easy and relatively inexpensive to
incorporate Internet mail into LAN mail. Groupwise isn't recommended
for offices without established Internet e-mail because of its
lack of features and its inability to conform to new standards
as they evolve. Currently, it's available only for Windows 3.1
and Macintosh systems.
Figure 13.11: Groupwise mail.
SPRY Mail
SPRY Mail, shown in Figure 13.12, is the mail client that comes
with the popular Internet in a Box software. It is a fairly good
mail client, boasting speed and ease of configuration. It has
many of the same features as Eudora but works only with the Internet
in a Box TCP/IP stack. One of its strongest features is its capability
to view the inbox remotely, meaning that you can delete unwanted
messages without downloading them. I recommend SPRY Mail for organizations
that purchase a full suite of TCP/IP applications for users. SPRY
Mail is available only for Windows 3.1 and Windows 95.
Figure 13.12: SPRY Mail.
Pine
Pine, shown in Figure 13.13, isn't really a mail client. It's
actually a program that resides on the server and is standard
with many UNIX-based servers. It gives users the ability to read
and send mail from almost any Internet connection. The mail remains
on the server and can be saved in folders. Pine has many of the
same features as the popular client-side mail tools, such as address
books, search tools, and the ability to attach documents, and
it has the added bonuses of being free and allowing users access
to their mail from almost anywhere.
Figure 13.13: Pine.
File Transfer Protocol (FTP) is a method of transferring files
from a client to a server or vice versa. As with e-mail, files
are transferred over the Internet using TCP/IP protocol. The only
difference between graphical FTP clients and command-line FTP
is the point-and-click features. Additionally, FTP clients use
few system resources.
CuteFTP
CuteFTP, shown in Figure 13.14, is a shareware/freeware program
available on the Internet. It has many features and is used widely.
CuteFTP provides an interface that looks much like a standard
file manager, with the remote file system on one side of the window
and the local file system on the other. Users can simply drag
and drop files from the server to their machine or from their
machine to the server. CuteFTP is available for Windows 3.1 and
Windows 95 systems, but it isn't yet available for the Macintosh.
Figure 13.14: CuteFTP.
Fetch
Fetch, shown in Figure 13.15, probably is the most popular FTP
client available. It's available only for the Mac, and it has
many features. Although PC users have a wide variety of FTP clients
available to them that offer comparable applications and features,
Fetch currently is the best FTP client available for the Macintosh.
I don't know of anyone using another FTP client on a Mac. Fetch
has a premium freeware version available on the Internet. Like
CuteFTP, Fetch works much like a typical file manager, showing
the remote file system and letting users browse their local drives
for files and/or directories. One notable feature of Fetch is
that it lets you upload and download entire directory trees.
Figure 13.15: Fetch.
Command-Line FTP
Windows 95, Windows NT, and all UNIX operating systems come with
a command-line FTP client. Because it doesn't have a graphical
interface, the user must know arcane commands. See Figure 13.16.
Figure 13.16: Command-line FTP.
Telnet clients are used to directly access the server. Users need
a UNIX account on the server to access Telnet. Telnet lets users
edit files and run applications on the server but demands few
system resources. Dozens of Telnet applications (also called terminal
applications) are available on the Web as freeware and shareware.
I'll discuss the two most common Telnet applications-Windows 95
Telnet and NCSA Telnet.
Windows 95 Telnet
This Telnet comes with Windows 95 and Windows NT. It's free but
has few features (see Figure 13.17). (See Chapter 29, "Telnet:
Direct Access," for reviews of popular terminal applications.)
Figure 13.17: Windows Telnet.
NCSA Telnet
NCSA Telnet, shown in Figure 13.18, is freeware and is a universally
popular Macintosh Telnet client. It is feature-rich and uses almost
no system resources.
Figure 13.18: NCSA Telnet.
A couple of the most exciting new applications on the Web are
Internet Phone, which lets users talk, real-time and free of long
distance charges, over the Internet, and Chat, which lets users
carry on conversations real-time by typing messages back and forth
(like chat rooms on America Online or forums on CompuServe). New
clients are arriving on the market on a daily basis to perform
both Internet Phone and Chat functions. Netscape is currently
developing both an Internet phone plug-in in conjunction with
InSoft, Inc. and Chat functions for use with its browser. (See
Figures 13.19 and 13.20.) IBM and Microsoft likely will follow
suit.
Figure 13.19: Netscape Chat.
Figure 13.20: Netscape's CoolTalk plug-in.
Now that you know which materials you need for a solid server,
client, and connectivity foundation, you should have a better
grasp of how you will begin to build your intranet foundation.
Because it's much more expensive and time-consuming to upgrade
client software and hardware than server software and hardware,
many of your decisions probably will be based on an assessment
of your current infrastructure. At this point, you might want
to take an inventory of your current infrastructure or, in the
case of remote users, attempt to gain insight into how technologically
savvy your users are. Keeping in mind the current state of your
infrastructure will help you make decisions as you continue through
this book.
|
