On 12/30/2015 8:36 AM, Paul Nelson wrote:
A couple of questions - At which point did Ops Nav/iSeries Navigator stop
being able to work with a V4R5 machine? Does anybody have an old copy of the

The old version of the software is on the IFS.
Before telling me that you can't see the IFS, imagine using FTP to
download the image to a PC and installing from that image. I don't
remember that far back, but try /QIBM/ProdData/Access/Windows

Service packs (and maybe the install images?) can also be found at

One of my clients has a V4R5 machine that has been used to store images in
the IFS via mapped drives. A couple weeks ago, they had a power failure, and
the mapping ability went out the window. The newer versions of iSeries
Navigator cannot "see" the TCP servers in a machine that old.

Anybody got a suggestion? I'm stumped, and IBM is no help, even through the
consult line.

I'm going to re-state to make sure I understand.

There's a PC which has Client Access on it.
That PC used to use Navigator to view IFS folders.
Not Windows File Explorer, but Navigator?
That PC didn't change.
But they need another old copy of Client access for it?

There was a power failure and IBM i got restarted.
Nothing changed on the IBM side; no PTFs awaiting delayed apply or
anything. Just an IPL?
cwbping says all services are running. This also indicates that the
network seems OK.

Have they tried using Windows File Explorer to map the network drive?
Assuming the shares are still intact, that should work. If the shares
are not available, then NetServer may not be started. This V4R5 page on
installing OpsNav may help:
http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/index.htm It
has information on NetServer.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].