I'm running windows 7 on the clients, windows 2008 on the servers, not r2 I've tried the local admin, uac, reconnect and no change options, nothing works... I can't find the cause but only know I have 24 drive mapping GPO's. Microsoft Customer Support Microsoft Community Forums This is more of a workaround then a fix but it works for us... check over here
Regards, Cicely Edited by Cicely FengModerator Saturday, September 08, 2012 1:08 AM Saturday, September 08, 2012 1:08 AM Reply | Quote Moderator 0 Sign in to vote once I reach the Resolution Reset the Novell Client 2 "Name Services" back to its default settings. Document ID:7016890Creation Date:08-OCT-15Modified Date:08-OCT-15NovellClient Did this document solve your problem? The NCP name service should never be deselected.
In this specific environment, SLP was the only configured name service. Error: "Volume ID can not be resolved by the database." seen in DSRepair | Advanced Options | Check Volume Objects and Trustees. If someone ever reads this and needs a data driven logon script to map drives based on group membership or user object OU with logic to handle the errors/ retries then Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
These error code numbers can be categorized as follows: eDirectory and NDS Operating System Error Codes Certain eDirectory or NDS background processes or operations require the use or functionality provided by Cause The status code being displayed is the Windows status code for STATUS_OBJECT_NAME_COLLISION (0xC0000035). MAP ROOT H:=%"HOME DIRECTORY" works for one server but not another. I've enabled 'always wait for network' and no changeRob Szarszewski Saturday, September 08, 2012 3:56 PM Reply | Quote 0 Sign in to vote Hi, Does this occur on some specical
Resolution Try using either a literal drive letter known to be available, to see if that avoids the error. 0x800789ff The eDirectory or NDS client error codes fall in the range of codes numbered -301 through -399 (or FED3 through FDA6). This section includes How do I find error code information? Resolution Use the Windows "Run logon scripts synchronously" policy to force Windows to completely finish running the loginscript(s) before proceeding with starting the user's desktop.See the Novell Client readme section 4.16
Generated Sun, 30 Oct 2016 13:18:54 GMT by s_mf18 (squid/3.5.20) Windows Client Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية eDirectory and NDS Client Error Codes Certain eDirectory or NDS background processes or operations require the use or functionality provided by other eDirectory or NDS servers. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. This will NOT delete the directory or data, just the pointer.) Note: Print Queues associated with this volume object will need to be recreated.
These functions, such as communication and transaction servers, can return operating system specific error codes to eDirectory or NDS. check my blog Bookmark Email Document Printer Friendly Favorite Rating: Error 8804 mapping drives via login scriptThis document (3074628) is provided subject to the disclaimer at the end of this document. I still have to capture errors in the script while mapping and retry for the drives to map successfully but it works. If any of these modules encounter an error, it can be passed on to the ds.nlm.