Mac Os X Smb Error 6602
enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked berck Level 1 (69 points) Q: SMB error code -6602 Hello,I have a linux server running Samba. I have a general shared folder for everybody, and then limited home directories that are shared. These are can not be browsed. What has happened, is if you try to connect to the server in general, it shows up the list of shared directories. But to get to your home directory, you had to do the following...Go>Connect to serversmb://
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 failover-clustered file share on https://discussions.apple.com/thread/1892913?tstart=0 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, to include it here to provide a http://serverfault.com/questions/245295/osx-10-5-leopard-to-failover-clustered-windows-file-share-error-6602 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| Your Answer draft saved draft discarded Sign up or log in Si
I had no major issues with Leopard. The Dock dissapeared once, and I had a non-reacting keyboard once when waking from sleep mode. Other than that I am a happy Leopard user. https://rolfje.wordpress.com/2007/11/16/osx-1051-update-still-smb-problems/ Up until a few das ago, when I tried to access my newly acquired http://verteksi.net/soks/2009/02/20/mac-os-x-ja-samba-jaon-error-code-6602/ 500GB Iomega Network Storage. The Iomega drive is a network connected drive, formatted as FAT32, and accessible through the samba (SMB://) protocol. With Leopard, I could see the drive in the network, and I could double click on it's shares, but when (if) the share connected, I could not drag files onto it, or see what is on mac os the disk. Unmounting takes ages, and sometimes requires me to "killall -9 Finder". I browsed the net and found quite a few people on forums discussing the same problem. Luckaly, Apple also had payed attention, and put out an update, which I installed just a few minutes ago. Sad thing is, that this update does not solve my problem (yes, that's Dutch you're reading): So I tried all tips I could find mac os x in the forums: Connect using the IP address, rather than the network name Change the group of the device (WORKGROUP changed to NOTIT) Remove any non-alphabetical characters from paswords Remove passwords alltogether Connect using CIFS:// in stead of SMB:// Any combination of the above After previous experience with Apple products I seriously began doubting the samba implementation of the Iomega drive. So I tried some things on the Iomega drive, amongst which were: installing a (wrong) firmware update, which almost bricked it. Resetting to factory defaults Erasing Mac sidecar or meta files (the .DS ones) Formatting the drive completely Unsetting and setting passwords Changing share names to lowercase But still, nothing. Leopard will not properly access this drive. Funny thing is, that when I try to connect to the Iomega drive from my other Mac, which runs Tiger, it works flawlessly. And I can also connect to that same drive from a Windows machine. This makes it clearly a Leopard problem to me, and one that still needs to be fixed, despite the speedy update issued by Apple. Can we have another fix please, Apple? I can't reach my remote rsynced backups until you do… Share:PrintEmailTwitterFacebookMoreRedditLinkedInGoogle Related This entry was posted on Friday, November 16th, 2007 at 02:03 \2\Nov\UTC +0000 and is filed under A
← 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://