Information Technology Reference
In-Depth Information
Table 8-1 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table8-1
Novell IPX: Client Cannot Connect to Server on Same LAN
Possible Problem
Solution
Misconfigured
client or server
Verify that the software on both clients and servers is the current
version, is configured correctly, and has loaded correctly. On
clients, check the network drivers and the configuration specified
in the net.cfg file.
(On servers, make certain that SAPs
1
are being generated
properly and that any NLMs
2
are loaded properly. Use the
track
on
command to monitor routing and SAP activity.
Check the encapsulation on clients and servers to make sure that
they are not mismatched.
For specific information on configuring your client or server,
refer to the documentation provided with the device.
Not enough user
licenses
Make sure that there is a sufficient number of NetWare user
licenses available. Use the Monitor utility screen on a NetWare
server to see the total number of connections available and the
number of connections in use.
Mismatched
network numbers
All servers attached to the same cable must bind to the same
external network number. If there are mismatched network
numbers, packets will not be forwarded properly.
Watch for error messages on the system console similar to the
following:
•
“Router configuration error detected”
•
“Node address claims network x should be y”
These error messages indicate that a server on the LAN has a
conflicting network number.
Node address
is the node address of
the network card from which the incorrect address came.
x
is the
network number specified in packets received from the node.
y
is
the network number configured on the server generating the
error.
All servers on the same LAN must have the same external
network number (if they use the same frame type). If the network
numbers do not match, reconfigure the conflicting server with the
correct external network number.
