BACK
TO INDEX PAGE
All of the NetCFax
clients can be installed in several different ways, depending on
what your network offer.
The major factors that can
influence this decision are :
1 - Do you only run
"standard" Windows such as W98, ME, or even W2000, with
no Windows "Server" systems on your network.
2 - Do you have any machines on
your network that run Windows XP Pro with Fast Task Switching (FTS)
enabled.
3 - Does your network have one or
more Windows 2000 or 2003 "Servers", and if so, do these
provide Remote Desktop Sessions (RDP sessions) to the client PC's
under which you want to provide access to a single NetCFax client
installation.
If the answer to 1 is that you
just have standard Windows XP, 2000, Window 98 or even Windows ME
machines only, then your installation type decision is very
easy. You install the fax server on any one machine that has
the modem(s), and the fax clients on as many other PC's as you
wish to provide faxing capabilities to.
In this environment,
the NetCFax client can be configured to use a fixed TCP port for
server notifications if this is required on your network, as each
one has it's own unique IP Address.
If however, you want
to run multiple instances of the fax client on the same
"standard" machine, you must then use dynamic ports on
that machine (only).
Click
here for more information on Fixed -v- Dynamic ports
If the answer to 2 is yes, then
potentially you have a slightly more complex decision to
take. Again, the NetCFax server can be installed on any
machine that has one or more modems installed, including of course
any XP Pro machine that is using FTS. The Fax clients can
also be installed on as many other PC's as you wish to provide
faxing capabilities to. However, with XP Pro and fast task
switching, especially if you only have relatively few PC's on your
network, it makes quite a lot of sense to make the XP Pro machine
the fax server as well. (CLICK
HERE FOR MORE DETAILED INFORMATION ON XP when running the
Fast Task Switching system).
By doing this, you can have the
fax server running in a Windows login account that is password
protected, and also install the fax client on this machine and
have it being run in as many other Windows login accounts as you
wish on the XP Pro FTS machine, each running their own fax client
and connecting to the fax server on that machine. All other
PC's on the network can of course also connect to the fax server
across your network in the normal way.
This even applies if you have
multiple machines running XP Pro with FTS enabled, you simply
install the fax client on each one of these machines, and each FTS
session will be able to run it, and connect to the Fax Server.
In this environment,
the NetCFax client can NOT be configured to use a fixed TCP port
for server notifications if this is required on your network, as
doing so will mean that only one instance of the fax client
installed on that machine can be run at any one time. The
default setting of using of dynamic ports is essential if you want
to use the client in multiple FTS or RDP sessions.
Click
here for more information on Fixed -v- Dynamic ports
If the answer to 3 is yes, then
potentially you have an even more complex decision to take.
Again, the NetCFax server can be installed on any machine on your
network that has one or more modems installed, including of course
your Windows 2000 or 2003 Server. (NB - You cannot run
the Fax Server AND the Fax Clients on the same Windows
Server)
Equally, the Fax clients can also
be installed on as many other (non server) PC's as you wish to
provide faxing capabilities to.
If you decide to install the
NetCFax client on your Windows Server and it is
providing access to the client using Remote Desktop Sessions (using Windows Terminal
Services), you have a little more work to do, at least initially.
The NetCFax client is fully RDP
aware, and a single installation of the client on the Windows
Server can of course be used by multiple RDP sessions
concurrently, (all using different fax login accounts). In
addition to this, you may also install fax clients on other PC's
that do not use the RDP sessions, or even if they do so, but may
also want a locally installed version of the fax client.
In this environment,
the NetCFax client can NOT be configured to use a fixed TCP port
for server notifications if this is required on your network, as
doing so will mean that only one instance of the fax client
installed on that machine can be run at any one time. The
default setting of using of dynamic ports is essential if you want
to use the client in multiple FTS or RDP sessions.
Click
here for more information on Fixed -v- Dynamic ports
BACK
TO INDEX PAGE |
NETCFAX -
Networked fax system