![](https://seccdn.libravatar.org/avatar/915019de619bbec0b54555e3c7a46107.jpg?s=120&d=mm&r=g)
On Tuesday 19 February 2008 15:14:07 Roger Oberholtzer wrote:
On Tue, 2008-02-19 at 10:27 +0800, Jonathan Ervine wrote:
I took all the settings from the Windows Novell client login box, which looks very similar to the Linux one. I can ping the machine listed in Server. I also enered the IP address. It made no difference.
It all looks very similar, and uses the same protocols. The configurations are somewhat different though. Typically the client will use Service Location Protocol (SLP) to locate services, such as trees, servers etc. on the network. If pressing the Tree button returns a blank dialog box then this discovery is failing to locate the tree. This could be due to a misconfigured SLP configuration on the client or possibly through eDirectory. This is something your NetWare/eDirectory admins will know more about however.
Failing that, as a long shot you could try seeing if you can locate the tree you need by pressing the Tree button... If after all that has failed you might be needing your NetWare admin to be helping out as they'll know the specifics of the eDirectory/NetWare environment.
If I press the Trees button, nothing happens. The entry box contains the name I used from the Windows Novell login.
Having the name in the Tree box relies on being able to resolve that name to an IP address. Normally, via SLP, DNS, or NDS (which would suggest an eDirectory connection). Obviously if these fail then the tree connection will fail as well. You should really try and find out from your eDirectory admin an IP address of a server holding a [Root] replica. If you have this IP address in the Tree field (or indeed a hosts entry for the treename with this IP address)) then you should be able to browse the contexts. The pressing of the context button to browse contexts has always been the real test of tree connectivity - if this fails the connection has failed, if it works you know you can connect. The first thing to get right is to make sure you can resolve the tree name to an appropriate IP address (i.e. a [Root] replica holder). Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org