Xerox SmartSend Support & Software User Guide
Problem Solving
SMARTsend
Installation and Administration Guide
Installation and Administration Guide
170
When running on a Windows XP computer, SMARTsend is unable to display all
destinations on the Document Destinations page. Why?
destinations on the Document Destinations page. Why?
IIS on Windows XP is configured out of the box for a maximum of 10 HTTP connections. If installing
SMARTsend on a Windows XP computer and running OCR jobs or jobs with a large page count, the
number of HTTP connections may be exceeded. This may cause SMARTsend to be unable to show all
destinations on the Document Destinations page. The number of HTTP connections can be increased
to 40 (but not higher). To do this, find the adsutil.vbs script on the SMARTsend computer (should be in
c:\inetpub\AdminScripts or similar) and run the following command:
SMARTsend on a Windows XP computer and running OCR jobs or jobs with a large page count, the
number of HTTP connections may be exceeded. This may cause SMARTsend to be unable to show all
destinations on the Document Destinations page. The number of HTTP connections can be increased
to 40 (but not higher). To do this, find the adsutil.vbs script on the SMARTsend computer (should be in
c:\inetpub\AdminScripts or similar) and run the following command:
adsutil set w3svc/MaxConnections 40.
When running on a Windows Server 2003 computer with Service Pack 1,
SMARTsend is unable to display all services on the Configure Service Settings page
and the corresponding destinations on the Document Destinations page. Why?
SMARTsend is unable to display all services on the Configure Service Settings page
and the corresponding destinations on the Document Destinations page. Why?
When SMARTsend is installed on a Windows Server 2003 computer with Service Pack 1 installed and
the computer is configured as a standalone computer (not in a domain), DNS is not always handled
fully by the network infrastructure. That is, the DHCP server does not completely register the hostname.
As a result, services may not be listed on the Configure Service Settings page and the corresponding
destinations will not be available on the Destinations page. To fix this, specify a primary DNS suffix
when configuring the computer name. This can be done with the following steps:
1.
the computer is configured as a standalone computer (not in a domain), DNS is not always handled
fully by the network infrastructure. That is, the DHCP server does not completely register the hostname.
As a result, services may not be listed on the Configure Service Settings page and the corresponding
destinations will not be available on the Destinations page. To fix this, specify a primary DNS suffix
when configuring the computer name. This can be done with the following steps:
1.
At the SMARTsend computer, right click on My Computer and select Properties.
2.
Click on the Computer Name tab.
3.
Click on the Change button.
4.
Specify a Primary DNS suffix when configuring the computer name.
5.
Click OK. Exit out.
6.
Reboot the computer.
My organization’s network does not use a domain. How would we log in to
SMARTsend?
SMARTsend?
In this situation, all SMARTsend users must have local accounts on the SMARTsend computer. Users
would log in to the SMARTsend application using the username and password for their local account.
would log in to the SMARTsend application using the username and password for their local account.
Will SMARTsend work in an Active Directory environment?
Yes. SMARTsend does function within an Active Directory environment. On Windows 2000 and
Windows 2003 domain controller servers, Active Directory is used to create domains. SMARTsend
computers may be members of these domains and users of SMARTsend may be domain users.
Windows 2003 domain controller servers, Active Directory is used to create domains. SMARTsend
computers may be members of these domains and users of SMARTsend may be domain users.
Note:
The fix may not occur immediately. Give the DNS server time to replicate the
information.