A Volume Failed To Mount Error Code 6602

enter a title. You can not post a blank message. Please type your message and try again. pierrot10 Level 1 (4 points) Desktops Q: A volume failed to mount (Error code -6602), why? Dear All,Actually I have a problem which does not appear before...I am using a iMac 10.5.8 (update are done) and we are used to mount two external drive following this syntaxe : smb://servername1.domain.ch/sharesmb://servername2.domain.ch/shareFrom that iMac I can not the first share, but now I can not mout the second share which is on a NAS.However I can mount it from another iMac. A colleague also try to mount from my iMac and he could'nt even if you can from his iMac. Then I am sure the problem come from workstation.I can ping it.When I am trying to mount it, it asked me form my password, and then it retunr me that error:"A volume failed to mount, The volume "[name]" could not be mounted"Then I gopt another window error:"Sorry, the oeration could not be completed because un unexpected error occurred. (Error code -6602)"I searched on the web, but I have not found a suitable solution.I hope you can help me with this matter.Cheers Posted on Feb 29, 2012 1:39 AM I have this question too Close Q: A volume failed to mount (Error code -6602), why? All replies Helpful answers by pierrot10, pierrot10 Feb 29, 2012 2:05 AM in response to pierrot10 Level 1 (4 points) Desktops Feb 29, 2012 2:05 AM in response to pierrot10 What it's interresring to know. I opened a terminal and tried to ping from the troubling workstation.I go that message:" bash: ping: command not found "Surprising that the command ping is not found. May be there is a relation? Helpful (0) Reply options Link to this post by BDAqua, BDAqua Feb 29, 2012 1:18 PM in response to pierrot10 Level 10 (123,710 points) Feb 29, 2012 1:18 PM in response to pierrot10 Can you ping it using Nework Utility? By Name or IP?Some possible cures...http://ericfickes.com/2009/01/a-volume-failed-to-mount-error-code-6602/http://computerplumber.com/2008/11/mac-os-error-code-6602/http://old.nabble.com/AFP--6602-Error-Code-td18810315.htmlhttps://discussions.apple.com/thread/1892913?start=0&tstart=0 Helpful (0) Reply options Link to this post by pierrot10, pierrot10 Mar 1, 2012 1:16 AM in response to BDAqua Level 1 (4 points) Desktops Mar 1, 2012 1:16 AM in response to BDAqua Hello,None of them help. I can not mount it using the IP adressBut now I wund

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody https://discussions.apple.com/thread/3770565?tstart=0 can ask a question Anybody can answer The best answers are voted up and rise to the top OSX 10.5 Leopard to Failover Clustered Windows FIle Share Error 6602 up vote 0 down vote favorite 1 I have set up a failover-clustered file share on a pair of Windows Server 2008 R2 Machines. This setup is working very well with all http://serverfault.com/questions/245295/osx-10-5-leopard-to-failover-clustered-windows-file-share-error-6602 of the Windows clients that I know of, as well as with Macs running 10.6 Snow Leopard. However, the Macs on our network that are running 10.5 Leopard are not connecting as they should. I don't expect that the failover-clustered part of the equation is causing any issues, but I thought that in the off chance that it may be causing issues, to include it here to provide a hint to whoever is willing to help. When a machine running Leopard attempts to connect, it trys for a bit, then asks for the username and password to connect with (as expected). The username and password are entered (correctly), and almost immediately it comes back with the message A volume failed to mount. The volume "Home" could not be mounted. When that box is dismissed, it continues to attempt to connect for a short time, then it comes up with this unexpected error: A couple of Google searches have not come up with anything (for me) about Error code -6602. Any ideas what this error may be, and/or how I should go about fixing

