 The NAT table must map to the IP address of the pcAnywhere host.

For this
reason, the host address should be a static internal IP address, unless you can
dynamically update the NAT table and mappings.
 The TCP/UDP ports that pcAnywhere uses to communicate, ports 5631 (TCP)
and 5632 (UDP), must be forwarded through the router. For information on setting up
port forwarding, consult your router manual or the manufacturer's Web site. Several
documents explain port forwarding on specific routers.
 If you have multiple pcAnywhere hosts on an internal network, you need to
assign different TCP/UDP ports for each individual host. For detailed information on
changing these port numbers, read the document How to change the IP ports that
pcAnywhere uses.

If there is a remote computer trying to connect to a host that is not using the standard
pcAnywhere ports (5631/5632), the ports on both computers must be reconfigured so
both computers are using the same ports.
 pcAnywhere remotes need the external IP address of the host's NAT router. If
the NAT router connects to the Internet using Dial-Up Networking, that address is
dynamically assigned by an Internet Service Provider and will probably be different with
each dial-up. pcAnywhere remotes connecting to a host using dial-up in this manner
require that you determine the NAT router's current IP address. For additional
information, read the document How to use pcAnywhere with a Dynamic IP Address or
Domain Naming Service.

At first glance NAS and SAN might seem almost identical, and in fact many
times either will work in a given situation. After all, both NAS and SAN
generally use RAID connected to a network, which then are backed up
onto tape. However, there are differences -- important differences -- that
can seriously affect the way your data is utilized. For a quick introduction to
the technology, take a look at the diagrams below.

More Differences
NAS  
Almost any machine that can connect to the
LAN (or is interconnected to the LAN through
a WAN) can use NFS, CIFS or HTTP protocol
 
to connect to a NAS and share files.
A NAS identifies data by file name and byte
offsets, transfers file data or file meta-data
(file's owner, permissions, creation data, etc.),  
and handles security, user authentication, file
locking
A NAS allows greater sharing of information
especially between disparate operating  
systems such as Unix and NT.
Wires and Protocols
Most people focus on the wires, but
the difference in protocols is actually
the most important factor. For
instance, one common argument is
that SCSI is faster than Ethernet and
is therefore better. Why? Mainly,
people will say the TCP/IP overhead
cuts the efficiency of data transfer. So
a Gigabit Ethernet gives you
throughputs of 60-80 Mbps rather
than 100Mbps.
But consider this: the next version of
SCSI (due date??) will double the
speed; the next version of Ethernet
(available in beta now) will multiply
the speed by a factor of 10. Which will
be faster? Even with overhead? It's
something to consider.
The Wires
--NAS uses TCP/IP Networks:
Ethernet, FDDI, ATM (perhaps
TCP/IP over Fiber Channel someday)
--SAN uses Fiber Channel
The Protocols
--NAS uses TCP/IP and
NFS/CIFS/HTTP
--SAN uses Encapsulated SCSI
SAN
Only server class devices with SCSI
Fibre Channel can connect to the SAN.
The Fibre Channel of the SAN has a
limit of around 10km at best
A SAN addresses data by disk block
number and transfers raw disk blocks.
File Sharing is operating system
dependent and does not exist in many
operating systems.
 File System managed by NAS head unit  
Backups and mirrors (utilizing features like
NetApp's Snapshots) are done on files, not
blocks, for a savings in bandwidth and time. A  
Snapshot can be tiny compared to its source
volume.
File System managed by servers
Backups and mirrors require a block by
block copy, even if blocks are empty. A
mirror machine must be equal to or
greater in capacity compared to the
source volume.

What's Next?
NAS and SAN will continue to butt heads for the next few months, but as time goes on, the
boundaries between NAS and SAN are expected to blur, with developments like SCSI over
IP and Open Storage Networking (OSN), the latter recently announced at Networld Interop.
Under the OSN initiative, many vendors such as Amdahl, Network Appliance, Cisco,
Foundry, Veritas, and Legato are working to combine the best of NAS and SAN into one
coherent data management solution.

For more information, see the technical library.

Home | Sponsors | Links | Technical Library| Contact Us

Copyright 2000-2003, Zerowait Corp

18 Haines Street, Newark DE 19711 302.266.9408