v
Verify
that
the
resources
of
the
PC
are
free
of
address
or
interrupt
request
(IRQ)
conflicts.
Operations
Console
uses
addresses
in
the
range
of
192.168.0.0
to
192.168.0.255
.
If
you
run
any
software
that
makes
your
PC
SOCKS-enabled,
check
your
SOCKS
configuration
and
make
sure
that
the
entry
is:
Direct
192.168.0.0
255.255.255.0
A
SOCKS-enabled
PC
accesses
the
Internet
through
a
firewall,
such
as
Microsoft
Proxy
Client,
Hummingbird
SOCKS
Client,
or
others.
v
Verify
that
the
system
name
and
the
local
console
name
are
correct.
v
If
you
are
using
Ethernet
for
your
network,
you
can
use
a
crossover
cable
to
directly
connect
the
PC
to
the
adapter
temporarily.
This
will
isolate
the
PC
and
system
from
any
potential
problems
on
your
network
that
might
interfere
with
proper
operations.
Note:
A
crossover
cable
is
a
standard
network
cable
but
has
the
transmit
and
receive
signal
wires
reversed.
This
virtually
allows
each
end
to
act
as
if
a
hub,
switch,
or
router
is
between
them.
Console
fails
to
connect
and
port
detection
fails:
If
your
console
fails
to
connect
and
your
port
detection
fails,
here
are
some
possible
reasons.
v
Sometimes
RealPlayer
or
RealJukebox
interferes
with
port
detection
and
usage.
v
Some
PDA
drivers
or
software
may
also
prevent
connections
or
port
detection.
Performance
degradation
on
local
console:
The
most
likely
reason
for
performance
degradation
is
that
the
communication
port
is
not
running
a
buffered
UART
(Universal
Asynchronous
Receive/Transmit
serial
port
chip).
Go
to
Advanced
settings
for
the
serial
port
and
verify
the
check
mark
is
checked
to
use
a
buffered
UART.
Make
sure
the
Receive
Buffer
setting
is
not
set
to
the
right-most
setting.
If
that
does
not
help
and
you
suspect
that
the
PC
might
not
have
the
buffered
UART,
you
can
try
slowing
down
the
connection
between
the
PC
and
system.
Depending
on
the
operating
system,
you
may
have
to
change
the
registry,
the
DUN
object,
the
phone
book
entry,
or
all
three.
The
problem
when
the
UART
is
not
buffered
is
that
the
high
speed
inputs
data
to
the
UART
faster
than
it
can
handle,
which
causes
a
missed
packet
of
data
resulting
in
a
30-second
retry.
This
can
occur
randomly,
but
will
be
persistent.
The
slower
speed
reduces
the
exposure
to
an
overrun
of
data
and
therefore
no
more
30-second
retries.
Unable
to
make
a
connection
when
infrared
devices
are
installed:
If
the
PC
having
connection
problems
has
infrared
devices,
you
may
need
to
disable
infrared
in
some
cases.
Most
of
these
devices
work
from
COM1
but
fail
to
show
up
as
using
the
associated
hardware
resources.
Some
experimentation
may
need
to
be
performed
to
isolate
the
problem
during
configuration
of
Operations
Console.
Unexpected
disconnections:
If
the
PC,
local
or
remote
console,
or
both,
have
power
management
capabilities,
it
should
have
this
function
disabled.
Most
PCs,
and
especially
notebooks,
reset
the
communications
ports
when
starting
power
management
after
the
specified
time.
This
can
potentially
disconnect
the
established
connection.
Therefore,
a
local
console
that
goes
into
power
saver
mode
might
disconnect
from
the
system
and
disconnect
an
active
remote
console.
Operations
Console
101
Содержание System i
Страница 1: ...System i Connecting to System i Operations Console Version 5 Release 4 ...
Страница 2: ......
Страница 3: ...System i Connecting to System i Operations Console Version 5 Release 4 ...
Страница 8: ...vi System i Connecting to System i Operations Console ...
Страница 120: ...112 System i Connecting to System i Operations Console ...
Страница 124: ...116 System i Connecting to System i Operations Console ...
Страница 125: ......
Страница 126: ... Printed in USA ...
