If you are using Windows Vista or Windows 7 and need to map a drive to an iSeries IFS directory you will need to follow the steps below:
- Open the Local Security Policy editor: Start – Run – “secpopl.msc” – Ok
- If a User Account Control window appears, click [Continue].
- Expand Local Policies – Security Options
- Double-click “Network security: LAN Manager authentication level”
- Change the value to “Send LM & NTLM – use NTLMv2 session security if negotiated”
This is documented on IBM’s website: http://www-01.ibm.com/support/docview.wss?uid=nas2bb4cf3cc6d1a859e862573900041ed36.
Another install-related issue concerns installing from the
applied System i PTF. Once the PTF is applied, you can install
this service pack or complete merged image from the network
share called QIBM on your System i. Accessing this share uses
the LAN Manager component of Windows, and NetServer support
on the System i. In Windows Vista, Microsoft has changed the
default negotiation method for such connections, so that, at
this time, accessing shares on the System i may fail. One way
to work around this problem is to change a policy setting on
the PC. This action requires administrator authority, and can
be performed as follows:
1) Click Start, click All Programs, click Accessories, click
Run; then type "secpol.msc" (without the quotes) in the
Open text box, and click OK.
2) If a User Account Control dialog box appears. verify that
the details shown match the request you initiated (you are
starting the Microsoft Management Console), and if so,
3) From the Local Security Settings console tree, expand
Local Policies, then click Security Options.
4) In the right pane, scroll down to the setting called
"Network security: LAN Manager authentication level
Properties" and double-click it.
5) Note the current value. The default value at the time of
this writing is "Send NTLMv2 response only". If the value
is not as follows, change it to be:
"Send LM & NTLM-use NTLMv2 session security if negotiated"
then click OK, and exit the Local Security Settings
console. You should now be able to access network shares
on the System i.
The last issue related to install has to do with installing
from a network share. Testing has shown that, in some cases,
installing System i Access for Windows on a Windows Vista PC
from a network share fails. In such cases, copying the files
from the network share to the PC’s local hard disk, then
re-starting the installation from the local hard disk,
Alternatively, you can map a drive to the network share in a
Command Prompt box that was opened as administrator and start
the installation from the mapped drive.
To open a Command Prompt box as administrator, click Start,
then All Programs then Accessories, right-click the Command
Prompt icon and choose Run as administrator. This action will
prompt you to allow the Command Prompt program to run elevated.
At the Command Prompt, type in the following command to map the
net use X: \server_nameshare_name
where X: is the drive you want to map, server_name is the
network server’s name and share_name is the name of the shared
directory. If you are installing from a System i, you would
net use X: \system_i_nameQIBM
Then change to the mapped drive in your Command Prompt box and
run the setup program from there. If you are mapping a drive
to the QIBM share of your System i, these are the steps you
should follow for a 32-bit installation of System i Access
for Windows V6R1:
If you are installing on AMD64 or on Itanium hardware use
Image64a or Image64i instead.
The cause of this failure is being investigated.