Mac Os X Error Code 6602
help!! MAC OS Error code -6602 A user was trying to connect to a windows network share and kept receiving MAC OS error code -6602. Strangely enough there does not seem to be much useful information on this error so here is what we found. This error seems to relate to some sort of permissions error when communicating with the Windows network share from OS X. In our case, the user was trying to access the following PC listed in our Active Directory: smb://computername.ActiveDirectory.domain.com/sharename All of our computers on the network follow that same naming convention. Alas when the user would try to connect and authenticate to that specific computer, they would receive MAC OS error code -6602 upon submission of their password. Strangely enough to circumvent this problem we simply changed the SMB connection to the server. Changing it to: smb://computername/sharename
We also found that using the IP fixed the problem as well, but once the ‘normal' naming is used, the problem returned. It is likely that some sort of caching of user credentials or connection settings is causing the problem but at least we got around it. A firewall was not an issue as the internal file server does not run one, and little snitch on OS X was disabled. There is probably a better solution to MAC OS error code -6602, but that worked for us a few times. Another solution we had investigated is here. Our Windows Server was not throwing any errors in the event log when the MAC was receiving the -6602 error, but this may help out others. 7 comments file sharing, Mac, OS X 7 responses to "MAC OS Error code -6602" computeruser.ca January 5th, 2009 at 08:00 I'm getting the same 6602 error using afp to connect to an AFP server on a Linux box that is running netatalk. The error only occurs trying to mount one sharepoint on the server. Other shares on the box mount just fine. The broken share appears to be configured exactly the same as those that work - same owner, group, permissions, AppleVolume definition, etc etc. I've checked everything I can think of. Clearly, something I haven't thought of it preventing the connection. The 6602 error occurs with both Tiger and Leopard (Connect to Server…) so it's not an OS incompatibility. admin January 6th, 2009 at 15:48 I can't stand AFP. If possible, create a new share then copy the files you want to share (that you can't access) to that newly created shared folder. Hopefully that will work. Our problem occurred Mac to PC, but if it is DNS that causes this then t
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 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 http://computerplumber.com/2008/11/mac-os-error-code-6602/ 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 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 http://serverfault.com/questions/245295/osx-10-5-leopard-to-failover-clustered-windows-file-share-error-6602 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 it? mac-osx windows-server-2008-r2 file-sharing failovercluster share|improve this question asked Mar 9 '11 at 17:28 Ryan H 5932815 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted It looks like this is a bug with 10.5. share|improve this answer answered Mar 9 '11 at 18:18 Scott Keck-Warren 1,2751022 Exactly what I needed to figure this out. It is indeed something to do with Failover Clustering. Because it is clustered, it must be accessed by name, and 10.5 tries to connect using the translated IP. The work-around is to connect directly to a share, adding the NetBIOS port number to the mix like so: smb://
to my Mac computer i have noticed error code 6602 mac x. Could you please help me to fix this error with an effective solution? Help Please!!!! The occurrence of error code 6602 mac http://www.macfixz.com/error-code-6602-mac-os-x-get-corrupted-deleted-mac-data-recovered os x is a most common issue and numbers of its users are looking for the easy solution for this. But you don't have to worry anymore as you arrived on the right destination. It seems that http://verteksi.net/soks/2009/02/20/mac-os-x-ja-samba-jaon-error-code-6602/ the error code 6602 mac os x is related to some sort of permission when any user is try to connect Windows network share from os x. While connecting and authenticating the specific computer you may receive error mac os code 6602 mac os x after the submission of password. The presence of this error message in computer is causing many issue such as slow system performance, registry file corruption, improper behaving of installed application and the major one is loss of data. Hence in order to recover the lost data due to this error, you should use Mac data recovery software. Not only in mac os x but this software is compatible with all mac os x other versions. An Introduction to error code 6602 mac os x Although Mac OS X is quite reliable, but still it is not free from glitches. Sometimes, users also have to face error code 6602 mac os x issues unexpectedly. It is one issue that continues to bother irrespective of the Mac versions you might use. Eventually, as a result of it, Mac system fails to process all your request and may crash severely. What more, due to error code 6602 mac os x issue, users also have to face some difficulties while accessing their hard drive files and other installed apps, which really presses a panic button at times. Wait that's not the end, it has also been reported that system's processing speed might get slow and even terminate abruptly, which may result in total loss of saved data on Mac. If you are also in the same situation and looking for error code 6602 mac os x solution then you need not worry because you will find complete guide to fix error code 6602 mac os x issue. error code 6602 mac os x: What are the Causes for Data Inaccessibility There are various reasons behind the emergence of error code 6602 mac os x creating panic situation. Any inconsistencies pertaining to Mac OS X files system might result in corrupt
← Levi ja talviloma tarjosivat lunta sekä pakkasta Outlook 2003 ja juhlapyhät kalenteriin → Mac OS X ja Samba-jaon Error code -6602 helmikuu 20, 2009 | mac, ohjelmistot, ongelmat Reply Finder antaa välillä hieman erikoisia virheilmoituksia, joista ei voi päätellä ongelman todellista syytä. Yritin jakaa Linuxissa levyä OS X:lle Samban kautta, mutta yritettäessä liittää levyä Finderin "Connect to Server" (Omena + K) -toiminnolla osoitteen ollessa muotoa smb://