Filter
Top Products
5-10 A-61588 July 2008
NOTE: Some of the concepts covered in this chapter assume
knowledge of Microsoft NT Domains and permissions. Refer to
your documentation for Microsoft Windows Server 2000 or
Windows Server 2003 for more information.
Scan Station user groups — for network domain environments, the
administrator should create a user group for all Scan Stations. This
group will be used to hold account names that are assigned to each
Scan Station. Minimally, there should be one account name that is
assigned to each Scan Station. Optimally, each Scan Station should be
assigned its own unique username and password and these accounts
should be contained within a group that is reserved specifically for Scan
Stations. These account names will be used when configuring the Scan
Station’s network settings and entered into the Username, Password,
and Network Domain fields.
NOTE: The Scan Station groups and login names must be given
appropriate privileges to access the network resources that the
user will see as Destination choices at the Scan Station.
Workgroup environments — for network environments that use the
Microsoft “Workgroup” configuration, you may minimally be required to
create an account name and password to be assigned to Scan
Stations. These account names will be used when configuring the Scan
Station’s Network settings and entered into the Username, Password
fields. The Network Domain field should be left blank in Workgroup
environments.
Network folders — it is recommended that you create network folders,
for either Destination or Remote Configuration, that can be accessed
(minimally read, write, change access) by any Scan Station login
account or by the user group created for Scan Stations.
UNC names for folders — as an administrator, you will need to know
the fully qualified UNC name for each network folder that will be used
by your Scan Station(s). When configuring network destinations, this
will be the information entered into the Address field of the Destination
Entry dialog box. For example, you could create a folder called
“scanfolder” on a server called “acmeserver” that would be reserved for
Scan Station access. You would reference it by the following UNC
name: \\acmeserver\scanfolder.
NETBIOS usage — in network environments that use routers it is
common practice to block NETBIOS traffic on your router. You may
need to know the IP address of the server to which you want to scan
documents. By substituting the IP address of the server instead of the
NETBIOS computer name, you can bypass the network traffic
restrictions that may cause network scanning to fail. For example, the
previously defined network address: \\AcmeServer\scanfolder should
be replaced with something similar to: \\192.168.2.10\scanfolder.