3Com OfficeConnect 3CR100A97, Руководство пользователя

Страница: 152 / 177

12 - 10 C
HAPTER
12: T
ROUBLESHOOTING
Application
Software Problems
The following table lists symptoms of isolated application software
problems that may be observed while using the OfficeConnect Gateway,
possible causes, and possible solutions
.
Symptom Possible Cause Corrective Action
Remote IP network
is not responding
(ex., to PINGs or the
web browser
connection
requests).
(continued)
IP routing table does
not show a route to
the remote network,
indicating a
configuration
problem. One of the following may solve
the problem:
Remote WAN IP addresses are
entered incorrectly. Check the
addresses and reconfigure as
needed.
RIP may be turned off. Set RIP to
Listen mode to automatically learn
routes to remote networks.
A static route or framed route is
needed to reach the remote
network. Add the route and check
the IP Routes web page to
confirm the entry.
No default gateway has been
configured that would allow the
OfficeConnect Gateway to
automatically look for the remote
network. Enable the default IP
gateway option in the remote site
profile.
Symptom Possible Cause Solution
Some application
software doesn’t
work properly. Application may have an
embedded IP address which
causes a problem when NAT is
enabled on the OfficeConnect
Gateway. If you have a static network,
disable NAT and try using
the application again. Do
not disable NAT if your
network is dynamic.
The user name and/or password
for this service provider may not
be entered properly. If you have a static network,
disable NAT and try using
the application again. Do
not disable NAT if your
network is dynamic.
The user name and/or password
for this service provider may not
be entered properly. Make sure that the user
name and password for this
service provider are entered
accurately.