Leopards broken connectivity to smb shares.

I bought Leopard recently and did an Erase and Install on my iMac. Everything seemed to work except ... my iTunes are on a NAS and although I can see the //<Device>/<share>, everything undere that is blank.
(ftp works fine ... except I also have some video files on there of about 5GB and I can't pull them off.)
I have a backup copy of Tiger on a USB drive - I can boot to that and see the NAS without any problems, so it isn't a hardware issue.
I note several others have had similar problems and I was wondering if anyone has a definitive fix for this yet?
As some comments I've read say people have it working, can someone who does have a working smb connection from Leopard to a NAS please let me know the firmware version of your NAS as I'm now at the stage where I'm prepared to blow away mine in an attempt to resolve this problem.

I just installed a Freecome Netdrive yesterday and I had the same issue of connecting to the folder and seeing no data. It was a problem with the user groups defined on the NAS set up. In essence if I connected to the root of the NETDRIVE it would show me all the share but then when I went to click into they were empty. I had to mount one of the individual folders first so that Leopard would ask me a user name and password (which was blank) then once it saved the password in the keychain I unmounted the drive and mounted the root this time I could see the files correctly. Same happened with a windows xp machine so I believe this is nothing to do with Leopard but just with the NAS. To ensure your problem is actually security try to access your NAS via HTTP or FTP and see if you can browse the files. If you can't you have a different problem.

Similar Messages

Does Lion support connecting to SMB shares?

Hi there,
Has anyone else had issues connecting to SMB shares since upgrading to Lion?
I am unable to connect to any previously accessible shares hosted on local Linux or Windows servers.
Thanks,
Bob

For those of you trying to access SMB shares, I found a free and easy solution.
Since a lot of people report they are able to access their NAS using apps other than the Finder itself, I decided to look for a free Lion-compatible File Manager to use instead of Finder.
I have found muCommander ( http://www.mucommander.com/ ) and indeed it works fine. All I did was click on the button highlighted bellow, go to "bonjour services" and select my NAS. It prompted me for my username and password and voilá, it works fine.
I keep Finder for everyday use and just load muCommander when I want to access the NAS. At least now I don't have to start my WinXP VM anymore just to access it.
Hope it helps you all.

Cannot connect to smb share - no error or time out, just keeps going

I searched the forum but could not find a solution.
We have a file server running on a Windows Server 2008. We have several MacBooks with snow leopard installed and the same config. Recently one stopped connecting to the shared drives. It does not provide any error. It just sits at the connecting dialog for as long as you leave it open with no progress. Does anyone know a solution to this? You can ping the file share box. It still works just fine on all other macs.

Try following the step I posted in:
http://discussions.apple.com/thread.jspa?threadID=2140745&tstart=0
And let me know if that helps.
If it doesn't try connecting via IP to your SMB share
Open Finder
Choose "Go" and connect to server
type sb://<ipaddress of the machine you are trying to get to/
And see if it comes up.

Can't connect to SMB share on Windows server from only ONE mac

I have over 20 macs on my network. All are running the same version of the OS. (10.4.9) Almost all of the macs can connect, using SMB, to our Windows 2000 file servers...but only ONE of them can not. When I try from that mac, I get the following error:
"The finder cannot complete the operation because some data in "smb://myservername" could not be read or written. (Error code -36)"
This same mac that has this issue can connect to any of our other Win2K file servers and all my other macs can connect to the server that this mac can't...which is very confusing for me because that tells me that the mac is fine and the Win2K server is fine as well...
Any ideas?

-36 is a bit generic, but usually means the Windows® machine is denying because of bad Password. Have you tried deleting that particular reference/share in Keychain Access and redoing it?

Can't connect to SMB share after upgrade

Just upgraded to 10.9 Mavericks and can no longer connect to our SMB file share on the network. Several of us have tried connecting to it on this machine and all we get is
There was a problem connecting to the server "xxxxxxx.domain.com".
You do not have permission to access this server.
Anyone else having this problem?

I have been searching high and low since yesterday afternoon for an answer to this. My problem is not connecting to an SMB share (well, it was, as the old Cmd+K to connect to the SMB share would close quickly) but instead of the old Mac way of using Cmd+K and the IP address, I simply clicked on the available NAS SMB share under Shared and it is a massively fast connection. The old SMB connection would take minutes to open the next folder. So, connecting as you would under Windows helped fix that problem, BUT...
1. The NAS SMB share times out regularly and you have to eject & reconnect. Annoying.
2. Worse than this is I can not open any documents on the share, only navigate it. I have to copy paste the documents to my local ssd, manipulate, copy back. Any new file I copy on, or edit and copy on, the NAS SMB share I can navigate to and open. But if I try to click a pre-Mavericks existing file, I get "Can not open 'excel/word/acrobat.app' with the -36" error. Total BS.
3. Even more weird, if I click spacebar on ANY file on the SMB Share it will pop up in preview. Double click to open and error message.
4. If I copy a document attached to an email (Outlook 2011) to the server it is corrupt. If I copy the file to local ssd, then to the NAS SMB, the same file works perfectly fine.
This is completely ridiculous and needs a fix immediately. I'm going to try using Reinfire's link right now and see if that helps.
My NAS is a Netgear ReadyNAS 516 (linux/unix OS) I use in my office. Computer is MBPr March 2013.

Windows 7 can't connect to SMB share

Hello, my windows gaming PC won't connect to my shares on my mini server, the server is clean installed just 2 days ago and it worked at first but now it won't even ask for username password it just gives a message that it can't reach the IP address.
I have tried hostname, FQDN and IP and nothing works. but my 2 MacBook Pros have no problem at all, and is maxing the bandwidth of the LAN when transferring files.
I can post a wireshark log if that helps??

Have you tried turning on and off the Filesharing services?
I know sometimes the SMBX portion of OS X Server might crash... so you would have to retart services..

Macs can't connect to SMB shares on Win 2008 Server

My office Macs are running MacOS 10.5.x
The Domain Controller was recently replaced - went from 2000 to 2008
The File Servers are running 2000 and 2003
The Macs were connecting fine when the DC was 2000 but after the change to 2008 when the Macs attempt to connect to either file server via SMB the connection times out. PCs are all fine.
The Macs are using the domain controller as the their time server. Binding to the domain seems to work fine.
Console logs show errors such as "Timed Out waiting on Response"
Help? What else can I check?
- C. Thomas

-36 is a bit generic, but usually means the Windows® machine is denying because of bad Password. Have you tried deleting that particular reference/share in Keychain Access and redoing it?

Can only connect to smb share from Windows as "nobody"

I'm trying to share some folders on my Mac using samba. When I connect from Windows, I do not get asked for a username and password, and I get connected as a guest user (nobody). What do I do to get connected as a real user? I've tried playing with /etc/smb.conf, but I'm not sure what to change.

when you enable smb in haring system preferences on your mac, did you check the box to enable smb on a specific account?
if you did, when you initiate smb from windows try entering
smb://[email protected]
instead of
smb://mac.ip.address

Cannot connect to SMB share as a Registered User, but can connect as guest.

I see all of our company servers in the Shared menu. They all automatically connect as Guest as expected with Leotard's fancy pants new networking stuff.
When I try to connect to a server by clicking the Connect As... button, I am prompted for my Registered User info. I enter it correctly (worked fine in Tiger), and the dialog just disappears without any warnings, and I stay connected as Guest.
I am also unable to authenticate to our Windows box that manages our printers, and I suspect it is the same issue.
As a note, I have already followed to excruciating detail the guidelines for connecting to a Windows network as outlined in this wonderful post: Explanation of Leopard NetBIOS (Windows Sharing) Wackyness With Solutions!

Hi
Check your user name in active directory and at the prompt enter the full name
your.name@activedirectorynetwork and password
If your windows network is properly configured you will be able to access the share and printers with no problems.
Leopard works fine in a properly set up windows AD network, is only a bit problematic with windows network without domain controllers

How to maintain default folder view (broken when leopard clients connect)?

hi there,
we run 10.4 tiger server and have the problem that if 10.5 leopard clients connect to the share their changes to the folder view become the new default for everyone connecting after them. with 10.4 clients the default folder view is looked to the settings of the admin.
is there a way to bring back this feature with 10.5 clients connecting? lock the default folder view of shares?
this question was asked before by andy lowe (http://discussions.apple.com/thread.jspa?threadID=1571877&tstart=45) but never answered.

It's "show view options" in English. Also obtained by typing CMD+J
Those only apply to the top-level folder. Each folder you open uses whatever you've elected to use as the defaults. Select a folder, CMD+J, set the view as you desire, click on Use as Default button. That setting will be used for all windows that you open in the future that have never been opened previously. All other windows that you opened will retain whatever view you previously selected for them.
If you want to reset everything to one view, close all open Finder windows, launch the Terminal app (/Applications/Utilities/), copy & paste this command into the window that pops up,
find ./ -name ".DS_Store" -depth -exec rm {} \;
hit the return key, quit the Terminal app, restart, open a Finder window, CMD+J, set up the view options as desired, click the Use as Defaults button, and close the view options window. Now, every Finder window you open will have this view.
Once you sort this out, see:
Switching from Windows to Mac OS X,
Basic Tutorials on using a Mac,
Mac 101: Mac Essentials,
Mac OS X keyboard shortcuts,
Anatomy of a Mac,
MacTips, and
Switching to the Mac: The Missing Manual, Snow Leopard Edition.
Additionally, *Texas Mac Man* recommends:
Quick Assist,
Welcome to the Switch To A Mac Guides,
Take Control E-books, and
A guide for switching to a Mac.

Invalid Username and Password on 10.7 SMB shares

Getting "Invalid Username and Password" message when connecting to SMB shares hosted off a Mac OS 10.7 Lion machine from Snow Leopard or other OSes? Even though you know you are using the correct username and password? With the new SMB in OS X 10.7 Lion you now have to specify the name of the computer your connecting to IN the username field of the prompt or else it won't connect. Kind of like Windows. Took me a while to figure this out so I figured I'd post this here.
i.e.
instead of:
Use:

Thanks for all of your advices. I want to say:
1. I just created this new database yesterday and created SYS password during database creation from another clinet machine in my office. All connections are working. This is why I don't want to change the password at this moment. If I re-create password file, will this affect another client machine in office to connect to DB as sysdba?
2. From server, I can connect. I used the same sys/syspassword as sysdba. If the password is wrong, I would not be able to connect from server.
3. When I tried to connect from remote client machine, I do connect with string like: SQL:> conn sys/syspassword@mydb as sysdba. But it didn't work and return ORA-01017 error.
4. I have other 4 databases on different servers. I can connect from the same remote client machine through SQLPLUS and TOAD with sys as sysdba and system.
Please advise more. Thanks.

SMB Share with Access Based Enumeration & Mac OSX 10.8/10.9

Hello,
I've been working on a bit of a problem related to some SMB Shares on Windows Server 2012 with Access Based Enumeration with Mac OSX 10.8 & 10.9.
Basically, we have one network share that mounts for all of our Students & Faculty on campus. Then, based on which security group the user is inside of in Active Directory, they gain access and visibility to different folders. (Basically, if they are members of the graphic design department, they get access to the Graphic Design's folder). All of that is working fine, no problems. From there we have 3 folders that branch off. We have a Distribution, an Open, and a Dropbox folder.
Distribution is setup as a spot for instructors to have full access, students have read access, They're able to drop files into this locations, to distribute them to their students. This folder is working fine, no problems.
Open is setup with everyone read/write access across the board. This folder is setup for students to share data to each other, work on projects, etc. This folder is working as intended, no problems.
Dropbox is the only folder we're having trouble with, i'm assuming because it's settings are the most complex out of the three. The purpose of the drop box is for students to have read/write control over their own content, but not others, and instructors to have read/write over this entire folder.
Now that I've laid out our Setup, the problem we've encountered, is ONLY occurring inside of the Dropbox folder. When I try to Drag/Drop OR Copy/Paste from another location on the computer into the Dropbox folder, I get a permission error. HOWEVER, if I have a file open, and I click "save as" browse to the dropbox folder, I can save the file into that location without any trouble. Also, on our windows computers, with the same exact users, drag/drop & Copy/Paste work normally.
Things I've Tried:
Disabling the .DS_Store - I figured in the drop box, the .DS_Store would be created by the first user who copied a file in, then subsequent users would not have access to the .DS_Store.
CIFS/SMB1 - I've read that SMB2 can cause some trouble while connecting to SMB Shares, so I tried both connecting via CIFS, and also by forcing back to SMB1, with no fix.
Am I missing something with this? I've read a lot about people having trouble connecting to SMB Shares, but for us it had not been a problem up until this point. Does anyone know what a possible fix might be for this? I'm sifting through internet searches right now, trying to find a solution, however MOST of the responses I see are regarding the two things I've already tried.
Any suggestions would be greatly appreciated.
Thanks!

hi everybody
I really need some help so here is a little up !
thanks !

Can't access smb shares after 10.9.5 upgrade

After the upgrade to 10.9.5 (from 10.9.4) I can not anymore access my smb shares on a NAS server (Thecus N3200PRO) dispite the upgrade says that it "improves the reliability of accessing files located on an SMB server". It had the exact opposite effect with my system.
The NAS server is visible, but after I log in no files or folders are shown (finder window is empy). Also to disconnect the smb share it takes much longer than usual.
To access it with cifs protocol does not help, neither.
Also the workaround by Reinfire (Michael Larson in Can't connect to SMB share after upgrade, to use smb1 instead of the upgrade) does not help at all.
Any solution out there?
-- thanks

hi there,
just a wild guess, but have you tried to connect via Terminal?
/sbin/mount_smbfs //userid:password@ip-of-server/name-of-share
or
/sbin/mount_smbfs //userid:password@dns_name-of-server/name-of-share
You need to have administrative privileges on your Mac to execute said command successfully.
For additional information you can enter (while in Terminal):
man mount_smbfs
and
man nsmb.conf
Glad to hear the problem is solved

OSX 10.8 and SMB Shares with Access Based Enumeration.

Hello,
I've been working on a bit of a problem related to some SMB Shares on Windows Server 2012 with Access Based Enumeration with Mac OSX 10.8 & 10.9.
Basically, we have one network share that mounts for all of our Students & Faculty on campus. Then, based on which security group the user is inside of in Active Directory, they gain access and visibility to different folders. (Basically, if they are members of the graphic design department, they get access to the Graphic Design's folder). All of that is working fine, no problems. From there we have 3 folders that branch off. We have a Distribution, an Open, and a Dropbox folder.
Distribution is setup as a spot for instructors to have full access, students have read access, They're able to drop files into this locations, to distribute them to their students. This folder is working fine, no problems.
Open is setup with everyone read/write access across the board. This folder is setup for students to share data to each other, work on projects, etc. This folder is working as intended, no problems.
Dropbox is the only folder we're having trouble with, i'm assuming because it's settings are the most complex out of the three. The purpose of the drop box is for students to have read/write control over their own content, but not others, and instructors to have read/write over this entire folder.
Now that I've laid out our Setup, the problem we've encountered, is ONLY occurring inside of the Dropbox folder. When I try to Drag/Drop OR Copy/Paste from another location on the computer into the Dropbox folder, I get a permission error. HOWEVER, if I have a file open, and I click "save as" browse to the dropbox folder, I can save the file into that location without any trouble. Also, on our windows computers, with the same exact users, drag/drop & Copy/Paste work normally.
Things I've Tried:
Disabling the .DS_Store - I figured in the drop box, the .DS_Store would be created by the first user who copied a file in, then subsequent users would not have access to the .DS_Store.
CIFS/SMB1 - I've read that SMB2 can cause some trouble while connecting to SMB Shares, so I tried both connecting via CIFS, and also by forcing back to SMB1, with no fix.
Am I missing something with this? I've read a lot about people having trouble connecting to SMB Shares, but for us it had not been a problem up until this point. Does anyone know what a possible fix might be for this? I'm sifting through internet searches right now, trying to find a solution, however MOST of the responses I see are regarding the two things I've already tried.
Any suggestions would be greatly appreciated.
Thanks!
iMac, OS X Mountain Lion (10.8.5)

Just thought I'd post this in case it helps someone. This could be the same problem we have (had) here so try this:
When it asks for name and password put this in the name field: sharename\name
So if the share is called "WWW" and your login name is "Bob" you'd put "www\Bob" in the name field and then normal password in the password field.
Works perfectly for us. I cant remember when it started 10.7 or 10.8 but this was the only solution. Hope it helps someone else!

How can I mount an SMB share in the Finder? (Leopard)

In Tiger, I was able to mount a SMB share in the finder and it would be displayed under the "Devices" section. With Leopard, I cant get this to work. Leopard is much easier to browse network shares on my Windows machine under the "Shared" section, but I would still like to have certain folder mounted all the time, preferably on startup.

Works perfectly for me, so let me make sure we're on the same page.
I mount the volume manually, using Connect to Server.
I drag the volume, now appearing in Computer and on the Desktop, to the Devices section of the Sidebar.
I eject the volume, and it disappears from the Sidebar.
I mount the volume again (it could be by browsing for it, through Connect to Server, or through an Automount Maker document)
It appears, without my having to do anything, in the Sidebar.
As far as I can tell, this is what you were aiming for. Am I missing something?

Leopards broken connectivity to smb shares.

Similar Messages

Maybe you are looking for