Using IBM i Access with Windows Operating Systems
|Windows Operating System||IBM i Access for Windows (5770-XE1)
IBM i Access for Windows (5761-XE1)
iSeries Access for Windows (5722-XE1)
Which releases work with this Windows operating system?
|Windows 8, 8.1 (Professional and Enterprise) Windows Server 2012, 2012 R2
|Windows 7 (Professional, Enterprise and Ultimate)
Windows 2008 R2
32 & 64 bit editions
|II14522The restrictions are in Information APAR|
|Windows 2008 Server||II14391The restrictions are in Information APAR|
32-bit and 64-bit editions
|Vista Home Premium and Home Basic editions are not supported. The other editions are supported with: II14239.The restrictions are in Information APAR|
Tablet PC Edition
|The Operations Console function is not supported on any release of IBM i Access for Windows on the Windows XP Tablet PC Edition. For all other components: Information APAR II14175 states the requirements and restrictions listed in this table entry.The Support Statement in|
|Windows XP Professional x64 Edition|
|Windows Server 2003 x64-based versions|
|Windows Server 2003||Information APAR II13465 for requirements and restrictionsRefer to the Support Statement in|
|Windows XP Professional||
Firewall Information for links to documents on this topic.
Starting with Windows XP SP2, Windows Firewall is enabled by default. Refer to |
Attention Operations Console users: if you use Windows XP, V5R2M0 or later IBM i Access for Windows is required. Refer to the Operations Console home page.
Information APAR II11853
Support Statement in |
Click here to learn about a known problem with Operations Console and Windows 2000 Service Pack 4.
|Windows NT 4.0|
How to acquire the latest service pack for IBM i Access for Windows
A service pack PTF is required for usage of IBM i Access for Windows on some Windows operations systems. Here are ways that you can acquire the latest service pack:
Starting with Windows XP SP2, Windows Firewall is enabled by default. There are two Software Knowledge Base documents with information on enabling IBM i Access for Windows with firewall products:
- System i and Microsoft Windows Firewall: Making It Work
This document provides one solution that will get IBM i Access for Windows functions working through Windows Firewall. Specifically, it show Administrators how to enable the three components that need to accept incoming requests to work: Incoming Remote Command, Operations Console, and Management Central.
- IBM i Access for Windows and PC Firewall Products
This document contains information that is useful for PCs running Windows Firewall or other firewall programs. It provides more detail for advanced users who may want to understand the different ways to enable IBM i Access for Windows functions through firewall programs. The document in "1" above only includes configuring application exceptions through Windows Firewall, and deals only with firewall products that block incoming connections. This document includes configuring port exceptions as well. It also includes information useful when running a firewall program that blocks outgoing connections.
Windows 2000 support - additional information
All releases of IBM i Access for Windows (that is, V4R4M0 and later) were tested with all released versions of Windows 2000. For Client Access Express V4R4M0, service pack SF60698 or later is required. The releases of IBM i Access for Windows that are currently being supported are V5R1M0, V5R2M0, and V5R3M0. Refer to IBM i End-of-service Dates regarding currently supported releases.
Information regarding IBM i on the Windows 2000 operating system:
Information APAR II11853 "Client Access and Windows 2000"
This info APAR contains...
Information APAR II12664 "Known Problems/Restrictions When Using Windows 2000 and NTFS Write Restrictions on Client Access Express Directories (V4R4M0 and V4R5M0)"
Information APAR II11791 "Client Access Express Support on VPN Connectivity"
This info APAR contains requirements for VPN connections, which include the Windows 2000 operating system.
- Call IBM Support Line:
Inside the US