Unable To Attach To A Remote Netware Server (Modems Only); Remote Server Not Found (Ipx) - Black Box LRA001A-R2 User Manual

Issue the IPX mode command update now. This should cause the modem to dial.
If you hear the local Router modem dial but the modems do not connect (use the dialup modemX
status command to see if the connection is established), try disconnecting the phone line from the
Router, connecting it to a normal phone, and placing the call.
Determine if the modem at the other end of the connection answers. If it answers, verify that the
number that you called is the same as the configured phone number using the dialup modemX status
command on the local Router. If it does not answer, verify that you're using the correct phone number
and check the Router at the other end to ensure that it is cabled and configured correctly.
Verify that the Ethernet cable is connected to the appropriate Router network connector.
Possible cause #2—The Router is not dialing the phone when a connection is requested, because it has not
learned about the services available on the network attached through its modem connection.
Suggestions—Issue the IPX mode command, update now. If a modem connection is not already
established, this command should cause the Router to dial. Use the IPX mode sap command to
determine if the service and server name that you require is listed in the display. If it is not, the Router is
not learning about the services on the remote network. This could be caused by a misconfigured
network. Refer to the section about misconfigured networks.
If the service that you require is listed in the SAP display, ensure that the appropriate route to the
service exists using the IPX mode route command. For example, if the SAP table displays the service
and server you require as:
Name Type
JUSTIN FILE SERVER modem0
The IPX modem route command must have a route to network 10 in order to reach the ENG File
Server. It should look something like:
Network
JUSTIN 00000010
If you do not have such a route, the problem may be caused by a misconfigured network. Refer to the
Section C.4.8.
C.4.6 R S
EMOTE ERVER
The NetWare client displays the following message when trying to connect to a remote server through
the Router:
SHELL-XXX-XX:
Possible cause—The local Router has not learned about the services available on the remote network. See
the Possible cause #2 described in the previous problem titled Unable to attach to a remote NetWare
server giving you suggestions about what to do when you attach to a remote NetWare server.
C.4.7 N C
O ONNECTION
The NetWare client displays a message similar to the following message when trying to connect to a
remote server through the Router:
SHELL-XXX-XX:
ASYNC ROUTER AR-P, AR-5, AND SYNC ROUTER USER'S MANUAL
Interface
Interface
modem0
N F (IPX)
OT OUND
a network server could not be found
S A (IPX)
LOTS VAILABLE
no connection slots available
Address
10.000000000001.451
Router/Next
74011fl59a4b
Hops Flg
2 P
Hops Ticks Timer
3 13 20
Flags
P
101