Re: Replacing a LAN console

id you shut down the windos firewall?

John McKee wrote:

Disasters don't come on a schedule. Came in this morning and the LAN
console computer had died. After multiple boot attempts, it came up
for a few minutes and then died again.

A replacement computer was brought in. I installed Client Access and
the same service pack that I was told to install on the dead computer
last week. Went through the same steps setting up the LAN console as
last week. It would not connect. Called IBM and reopened the PMR
from last week. Got a different person. That may or may not be
relevant.

New pc was set up as DHCP. I changed it to match the old pc. Even
transferred the network cable from old to new pc. No connection.

From front panel, I entered some codes I can't recall. From SST, I

entered some functions as well. Still no connection.

Rebooted the new pc, on advise that something might have changed.
Still nothing.

Bob's last idea was to IPL the i. Talked to my boss. He is planning
on that on Monday morning.

I'm just wondering if Bob might have missed something. I am not
meaning to challenge him. Just no idea what the heck else could be
messed up. I can ping the pc from the i. Pc can ping the i. CWBPING
shows all connections good, except for DDM port.

Since I am dead in the water for this week, I will have time to look
at that manual. And will in a few minutes. I am just curious if
anybody has any obvious ideas. When IBM gets stalled and goes to the
IPL route, I get curious. Last week Anthony consulted with people.
Bob didn't. That does not mean a thing.

John McKee

On Wed, Apr 10, 2013 at 3:48 PM, Pat Barber <mboceanside@xxxxxxx> wrote:

This might of some help in your problem.

http://www-912.ibm.com/s_dir/SLKBase.nsf/DocNumber/502180186

It explains almost all consoles and how to change them, manage them, etc.
Why this isn't shipped with all machines sold remains a mystery to me.




On 4/10/2013 12:00 PM, John McKee wrote:

I gathered I could, based on the screen inquiring if I wanted to take
control. Issue then becomes a matter of communication. The system is
almost totally unmonitored. No dedicated people to serve as
"operators". So even knowing who will be operating is a bit of a
challenge.

--
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.

--
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.