Extended Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Drive mapping - extended error Windows 7 IT extended error status has been encountered check logs(252) Pro > Windows 7 Networking Question 1 Sign in to vote
Extended Error Text 'error In Device Matching'
Error message: The mapped network drive could not be created because the following error has occurred: An extended error has occurred importing security policy extended error has occurred. Things I have checked: AD account Time/date on server and local machine User account can map them successfully on other PCs Only a problem when
Extended Error Has Occurred
using the fully qualified path to the server. Mapping by IP address works. Flushed and re-populated DNS cache Rebooted multiple times Logon script that normally maps drives is correct Any ideas? Thanks, -Tom Tuesday, March 27, 2012 3:11 PM Reply | Quote Answers 0 Sign in to vote Hi, What the error code or message you get extended error when mapping a network drive in your issue? Is there some event logs related to the issue? You may run “net use” command. For example: To assign the disk-drive device name E: to the Letters shared directory on the \\Financial server, type: net use e: \\financial\letters Meanwhile, please open an elevated command and refresh DNS and reset Winsock. >ipconfig /flushdns >netsh winsock reset Net Use command http://technet.microsoft.com/en-us/library/bb490717.aspx I suggest you post the error code or event logs in the forum. Marked as answer by Arthur XieMicrosoft contingent staff, Moderator Tuesday, April 03, 2012 5:25 AM Thursday, March 29, 2012 8:43 AM Reply | Quote All replies 0 Sign in to vote 1. What you get when you issue net use * \\server\share 2. Would you catch the network traffic by network monitor.... 3. Are there any traces in Event logs? Regards Milos Tuesday, March 27, 2012 6:39 PM Reply | Quote 0 Sign in to vote Hi, What the error code or message you get in your issue? Is there some event logs r
Technote (troubleshooting) Problem(Abstract) 'An Extended Error Has Occurred' When Mapping a Network Drive
Extended Error Has Occurred When Mapping Drive
occurs as a result of invalid credentials being passed on the
Extended Error 32
drive mapping attempt. Symptom When attempting to map a NetServer drive, a message is returned saying extended error information revocation status the mapped drive "cannot be created because of the following error - an extended error has occurred". Cause This error can be returned when the client https://social.technet.microsoft.com/Forums/office/en-US/d960c4ae-d971-40a9-97d5-fc9a9ce1a802/drive-mapping-extended-error?forum=w7itpronetworking PC is sending an invalid User ID (one that does not exist on the IBM i). For example, if the user logs on a Domain with a profile that is different than the user's IBM i ID (and that does not exist on the IBM i). The drive can be mapped successfully by one http://www.ibm.com/support/docview.wss?uid=nas8N1020932 of the following methods: 1) Using the "Connect using different credentials" option from the Windows Map Network Drive GUI, and specifying a valid IBM i User ID. 2) Use a log on script that provides valid IBM i User ID and password. 3) Store valid IBM i User ID and password in Windows Credential Manager. See IBM Technote N1019212 'Connecting a NetServer Drive Automatically When Microsoft Windows XP or Windows 7 Password Is Different Than the IBM System i Password' Cross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.2 Operating System IBM i 7.1 Operating System IBM i 6.1 Document information More support for: IBM i Host Servers Software version: 6.1, 6.1.0, 6.1.1, 7.1, 7.1.0, 7.2, 7.2.0 Operating system(s): IBM i Reference #: N1020932 Modified date: 2015-10-02 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
A Network Drive When mapping a network drive across different domains "An extended error http://ilosys.blogspot.com/2010/03/exended-error-has-occured-mapping.html has occurred" error message. See illustration below: Cause: This http://www.chicagotech.net/netissues/mappingerror1.html is due to diffent login credentials when accessing a mapped drive via VPN to another domain. Resolution: This resolution assumes that the login credentials are correct. By using 'Net Use' command from a command line utility interface. When you use extended error the NET USE command to connect to a share on a server in a domain, the following authentication process verifications take place: => If the client's user name is in the domain's UAS account database, the passwords are compared. If the passwords match, access is allowed to the share. To extended error has connect the user name 'Sam' and giving the mapped drive identifier as 'z', do this: net use z:\\server\share /USER:Accounts\Sam Enter the password for 'Account\Sam' to connect to 'server':password The command completed successfully. net use /PERSISTENT:yes The command completed successfully. To delete the mapped identifier 'x', do this: net use x /delete X: was deleted successfully. More on 'Net Use' command go to this URL: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/net_use.mspx?mfr=true Posted by Fabe & Anne Pinto at 12:08 PM Older Post Home My Profile Fabe & Anne Pinto Pasir Ris, Singapore, Singapore Network Engineer and Human Resource View my complete profile Blog Archive ▼ 2010 (4) ▼ March (1) 'An extended error has occured' Mapping A Network ... ► February (1) ► January (2) ► 2009 (4) ► December (1) ► November (1) ► February (2) ► 2008 (20) ► October (4) ► July (8) ► June (3) ► May (5)
you may receive this message: "The mapped network drive could not be created because the following error has occurred: An extended error has occurred" as shown below. Troubleshooting: If using net use command to map the network, drive, we receive "System error 2457 has occurred. This server's clock is not synchronized with the primary domain controller's clock" message. After checking the time, we found the workstation time is 12 hours behind the domain time server. Using net time command fixes it. Please refer to this post for more details: System error 2457 has occurred. Post your questions, comments, feedbacks and suggestions Contact a consultant Related Topics This web is provided "AS IS" with no warranties. Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.