Resolution The Nal problem is fixed in the Zen 4 updates as of December 2004, problem has not been verified as existing in Zen 6.5FIX for Non-Nal / Zenworks related problems Novell makes all reasonable efforts to verify this information. By monitoring user activities, security events, and critical systems, we provide actionable security intelligence to reduce the risk of data breach. Flag Permalink This was helpful (0) Collapse - Not exactly the same problem-update by lotalaughs / March 16, 2006 8:10 AM PST In reply to: Not exactly the same problem An check over here
Authenticating to server BOND4_SERVER. Experts? Novell makes no explicit or implied claims to the validity of this information. When the customer logs into my machine, it works fine so it is not an account issue.I have tried removing/reinstalling Novell.
Bookmark Email Document Printer Friendly Favorite Rating: Error code 8884, unable to map drive in login scriptThis document (7017882) is provided subject to the disclaimer at the end of this document. www.novell.comIn closing, the fact you don't allow hosts files or "a solution" may mean you will never see this work.Bob Flag Permalink This was helpful (0) Collapse - Resolution (at least SLP is returning the proper Address for the server but clients never attempt to connect on port 524 to that address. I read something about logging into the active directory one time, but haven't been able to find anything on that.Thanks!
Trevor Skinner Reply With Quote « Previous Thread | Next Thread » Bookmarks Bookmarks Twitter Facebook Google Digg del.icio.us StumbleUpon Posting Permissions You may not post new threads You may not Results 1 to 7 of 7 Thread: Handful of computers on campus won't map network drives Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Switch to I am lost as to what else to try. Authenticating to server BOND3_SERVER.
SeeOES 2015 SP1: DNS/DHCP Services for Linux Administration Guide. We provide upfront analysis and planning, and deliver automatic, unattended high-speed Physical-to-Virtual (P2V) or anywhere-to-anywhere workload migrations. Or,3. The following TID led us to the resolution which was to set the client Advance Settings\Bad Address Cache Timeout from the default of "300" down to "0".http://support.novell.com/cgi-bin/search/searchtid.cgi?/10091670.htm This was found after
As a troubleshooting step, replace the server name in the map drive statement with the server's IP address. https://www.novell.com/support/kb/doc.php?id=7017882 Experts? Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended. e.g "map H:=126.96.36.199\VOL1:HOME\BILL"2.
Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. check my blog Changing Bad Server Name Cache timeout, recreated the hosts file, Repaired TCP/IP. Document ID:7017165Creation Date:19-JAN-16Modified Date:19-JAN-16NovellClient Did this document solve your problem? Resolution Correct the name resolution problem, or use the IP address of the server in the MAP statement.Correct the name resolution problem:1.
Discussion is locked Flag Permalink You are posting a reply to: Any Novell? I had the same problem and what I did was go into the NWLink IPX/SPX/NetBIOS Compatible Transport Protocal and change the frame type from auto to Ethernet 802.3 and rebooted. My drives mapped fine with no errors. this content Flag Permalink This was helpful (0) Collapse - LOGIN-LGNWNT32.DLL-890 by bigehill / August 4, 2006 8:55 AM PDT In reply to: Any Novell?
When logging in apart from the master replica server which works 99% of the time the mappings may error with error code 8884 and will not map but the next mapping LOGIN-LGNWNT32.DLL-890: The specified server is unknown. We have tried a lot of the same solutions as above with out sucess.
Results 1 to 10 of 14 Thread: Login mapping error 8884 and slow logins Thread Tools Show Printable Version Subscribe to this Thread… Display Switch to Linear Mode Switch to Hybrid Flag Permalink This was helpful (0) Collapse - Worked for us also by xdeslitx / February 23, 2006 1:21 PM PST In reply to: Resolution (at least in our case) This The posting of advertisements, profanity, or personal attacks is prohibited. Preview post Submit post Cancel post You are reporting the following post: Any Novell?
Learn more about Unified Communications and VoIP Management Deploy or expand Voice over IP (VoIP) Improve VoIP quality of service Maintain VoIP capacity Manage mixed unified communications (UC) Unified communications and Consult your product manuals for complete trademark information. Proffitt Forum moderator / March 7, 2005 3:13 AM PST In reply to: Switched to IP When I reach this point, I make the call to Provo... http://thesweepdoctor.com/the-error/the-error-code-was-8901-novell.html Check for name resolution problems, such as bad DNS records and correct SLP configuration (see TID 7012387).
symptom Error 8884 during login Error message: "LOGIN-4.21.15-430: The following drive mapping operation could not be completed:[ROOT S:=[servername]/[volumename]:] Error code: 8884." cause The problem only occurs if SLP is disabled and Any trademarks referenced in this document are the property of their respective owners. This post has been flagged and will be reviewed by our staff. by R.
Experts? document Document Title: Clients unable to map to server. unclebob2004, I got exactly the same problem, if you know alredy how to solve the problem, please post the solution, or send to me [email protected] in advance.Tony Flag Permalink This was We integrate service management, application management and systems management, to help you improve performance and availability.
There are 3 things that are being tracked down on this problem:1) workstation manager is running before the client login and it may be causing the address to get cached as This TID did not come up related to my searches regarding the error we were receiving with lgnwnt32.dll. Visitdownload.novell.comfor the latest updates. When I log into the system, I receive the same issue.
I would like to say we have recently went under a major VoIP project and have changed the switches to POE switches which is the only major change we have done