6 replies
by jaolson40
Is the bindery context set? The Microsoft client for Netware is not NDS aware, and needs a bindery context set on the server you are trying to attach to to be able to browse its resources. Somebody may have removed the bindery context setting from the AUTOEXEC.NCF and then manually added it afterwards at the console prompt.
Type CONFIG at the console prompt to see if the bindery context is set and what it is set to (a context needs to be set at the container the user object is in. For example, if the user object is .CN=user.OU=cont2.OU=cont1.O=org then there should be a context set to .cont2.cont1.org). If the context is not set then set it at the console prompt using the SET BINDERY CONTEXT = (insert path here). If this fixes the problem, then add the same command to the server's AUTOEXEC.NCF
Hope this helps! :)
by brandonf
Welcome to MS networking. I suspect they need to logout and then login again.
I use only Netware clients, which are much faster. Many people run both at the same time, which I don't find as stable - and it certainly is slower.
I don't know whythe user is deciding which client to use. If user is the expert, let him solve the problem.
good luck, sounds like you'll need it.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending