Related Topics

HOWTO: Backing Up the ILLiad Database
HOWTO: Breaking the User Link in the ILLiad Database
PROBLEM: Cancellations or OCLC Reasons for No are all updating as Other
HOWTO: Changing the Port for Microsoft SQL Server 2000
HOWTO: Changing the size of a field in the ILLData database
See more

Other Support Options

Contact Atlas Systems
Phone Numbers, Support Options, Online Help, and more.
Listserv
Pose a question to other users.

Page Tools

Print this page Print this page
E-mail this page E-mail this page

Feedback

How helpful was this article?
Suggestions:

Revised:January 6, 2006 (mc)
Version:All Client, DLL, AutoUpdater, and Connection Manag
Revision:1
INFO: What Ports are Required to be Open for General ILLiad Use?
January 6, 2006

SUMMARY

Required Ports

In order to allow access to ILLiad and its various component parts, the following ports are required to be open.

Optional Ports

If you plan on using Z39.50 to search your local OPAC from within ILLiad, you will need to check that the ILLiad Client machines have access to the Z39.50 server over that port. This port differs from OPAC to OPAC so you will need to verify that value.

If you want to allow access to your ILLiad Server via Terminal Services, port 3389 should be opened. You can decide if you want to open this to particular ip address ranges or all ip addresses. You can also leave the port open and just turn on Terminal Services on the server as needed.

More Related Topics

PROBLEM: Class Not Registered error when trying to initiate Z39.50 Searching
PROBLEM: Incorrect Queues and E-mail Routing Entries in the ILLiad Client for a Shared Server Site
HOWTO: Enabling Logging on the ILLiad Gateway
HOWTO: Enabling Logging on the ILLiad Web DLL
HOWTO: Increasing the Username field in the ILLiad database
INFO: ILLiad and McAfee VirusScan 8
OCLC ILLiad and Windows Server 2003
INFO: ILLiad and the NVTGC Field
HOWTO: Implementing SSL with ILLiad
HOWTO: Importing a Customized List of Addresses to ILLiad
HOWTO: Importing Pre-ILLiad Copyright Information into your ILLiad Database
PROBLEM: Z39.50 Searching Form gives File Not Found error for Yaz.dll
INFO: Z39.50 Profiles in ILLiad
INFO: Z39.50 Compatibility in ILLiad
INFO: User Request Limits
HOWTO: Updating Across a Multiple Server ILLiad Installation
PROBLEM: I/O Error 32 or Path not Found when opening the Borrowing Request Form
HOWTO: Migrating an ILLiad Database to a New ILLiad Server
PROBLEM: Error Message "Login failed. Reason: Not associated with a Trusted SQL Server connection"
PROBLEM: SQL Server Agent fails when executing job to run ILLiad Connector
ERROR: SQL ERROR: Unmatched '' near TransactionNumber
PROBLEM: EDBEngine Error: Vendor Initialization Failed
Microsoft SQL Server 2005 Compatibility
HOWTO: Changing the Default Request Type for Manually Entered Transactions
INFO: Required ILLiad Server Permissions
HOWTO: Routing Rules Across Modules
BUG: Routing Rules for Borrowing and Doc Del do not work using the ILLiad Connector