Highlighted
Absent Member.
Absent Member.
3285 views

Another "The tree or server could not be found" thread

We are getting this error on Windows 7 sp1 (x86_64).

SLP is running on SLES11
SLP settings in both DHCP and set in local client.
I have checked SLP and all the servers are registered to the DA's (we have 2 redundant/load balanced DA's)

The reg "Max Retries Boot Threshold"=dword:00000384" as detailed "http://www.novell.com/support/kb/doc.php?id=7006626" set.

Installed the latest Novell client (according to the readme it has some fixes for this).

Made sure spanning tree is disabled on workstation port (but issue happens on VM's withing VMware as well).

But everything to no avail.

Any other suggestions I could try? Besides waiting before logging in.
Labels (1)
0 Likes
25 Replies
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

To answer my own question:
I have found the culprit, it was the Sophos local firewall blocking xtsvcmgr.exe from communication.

After creating a rule and setting "Max Retries Boot Threshold"=dword:00000078" in the registry the issue was fixed.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

Thank you for the follow-up!

-- eDirectory Rules! Peter www.DreamLAN.com
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

Hi, to come back to this...

It isn't solved. It sometimes works well 4 times in a row, and you can login straight away.
Sometimes you can and have to wait 25 secs or so after the login box pops up before you can login without the error.

So, back to my first question. Any suggestions?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

By "latest client", you are sure you have Client 2 SP3 IR4?

The changes you made in Sophos and the registry appeared to ameliorate but not completely solve the problem? That is, they did have some effect?

On a win7 command line do slpinfo /a and post the results please (with commentary on what the IP addresses are, etc). I wonder if it works Ok when it goes to one of the DAs, and the problem is in trying to get info from the other ...

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

Hi Andrew,

Yes, tried 2sp3IR4. The one released last month.
The changed I made to Sophos and the registry setting *seemed* to help a bit. But could be a coincidence.

I am not on site at the moment, so can't test, but I thought slpinfo didn't work any more on Windows 7, only XP?
But I'll give it a go, Thursday at the earliest.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

https://www.novell.com/support/kb/doc.php?id=7010566

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

OK, I wasn't aware the slpinfo had been reintroduced.
This is the output:

=============== Scope List ===============
ABCSLP

============ Directory Agents ============
DA IP Address Host Name
10.xx.2.10 xxxxxxx.abc.xxxxxxxxxx.xxxx.xx
10.xx.5.20 10.xx.5.20

================= Trees ==================
Tree Name IP Address
xxxxxxxxxxxx_xxxxxx_xxxxxx 10.xx.5.235, 10.xx.5.236, 10.xx.5.240, 10.xx.5.20, 10.xx.5.230, 10.xx.5.236

================ Servers =================
Server Name IP Address
ch----- 10.xx.5.20
PC---- 10.xx.5.230
pr------ 10.xx.5.236
ve---02 10.xx.5.235
ve---03 10.xx.5.234
ve---04 10.xx.5.236

I have made the output anonymous, but all the info is there and is correct.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

We'll need a little commentary from you on that output. So you have two DAs servicing one scope? Those are the primary or only IP addresses for those two servers? Are they in the same subnet?

This is OpenSLP running on pure SLES, or SLP on OES11?

You say above you have set SLP in the client, but are also pushing it out via DHCP? Can you clarify that please, and what exactly are the settings on the client as a result?

I wonder if the issue happens when the client uses one DA for resolution, and is OK with the other ... I see one has no host name showing there.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

Hi Andrew,
Thanks for your help.

One SLPDA is running on a SLES11sp3 server, the other one is running on an OES2 (so SLES10) server.
Both servers only have one IP-address, so this is their primary IP-address. Both servers are in a different subnet, the workstations are in even another.

The reason one shows a DNS name and the other shows an IP-address is that one can be reversed lookupped via an IN-ADDR.ARPA zone in DNS and the other cannot.
I assume the SLPINFO command does a reverse lookup of the SLPDA addresses.

We also push out the SLP information via DHCP, but we added it to the static content of the clients as well to rule out an issue with DHCP.
Having it in the client doesn't seem to make a difference.

The settings in DHCP as well as the static config is this:
SLP Scope = ABCSLP
SLPDA = slpda1.xxx.xxxxxxxxxx.xxxx.xx
SLPDA = slpda2.xxx.xxxxxxxxxx.xxxx.xx

The slpda1 and slpda2 are CNAME records that point to A-records in DNS. We have done this so we can easily move a SLPDA to another server should the need arise.
But I also tried putting IP-addresses in the static content of the client, no change.

I also tried putting only one SLPDA in the config and then the other.
Both settings have the same issue.

Cheers,
Hein
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

I also tried this:
https://www.novell.com/support/kb/doc.php?id=7005241

And if the login fails I get this:
(file is called NOVEAP-0001-mpnotify-DEBUG.LOG)

[NOVEAP-0001-mpnotify-137C-4D0F8] log opened - 15NOV2013 10:02:43.546 - max log size 0KB (0x00000000KB, 0MB)
Logging on process ID 4904 (0x1328): "mpnotify.exe"

[NOVEAP-0001-mpnotify-137C][10:02:43.546] Loaded NOVEAP.DLL 5.0.70.9709 (20130930 00:56) from "C:\Windows\system32\noveap.dll".
[NOVEAP-0001-mpnotify-137C][10:02:43.546] CNovEapdllApp::InitInstance for 0x000007FEF3380000.
[NOVEAP-0001-mpnotify-137C][10:02:43.546] OpenCreateEveryoneMutex for "Global\{6F4BD3D8-2CDB-468C-9AAF-51C530A24D8F}" CreateMutex succeeded; handle 0x00000000000001B0.
[NOVEAP-0001-mpnotify-137C][10:02:43.562] NwEAPAuthenticate called for "xxxxxxxxxxxx", password PRESENT, timeout 5 seconds, flags 0x00000104.
[NOVEAP-0001-mpnotify-137C][10:02:43.562] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:43.562] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (0 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:44.062] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:44.062] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (1 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:44.562] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:44.562] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (1 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:45.062] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:45.062] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (2 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:45.562] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:45.562] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (2 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:46.062] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:46.062] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (3 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:46.562] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:46.562] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (3 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:47.062] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:47.062] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (4 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:47.562] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:47.562] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (4 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:48.062] DoRPCConnect NOVEAP RPC server not running.
[NOVEAP-0001-mpnotify-137C][10:02:48.062] NwEAPAuthenticate DoRPCConnect NOVEAP RPC server not running. (5 of 5 seconds elapsed)
[NOVEAP-0001-mpnotify-137C][10:02:48.062] NwEAPAuthenticate DoRPCConnect failed completely; error 1715.
[NOVEAP-0001-mpnotify-137C][10:02:48.062] NwEAPAuthenticate returning 0x6B3 (1715).


Maybe this is muddying the water and it doesn't have anything to do with the issue at hand...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Another "The tree or server could not be found" thread

NOVEAP is for 802.1 authentication, which I assume is not happening here?

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.