AFP file share from a LaCie disk (or other netatalk server), Mac OS X gives and error, "Failed to mount volume" with "Error code -6602". http://www.macfreek.nl/memory/LaCie_AFP_Mount_Fails Alternatively, while trying to mount using the shell command mount, mount_afp returns "AFPMountURL returned error -5014, errno is 89". Cause The cause is the same in both cases, the file system contains https://www.afp548.com/forums/topic/1054-clients-cannot-smb-mount-10411-xserve/ special files and folders, called .AppleDB .TemporaryItems .DS_Store .AppleDesktop. These folders are present on the netatalk server and contain data necessary for some older Mac files (e.g. resource forks, type and creator a volume codes). However, the data in these folders may sometimes get corrupt and the volume will refuse to mount. Workaround This workaround deletes the resource fork of your data. If possible, mount the volume in some other way, for example using SAMBA. (If you first mounted afp://myserver.example.org/volumename, now mount smb://myserver.example.org/volumename instead). Backup (copy to a local disk) the hidden folders, such as .AppleDB .TemporaryItems .DS_Store .AppleDesktop a volume failed Remove the hidden folders .AppleDB .TemporaryItems .DS_Store .AppleDesktop Unmount the SMB disk Remount it using AFP Caveat: Check Your Data After you followed the above workaround, the resource fork of your data is deleted. Again, part of your data is permanently gone. Now, this may not be as bad as it sounds, as the main data is located in the data fork, not in the (deleted) resource fork. However, before overwriting anything or deleting your backups, do check the integrity of your data. Stuff like pictures, movies, text files will probably be fine. However, you should check files in older formats. In particular check things like font files or any pre-OS X stuff you may still have laying around. Retrieved from "http://www.macfreek.nl/memory/index.php?title=LaCie_AFP_Mount_Fails&oldid=5015" Categories: Bug ReportsSystem MaintenanceMac OS XHardware Navigation menu Personal tools Create accountLog in Namespaces Page Discussion Variants Views Read View source View history More Search Navigation Main Page Categories Recent changes All Pages Tools What links here Related changes Special pages Printable version Permanent link Page information This page was last modified on 24 January 2012, at 00:55. Content is available under Creative Commons Attribution 3.0 Netherlands unless oth

› 10.5.4 clients cannot smb mount 10.4.11 XServe This topic contains 4 replies, has 2 voices, and was last updated by mose 8 years ago. Viewing 5 posts - 1 through 5 (of 5 total) Author Posts August 29, 2008 at 4:25 pm #373945 moseParticipant No 10.5.4 clients can mount smb shared folders on 10.4.11 XServe, but 10.4.11 clients have no problems. Here are the details. 1. XServe 10.4.11 is bound to 2003 AD. 2. All clients, including 10.5.4 clients, are bound to AD. 3. All servers and clients are in the same AD domain. 2. OD is not used for anything. 3. XServe provides smb shared folders, and ACLs allow AD users to access the folders. 4. The smb shares can be mounted by 10.4.11 clients and Windows XP clients. 5. The same shares cannot be mounted by any 10.5.4 clients. A user can log into a 10.5.4 client with AD credentials. At the point in the login process where the "Home folder" is mounted with the path from the profile in AD, a dialog box appears with the message A volume failed to mount. The volume "XYZ" could not be mounted. If the share is mounted manually with Go->Connect to server…, the same dialog is displayed, and then a second dialog box is displayed with the message Sorry, the operation could not be completed because an unexpected error occurred. (Error code -6602) At the same time, /var/log/system.log shows the error lwMountWithArrayOfPaths: failed to mount prefPath=smb://xserve.example.com/XYZ, error=13 I have changed the owner and group (and permissions) of the shares to no avail. Allowing Everyone full access does not help. As a test, I created a local account in Netinfo on XServe and smb shared a folder that is accessible by the local account. I logged into a 10.5.4 client with AD credentials, and manually mounted the new share, authenticating with the local (Netinfo) account. That was successful. So, at some level, smb sharing is working. The 10.5.4 clients can access shares on Windows servers without any problems. Any suggestions or ideas of things I can check would be much appreciated. Thank you! 😀 mose August 29, 2008 at 5:23 pm #373948 plochnerParticipant In my experiences, Kerberos is not passed correctly from 10.5.x clients to the 10.4.x Xserve. This was supremely frustrating, especially around the 1st quarter of this year when you couldn't buy a new mac that had Tiger still installed on it (ie they all came with Leopard). Here is how I came up with a workaround. Log into the account as usual. Open up the Kerberos app (System/Libary/Core Services) You should see your Kerberos ticket listed there. De