|
|
|
Can't find Tree
|
Original Message
|
Name: special_ed
Date: December 8, 2006 at 06:16:30 Pacific
Subject: Can't find TreeOS: netware 5.1/xp proCPU/Ram: 256Model/Manufacturer: dell |
Comment: When attempting to login using netware client v4.91 SP3 I am receiving the message that the tree cannot be found. I added the user in the root in nwadmn32.exe and removed all accounts that weren't being used to eliminate any licensing issues. I can manually enter the tree, context, and server but I cannot select them when using the search function. I receive the message once again that there were no trees, context, servers found. I am really at a loss here and would appreciate any help you can provide. Special Ed
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: paulsep
Date: December 8, 2006 at 09:05:42 Pacific
|
Reply: (edit)Couldn't be a problem of Licenses, because at this stage of searching for trees and context, no license is needed. Which version of Netware is running at the server? And further question, did it work in the past? Btw, if the server is running Netware 5.1 and Client uses IP-Protocol only, it will never find the server, the tree or the context by doing a search. Paul
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: wanderer
Date: December 28, 2006 at 10:34:55 Pacific
|
Reply: (edit)"Btw, if the server is running Netware 5.1 and Client uses IP-Protocol only, it will never find the server, the tree or the context by doing a search" that statement is incorrect. NW5 was the first to use ip natively. Perhaps you were talking NW4. Can you ping the server? Doesn't sound like you have a connection... Knowing the correct answer and giving a correct answer, are two different things
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: paulsep
Date: January 21, 2007 at 18:15:32 Pacific
|
Reply: (edit)@wanderer Ups, sorry, you're right. Netware 5.1 is able to work with IP only. @special ad Could also be a router problem. Some routers are blocking the slp protocol on multicast by default. You can start PIM.NLM at the server and try again. If this does not help, you can increase the "Name Resolution Timeout" in the NWclient properties under "Advanced Settings" to 50 (default is 10), if the name server needs more time to resolve names. Paul
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|

|