Problems that occur with networking can originate for any of several reasons: corrupted hardware or software, bad links, not enough memory, etc.
The following are tips for solving network communication problems.
Check all hubs and repeaters to make sure that they are on.
Check concentrators and look for flashing yellow lights that indicate collisions.
Make sure that all routers are functioning properly and have enough memory. A router with insufficient memory becomes the weak link in the chain and can slow down an entire LAN.
Check the cables for proper termination. Make sure that cables are not running close to sources of interference.
Make sure that the server network board is seated properly and is initializing.
Make sure that a protocol is bound to each board and check the configuration of the network boards. Then shut down the server, turn off the power, and check the actual network board settings:
Make sure that all settings agree with the settings used to load the driver. If you load the driver with an interrupt that conflicts with the board’s setting, the network board cannot broadcast on the network.
Make sure that the node address on the board is a legal address. (Addresses 0 and FFFFFFFFFFFF are reserved; do not use them.)
Make sure that the memory range for the I/O ports and memory addresses do not overlap. If there are conflicts, reconfigure the equipment so that no conflicts exist.
Make sure that network boards do not conflict with other boards, the monitor board, or ports in the server. Make sure that no two pieces of hardware are using the same I/O port, interrupt, or memory address. Avoid interrupts 2, 9, and 15.
Make sure that the network board works correctly; replace it if it doesn’t. Check the lists of certified products at YES CERTIFIED Bulletin Search. Make sure that drivers are the latest versions.
Run VOLUMES at the System Console prompt. If volume sys: is not mounted, mount it. The server does not broadcast to the network until volume sys: is mounted.
Check workstation addresses and server node numbers.
Each node address on the network should be unique. Sometimes you can find the problem by turning off all workstations and then turning them back on one at a time.
Make sure that workstations are using the correct frame type.
Have a user log in to the network from a workstation. In Novell Remote Manager, click the link under the heading in the navigation frame.
If the Connections list shows the user’s login name, the server is receiving and responding to the workstation’s request.
If the workstation receives a “Server cannot be found” error, make sure that the server and workstation are using the same frame type.
If using 10baseT, try using a cross-cable to connect the server directly to the workstation. If this solves the communication problem between the server and workstation, then something on the network is causing the problem.