Error: "The Tree or Server cannot be found"

Error: "The Tree or Server cannot be found"
Error only occurs when accessing servers across a router.
Can ping the server, but cannot login by server name
Can login only by IP address
Configuring NetWare Client to Login IP Across a Router

There are three possible solutions:
1. Add server name and IP address entries in the NWHost file on the workstation. The NWHOST file is located on the workstation in the Novell\Client32 directory on Win95 and Win98 workstations. It has samples that are easy to follow.

On an NT Workstation, instead of NWHost the client uses the standard MicroSoft TCPIP host file. Edit the host file to add the server name and address. The path to this file is Winnt/System32/Drivers/Etc/Hosts.

2. Load SLPDA.NLM on the NetWare Server. This defines the server as a Directory Agent. Add the IP Address of the server running the SLPDA.NLM under properties of the client, Service Location Tab, Directory Agent list. Click on the box next to the Directory Agent box labeled "Static." With a static directory agent defined, the client will not multicast for a directory agent, but will send a unicast to the specified directory agent.
For an overview of SLP (Service Location Protocol) and a discussion of Directory Agents, see TID 10014788.

3. Allow multicast packets to pass through the routers. Along with Multicast, all devices that are routing IP between the workstation and the NW server must be PIM enabled. (For NW servers acting as routers load PIM.NLM. For third party hardware routers, see equipment documentation.) PIM stands for Protocol Independent Multicast.

You can refer to TID 2942943 for an explanation of PIM.NLM.

By default the client discovers IP services via multicast. Unless some other method is configured, IP clients will try attempt to discover server by multicasting SLP packets. Most routers filter out Multicast packets by default.

Formerly known as TID# 10016486