Novell Error Code 886f
Favorite Rating: Error: "Login Script error 886F." (Last modified: 13Aug2004) This document (10065810) is provided subject to the disclaimer at the end of this document. fact Novell Client 4.8 for Windows NT/2000 Novell NetWare 5.1 Support Pack 3 (NW51SP3.EXE) symptom Error: "Login Script error 886F." Users login to NDS sometimes get mappings that fail with error 886F. Getting login script mapping error 886F randomly on login cause 886F is a server error of unknown object. This is similar to a -601 in NDS.In another case Connection in MONITOR.NLM showed Licensed Conn via IP but authentication via IPX Could not Map Root drives but could map drives if not using Map Root. fix 1. In NWADMN32 | User object | Details | Environment tab | Set the Default Server attribute to the proper server. This can be done for multiple users by highlighting them and selecting the Details on Multiple Users option from the File menu. 2. Change drive mappings from old Bindery syntax of server\volume: to the proper full DS context method: i.e. MAP G:=.servername_volumename.ou=name.o=name:users\username If the server you are trying to map a drive to does not hold a replica of it's own server object, run DSREPAIR -XK3, Advanced Options, Repair Local, F10 to accept the defaults. Once it is finished, exit completly out of DSREPAIR and SET DSTRACE=+BLINK and SET DSTRACE=*B. Once FinishedChecking Backlinks=SUCCEEDED, reboot the workstation and try and login again. disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owne
having some problems with edirectory and mapping windows shares. first i'll explain my situation well... I'm having a home network for my parents and sisters which are using Microsofts Active Directory. But i'm suffering from several problems with AD. And I've switched to linux (Ubuntu) by almost a year a go. So I'd like to switch to a Novell domain for my parents and I like to use Novells client on my linux box in the future. Now i'm trying to get familiar with Edirectory on VMware with a Windows XP client, but with my setup it won't map Windows shares http://www.novell.com/support/kb/doc.php?id=10065810 on the Windows clients. I've just installed Edirectory with imanager. That's basicly all I've installed on the server. on Edirectory i ve made a login script wich looks like this: MAP E:=server2\downloadpubliek MAP X:=\\192.168.0.19\Novelluzip The server2 is my running AD Windows 2003 server and the \\192.168.0.19\Novelluzip share is on a Linux box with samba but both of the mappings won't work and fail with the following error: LOGIN-LGNWNT32.DLL-890: https://forums.netiq.com/archive/index.php/t-31470.html The specified server is unknown. LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed. [X:=\\192.168.0.19\NOVELLUZIP] The error code was 886f. The strange thing is when i manualy map these shares (with clicking on the red N and using the Novell map network drive) it just mounts the shares fine without a hitch! so I'm realy confused with this error and I don't know how to fix it Should I install a licence, and how? or is it a SLP problem (wich i didn't touch) or is it a DNS problem??? Please help me pointing in the right direction I realy like to move to Novell, but i have absolutely no experience at all. -- robert114 ab@novell.com17-Mar-2006, 20:28First, eDirectory cannot help you when it comes to drive mappings on ad/windows/m$-stuff at all. Until microsoft opens up their APIs for these types of things there is no legal way to do that kind of operation. The map command is made for creating NCP (Novell) mappings to servers with NCP volumes. These include Netware versions 4+ and Linux servers with NSS volumes. This specifically excludes (afaik) windows because you cannot create NSS volumes on windows. In your login script it is possible to "map" windows n
from GoogleSign inHidden fieldsSearch for groups or messages
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > More login woes... 'Access has been denied' and 'Specified server is unknown' errors on login Want to Advertise Here? Solved More login woes... 'Access has been denied' and 'Specified server is unknown' errors on login Posted on 2006-10-02 Novell Netware 1 Verified Solution 29 Comments 6,167 Views Last Modified: 2007-12-19 The problem described in this question... http://www.experts-exchange.com/Networking/Netware/Q_21919694.html has returned. SHAMU is the main server, and is . EMU is a small, older box that runs nothing but FTP, Here's what I see in the results dialog when I first log into the server. SHAMU LOGIN-LGNWNT32.DLL-890: The specified server is unknown. Your current context is Gainesville.nccer User: bmerc Context: Gainesville.nccer LOGIN-LGNWNT32.DLL-100: Access has been denied. SHAMU LOGIN-LGNWNT32.DLL-890: The specified server is unknown. Your current context is Gainesville.nccer User: bmerc Context: Gainesville.nccer Your current tree is: NCCER-TREE You are attached to server EMU. You are attached to server SHAMU. After this login, I can generally see some but not all of my drive mappings. If I then log in to edir again without rebooting (by using the Netware Login option from the red N menu) I see this: Your current context is Gainesville.nccer Your current tree is: NCCER-TREE You are attached to server SHAMU. After reading some forum notices about these errors, I noticed someone mentioning that uninstalling NMAS worked for them. , so I tried that, but still got the following on rebooting: SHAMU LOGIN-LGNWNT32.DLL-890: The specified server is unknown. Your current context is Gainesville.nccer User: bmerc Context: Gainesville.nccer Your current tree is: NCCER-TREE You are attached to server EMU. You are attached to server SHAMU. I've tried recreating my SLP configuratio