Finding eDirectory with DA Discovery
Novell Cool Solutions: Feature
Digg This -
Posted: 15 Dec 2004
What do you do when your Windows Novell Client or ConsoleOne can't find eDirectory for login? One of our readers put the problem this way:
"I'm new to Novell but after several Microsoft virus/spam attacks, I have decided to move my server over to Linux and Novell's eDirectory seemed to be the best I could find. I installed eDirectory on Fedora Core 3 and everything seems to be working. The login is working fine with ConsoleOne on the Linux box, but the Windows Novell Client is not finding it, nor is ConsoleOne on XP. I managed to get in with ConsoleOne on XP but I had to set the tree as SPCC/192.168.0.1 (the IP address of my server)."
The answer to the problem is in the DA discovery. Here's what one of our Forum experts had to say about it:
You need to configure your Fedora box as DA so the windows boxes can see it. Here are the steps to follow:
- Make sure your Fedora box has a multicast route enabled. Novell Client for Windows will multicast for DA discovery
- Test the multicast route with a multicast ping from the Windows box (ping 126.96.36.199). This assumes your Fedore box has only one network adapter. If your Fedora box has a multicast route enabled, it will respond to the ping.
- Open /etc/slp.conf in an editor.
- Uncomment the line net.slp.isDA = True under the DA Specific Configuration section.
- Save the file and quit.
- Restart the slpd service (/etc/init.d/slpd stop ; etc/init.d/slpd
- Bounce the ndsd service (/etc/init.d/ndsd stop ; /etc/init.d/ndsd start).
- Look for a directory agent (slptool findsrvs service:directory-agent). Your Fedora box should show up in the output list.
- Check if NDS is registered with the DA (slptool findsrvs servic:ndap.novell). Your tree should show up in the list.
Next, you need to enable your Fedora box as an SLP DA.
Now test the DA and SA configuration as follows:
At this point your clients should be able to find the DA through multicast detection. If your multicast isn't working, we can tell the clients were to look for the DA, which can also be delivered through DHCP.
There are many specifics to work out in a production environment, like the DA scope, but this is a start. Also, remember that restarting your server will remove things like routes added with the route command, and your slpd daemon won't start unless you use the chkconfig command.
As a final check, make sure you have set multicasting to ON, and you have installed OpenSLP before installing eDirectory. Also, be sure to install OpenSLP 1.0.11, which is the current, stable version. OpenSLP 1.1.5 is available (and ships with SLES9), but eDirectory will not work with version 1.1.5.
You can tell the client where to look for the DA by accessing the Novell Client properties (right-click the red "N" in the system tray and select Client Properties) and clicking the SLP tab.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com