Re: IBM Thin Client and V5R3

[ChadB@xxxxxxxxxxxxxxxxxxxx]

Another option you might be able to use as a workaround would be to set up
a V5R2 partition on a V5R3 box to run Netstation Manager within.  That's
not necessarily a quick fix, but it might buy some time if needed.










If they're using IBM Netstation Manager on the iSeries to run the Thin
Clients it's probably a dead solution at this point.

We experienced the same on our backup iSeries, and had to do some
scrambling to come up with a new solution before upgrading our production
machine.  Netstation manager won't function anymore at V5R3 (it's been
unsupported for a loooong time now...).  I did a good bit of research
before upgrading and never really found any concrete info saying it would
finally break with V5R3.  We even got in touch with a Netstation Manager
consult line expert and he did not have any tricks to get it working again
with V5R3.

We were facing an upgrade to 520s the next month and HAD to get to V5R3 on
those 2 machines.  What we did was keep our Websphere/Domino oriented model
800 at V5R2 and migrated the Netstation Manager profiles to that machine
and used it to run the thin clients for several months (until we researched
and purchased a new thin client solution; we went with IGEL flash cards
that installed in our existing IBM 2200 thin clients).



             kirkg@xxxxxxxxxxx
             om
             Sent by:                                                   To
             midrange-l-bounce         midrange-l@xxxxxxxxxxxx
             s@xxxxxxxxxxxx                                             cc

                                                                   Subject
             04/19/2005 09:54          IBM Thin Client and V5R3
             PM


             Please respond to
             Midrange Systems
                 Technical
                Discussion
             <midrange-l@midra
                 nge.com>






 I upgraded a client from V5R1 to V5R3 last weekend and it broke an older
IBM ThinClient. It boots, downloads it's kernel and gets to the signon
screen. Any signon attempts result in an Authentication Error on the
ThinClient and the message ID of NSC3005. I can't find any errors on the
170 or that msgid out here on the web.  It's the only one they have left
and it's not in a critical place, but I would still like to get it
working...

Any help greatly appreciated
_____________________
Kirk Goins CCNA
Systems Engineer, Manage Inc.
IBM Certified iSeries Solutions Expert
IBM Certified iSeries e-Business Infrastructure
IBM Certified Designing IBM e-business Solutions
Office 503-353-1721 x106 Cell 503-577-9519
kirkg@xxxxxxxxxxxxx      www.manageinc.com

There are 10 types of people in the world:
Those that understand binary, and those that don't.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_____________________________________________________________________________


Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________



ForwardSourceID:NT0001E83A

_____________________________________________________________________________

Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________


_____________________________________________________________________________

Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


ForwardSourceID:NT0001E866

_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For 
more information please visit http://www.ers.ibm.com
_____________________________________________________________________________