| Guest Tracker requires high-speed access
to the database in order to work properly. Internet connections, with
their lower speeds and frequent packet loss and data collisions, are
not generally able to provide that sort of high-speed access. Guest
Tracker also requires a standard drive letter to connect to, not a
network address, making configuration of an Internet location for the
database difficult.
Guest Tracker can not support use of our software across an Internet
connection at this time, but here are some methods that have have
been tried in the past.
|
| 1) |
 Microsoft Terminal Server
The main method of networking several remote locations that has
been used successfully involves a Microsoft Terminal Server network.
Using Terminal Server, it is possible to set up a main computer
(the server) at a central location and workstations at each remote
location.
On the server, set up the Guest Tracker database in one folder.
Then install the Guest Tracker program into a different folder
for each station that will be able to access it.
For example, if there are two remote systems and one server, there
should be four folders: one for the database and three separate
Guest Tracker installations - Server, Remote1, and Remote2. Each
Guest Tracker program should be set up to open the main database.
Each computer that will log on should only use the Guest Tracker
program in the folder specified for its use. There is no way for
two systems to run the same installation of Guest Tracker.
Using this method, all actual database access occurs on the server.
The remote workstations function as keyboards and screens, with
all the real work being done on the server. It is important to
be aware of this and to have a server capable of handling the workload
of however many systems are logging in to it.
This method can be used with modems or Internet connections. |
| 2) |
PC Anywhere
Symantec's PC Anywhere software, and other programs with similar
capabilities, use a dial-up networking or Internet IP connection
method to access your main computer from a remote computer. Essentially,
this turns your remote computer into a screen and keyboard that
are attached to the main computer.
Some Guest Tracker users use this sort of program to access a
main computer while they are away from their property. Although
there are no technical problems with accessing your database in
this manner, any users should be aware that running PC Anywhere
increases the recommended minimum (RAM) memory requirements for
Guest Tracker by 32 MB.
Properties considering this solution should be aware that the
remote computer completely takes over control from the computer
it is connecting to. If the remote computer is logged in, no one
can use the main system. This solution works well if there is one
remote user and one main computer that will not be used while the
remote system is logged in.
This method can be used with modems or Internet connections. |
| 3) |
Virtual Private Networks
Although setting up Guest Tracker to run on a VPN is not difficult,
the bandwidth requirements of Guest Tracker (100mbps minimum recommended)
can not generally be met by the technology available. A single
remote user accessing the database across a VPN will experience
significant speed issues and possibly transmission failures due
to disconnects or time-outs. This may lead to database corruption.
Each additional user slows the transfer more and multiplies the
possibility of failure.
It is strongly recommended that you do not run Guest Tracker on
a VPN.
This method can not be used with modem-access. If you choose to
use an Internet connection, a dedicated T-3 line is recommended. |
| 4) |
Wireless Networking
Properties trying to share a database between different buildings
or between properties that are a short distance apart or between
properties using a satellite link are likely to consider using
Wireless Networking if they are unable to run a regular network
cable between locations.
The lag time involved in a satellite link makes it impractical
to use to network Guest Tracker. Combining a satellite link with
a Terminal Server environment may work, but is an untested configuration.
Currently, most wireless networks use the 802.11b standard, which
has a maximum rate of 11mbps and a practical rate of 7mbps. Guest
Tracker's recommended minimum transfer rate is 100mbps.
New wireless technology uses the 802.11a standard, with a maximum
normal rate of 54mbps. 802.11a equipment may also have a "turbo" or "boost" mode
to bring the maximum transfer rate to 72mbps or faster. Turbo modes
are only effective at fairly short range. Again, the transfer rates
fall short of Guest Tracker's recommended minimum.
Although the higher-speed connections show promise, at this point using a wireless network in conjunction with a Terminal Server
environment (as described above) may be the best
way to connect locations that are within range when a regular network
line can not be run.
Running Guest Tracker on a 802.11a wireless network between two
systems will probably function fine most of the time, although
it will be slower than a normal network connection and runs the
same - although smaller - risk of disconnects and time-outs as
a Virtual Private Network as a result. Each additional computer
will increase the lag time and the risk of failure.
Wireless networking methods all require special equipment and
expertise to set up. |
