Re: NetWare 5 Pure IP Login Across Subnets

[Joe Pinkus]

Seth, By default, Novell IP clients discover IP services via multicast. Unless some other method is configured, ip clients will try attempt to discover the server by multicasting SLP packets. By default, IOS Routers will filter mutlicast packets.   Router Solution: Enable "ip multicast-routing" and enable "ip pim" under each respective interface. Novell Workaround #1 >From Novell Documenet: 2944038   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. Novell Workaround #2 >From Novell Document 2944038 Load SLPDA.NLM on the NetWare 5 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 directoy 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 2943614. Joe   Seth Wilson wrote: We have a Netware 5 server -- IP plus IPX, for our CNE lab work -- whose IP address is 10.0.0.99 and a client -- IP only -- whose address is 198.56.78.13.  The server's subnet connects to E0 on a 2501 -- address 10.0.0.2.  The client's subnet connects to E0/0 on a 3801 -- address 198.56.78.1.  The 2501 and the 3801 are back-to-back and all machines across the board can ping cleanly by name or address. When I move the client to the server's subnet and set its IP to 10.0.0.13, login works just fine.  So login over IP is okay.  But when it's on 198.56.78.13, the client reports it can't find the tree or server.  But as noted, it can ping the server by name or address.  So I conclude that the problem is the broadcast that starts the login process. I set E0/0 on the 3801 to "ip helper-address 10.0.0.99" and still cannot login.   From the packets I captured, it looks like the initial broadcast is NetBIOS Datagram Service, which I thought ought to be forwarded when the IP helper-address is configured.  I am getting a little out of my depth here if you haven't noticed. Can anybody suggest what else I need to do to get the routers to forward this IP Netware login broadcast? Thanks, ~Seth~