Os X Error 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 s
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 have set up a http://computerplumber.com/2008/11/mac-os-error-code-6602/ 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 that it may be causing issues, http://serverfault.com/questions/245295/osx-10-5-leopard-to-failover-clustered-windows-file-share-error-6602 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://fileserver:139/sharename. Thank You, Scott. –Ryan H Mar 9 '11 at 19:12 add a comment|
6602 kaspersky antivirus SubscribeSubscribedUnsubscribe11 Loading... Loading... Working... Add to Want to watch this again later? Sign in to add this video to a playlist. Sign in Share More Report Need https://www.youtube.com/watch?v=KPdkgMA9M3k to report the video? Sign in to report inappropriate content. Sign in Statistics No views 0 Like this video? Sign in to make your opinion count. Sign in 1 0 Don't like this video? Sign in to make your opinion count. Sign in 1 Loading... Loading... Loading... Rating is available when the video has been rented. This feature is not available os x right now. Please try again later. Published on Sep 21, 2016upgrade to snow leopard by downloadupdate snow leopard comboupgrade snow leopard download freeupdate snow leopard downloadupgrade snow leopard without dvdupgrade snow leopard online downloadwill upgrading snow leopard erase everythingupgrade snow leopard from usbupgrade snow leopard free downloadupgrade snow leopard from 10.5.8upgrade snow leopard from 10.6.3 to 10.6.8update snow leopard from os x error 10.6.3 to 10.6.8upgrade to snow leopard from tigerupgrade to snow leopard from 10.4.11upgrade to snow leopard from 10.5.8 freeupgrade to snow leopard from mac os x 10.5.8upgrade snow leopard hackintosh to mavericksupgrade snow leopard hackintosh to lionupdate snow leopard hackintosh to mountain lionupgrade to snow leopard how tocara upgrade snow leopard ke lionupgrade to snow leopard keep filescara upgrade snow leopard ke maverickscara upgrade snow leopard ke mountain lionupgrade to snow leopard keep dataupgrade snow leopard lionupdate snow leopard lionupgrade snow leopard mountain lionupgrade snow leopard mavericksupgrade snow leopard macupgrade snow leopard macbookupgrade snow leopard to mountain lion hackintoshupgrade snow leopard to mavericks freeupgrade snow leopard to mountain lion problems Category People & Blogs License Standard YouTube License Show more Show less Loading... Autoplay When autoplay is enabled, a suggested video will automatically play next. Up next os x error failed to build gem native extension - Duration: 1:32. kaspersky antivirus 2 views 1:32 os x error code 0 - Duration: 1:46. kaspersky antivirus 6 views 1:46 os x error 8003 empty trash - Duration: 1:32. kaspersky antivirus 1 view