How to create a Directory Agent with NetWare 5.
(Last modified: 09Sep2002)
This document (10014211) is provided subject to the disclaimer at the end of this document.
goal
How to create a Directory Agent with NetWare 5.
Configuration of pure IP and NetWare 5.
Setting up IP only with NetWare 5.
fact
Formerly TID 2943657
Novell NetWare 5.0
Novell NetWare 5.1
symptom
Migrating from IPX to IP.
Migrating from 4.x to 5.x.
Workstations cannot login to NetWare 5 via pure IP.
Workstations dialing in across a Shiva LAN Rover can't connect to NetWare 5 via IP.
Workstations can't connect to a pure IP NetWare 5 server.
Workstations dialing in with NIAS can't log into the NetWare 5 servers.
Changed routers to ip only routers from IPX now they can only login using IP addresses manually.
cause
A Directory Agent (DA) on a NetWare5 server acts as a repository of all the Service Agents that it can "see". When a NetWare5 client boots up using IP, it will look for a DA that can point it to the desired resources on the network.
fix
How to configure a DA:
Load SLPDA on the server, and accept the default configuration. This will automatically create an SLP Scope Unit and an SLP Directory Agent in your tree, and you will be ready to go.
ALTERNATIVELY,
In NWAdmin32, create an SLP Scope Unit, and an SLP Directory Agent.
Under the Configuration tab for the DA select the Host Server.
Under the SLP Scope Units tab add the scope to the Serviced Scope Units.
Then load SLPDA on the server.
When the DA is initialized (i.e. when SLPDA is loaded), the DA server will multicast for all Service Agents (SAs), and will build a table of all responding Service Agents. SAs refresh their information with the DA every hour. See Overview of the SLP Protocol for more information.
document
Document Title: | How to create a Directory Agent with NetWare 5. |
Document ID: | 10014211 |
Solution ID: | 4.0.21369320.2273210 |
Creation Date: | 12Aug1999 |
Modified Date: | 09Sep2002 |
Novell Product Class: | NetWare Novell eDirectory |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.