Difficulty Accessing Sub Directories on SMB Shares

I am able to use "connect to server" to connect to shares on our LAN. However, two that I need access to are giving me problems.
I am able to ping and connect to these shares okay. Both by the IP address and by the share's name. Once connected to the servers, I can also access the disks I need on them.
The problem occurs after I connect to the disk on the server. I'm able to see all of the folders on the disk, but when I attempt to open any of them, they are empty.
I'm not getting any errors, they are simply empty. I'm able to see the subfolders and files beneath these fine with my Windows system.
This problem only occurs on a couple of shares. All others work just fine.
Any idea what might be wrong? Thx.

Since you could log onto your Windows machine then this means you have a Domain Account.
First open on you Windows machine open a CMD window and type: ipconfig /all . This will show you want DNS server the Domain is using. You will need to put this DNS manually into your settings on the Mac. Also you have to get an IP assigned for your Mac from the IT department. Plus while still in the the Windows machine find the Time Server that is is using. You will have to use this in your Mac when connecting to this Domain.
Now in the OS X 10.6.x machine follow these steps:
1. Open System Preferences->Network pane and at the top of the pane is "Location" with a pull-down. Use the pull-down to create a custom location (calling it Work), then in the right hand of the pane hit the apply button.
2. Then hit the 'Advanced' button and first uncheck the IPv6 box since Server 2003 doesn't support IPv6. Also while in there put in the IP your IT people gave you machine, the subnet and the router IP (get this information from your IT people).
3. Save the configuration.
4. Then follow the advice in the article Connecting a Macintosh running Leopard (10.5) to SBS 2003. *Important Note*=the Directory Application is now in /System -> Library -> CoreServices folder *
I hope this helps you. Plus you should bookmark the web site MacWindows.com.

Similar Messages

Mac Pro accessing SMB shares on a windows server. After being left on all night, the MP gets "file unavailable" messages when opening files on the share.

Windows Server 2003 accessed by several PCs and Macs without previous incident. This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
"Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
"<filename> could not be found. Check the spelling of the file name and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
Note that these messages are popping up AFTER the user has double-clicked on them to open them. So the files are certainly there and correctly named (and contain only letters, numbers and underscores). After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

Windows Server 2003 accessed by several PCs and Macs without previous incident. This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
"Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
"<filename> could not be found. Check the spelling of the file name and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
Note that these messages are popping up AFTER the user has double-clicked on them to open them. So the files are certainly there and correctly named (and contain only letters, numbers and underscores). After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

Trying to access SMB share, can read but not write, I use the domain account to autenticate and domain account has access to the share. its a samba domain and im a Windows Admin by trade.

I have two I Mac's Intel i7 models.
I have some problems getting them to write files to SMB shares.
The domain user account I use when requested to enter when i first try to connect to the share seems to go though without a problem and it presents me with a list of mounts (shares) I select one and the folder opens, I can read files and copy them but I cant write to any of the folders.
I have also mounted the network locatiosn to a folder from the terminal while also specifying a user name and password to use but this also doesnt allow the specified user account to write data to the share.
I have confirmed the user account can write to the share by having the user do so from a windows box.
any help from any of you mac guys would be great!!!!
Im a windows fan boy / Windows Server based Network Administrator and am slowly becomming a fan of your macs (mainly due to the Unix terminal access letting me realise there is more control to be had than most haters would lead you to believe).
Peace Out

I should add that I originally formatted the problematic drive for FAT32 from the Mac, but then the WinXP computer couldn't see the drive when I plugged it in directly via USB. That's why I went with Seagate's utility to format it.

Windows machines unable to access smb shares

I know many people are having problems with smb on osx server, but my issues seems very basic, so I will try to ask for help here.
Basically, I have set up a single folder for sharing on a Mac Mini running OSX Mountain Lion Server. Directory services are provided by a WIndows 2003 server, and I have joined OSX Server to that, and am able to see all AD users and groups correctly. I have checked the boxes specifying I wish to share as afp, smb and webdav and also made shares accessible to guests.
Now, if I use a mac client, I can correctly browse the afp and smb shares, and the latter work via finder and smbutil as expected, including access via AD users, connection and file transfer.
If, instead, I use a windows client (I tried both Win7Pro and WinXP), while being able to ping the osx server machine, if I try to "explore" (entering \\hostname in explorer) the shares I get a "Network error: impossible to access ..." (approximate translation, sorry ). I tried both using the hostname and the ip address, always getting the same result.
If I try via prompt with "net view \\hostname" I get a System Error 53 (Unable to find network path).
Does anyone know if I am doing anything wrong?
Thanks
Christian

I have done some further testing, and I can report that occasionally, I am able to connect from a windows 7 professional machine by issuing the following command:
net use z:\\hostname\share /user:DOMAIN\username
mostly this command returns a 53 system error, but sometimes I am asked for the user's password and am then able to access the shared folder for a brief time.

Windows 2012 Standard File Server Clustering SMB Share Error: Access is denied.

Hi All,
My setup consist of 2 nodes clustered with File Server role. I can successfully failover role to either node with no issues. But if I try to modify the permissions of any file share on my file server cluster I get the following error: Error
Occurred while updating an SMB share: Access is denied. Access is denied.
Now I played around with the permissions on these shares and noticed that when I add the "everyone" group to these shares with change permissions I can successfully modify the shares with no errors. If I removed the "everyone" group
I get the error. So to tell its like some service or account needs permission to these shares to be able to modify them. I don't want to keep "everyone" group on these shares. Can anyone please shed some light on what group, user,
or service account needs permissions on these shared in order for me to modify these SMB shares without getting Access is denied. Thanks

Hi,
It seems your account don’t have the enough right to modify this clustered folder permission.
More information:
Create a Shared Folder in a Clustered File Server
http://technet.microsoft.com/en-us/library/cc732302.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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!

Problem accessing smb share since change to Windows 8

Hy,
I have a smb share folder on my router (I connect a pen and is shared in the network), with no password.
I am able to access from Windows 7 and Linux, but not from Windows 8.
The reported error is:
The device or resource (SERVER) is not set up to accept connections on port "The File and printer sharing (SMB)".
Which is obviously wrong, since I can access it from other OS.
How can I solve this or get more information on the underlying issue.
I've read several threads in here about similar problems, but nothing worked in my case (services are running, smb-cifs is active and there's no error about IPRStackSize and I turned off firewall and antivirus).
Thanks in advance

is your network public or private? in order to access shares you need to be on a private network in windows 8.
Change Network Status Using Settings Charm
1. Press Windows Key + I combination on the keyboard to reveal the
Settings charm. Now in the bottom, click on the Network icon there. Alternatively, you can click on the
Network icon in the notification area on the
taskbar.
2. Now in the Networks section, right-click over the network whose status you’re looking for to change, select
Turn sharing on or off.
3. Finally, you have the options to select between Private and
Public status for your network. If you select Yes, turn on sharing or connect to devices, the network will be switched to Private status.
<ins class="adsbygoogle" data-ad-client="ca-pub-5950002284129980" data-ad-slot="6708462760" style="width:336px;height:280px;display:inline-block;"></ins>

Unable to access files containing special characters (accents) on a SMB share

I can't access some files on a SMB share.
Those files have one thing in common, that is they contain accented characters (àèéìòù).
I can't access them from finder, terminal, or other softwares.
It works fine when accessing them from a Windows 7 client.
How can I fix this issue?
Is there some SMB option to specify the UTF8 encoding?
In addition, when I create a file with such characters from my mac, the special character shows as ?? on a non-mac client.

it turns out I had way more filenames with accented letters that worked well with MacOS X.
the difference is subtle: those OS X didn't like were like a "composition" of two character (sorry, I don't know the encoding details), that is a vowel and a unicode special character that modifies the previous char adding an accent.
I discovered this while renaming the files from a Windows client, by placing the cursor after "é" in "perché" and hitting backspace, it turned into "perche", and hitting backspace again deleted the "e", turning into "perch".
so I fixed those few invalid filenames.

Issue accessing smb share on Imac os x 10.7

I am have some issues accessing our company smb share. The problem i am having is that when i click on a folder it does not show any content, but if i eject the network drive and reattach it it works.

try this:
(run this in Terminal.app, replace <YOUR_DROPBOX_FOLDER>)
rm <YOUR_DROPBOX_FOLDER>/.dropbox.cache/dropbox-upgrade-3.4.3.tar.bz2
curl -L -o /tmp/Dropbox-darwin-update-3.2.9.tar.bz2 'https://www.dropbox.com/download?plat=mac&meta=1&build=3.2.9'
mv /Applications/Dropbox.app /Applications/Dropbox_backup.app
mkdir -p /Applications/Dropbox.app/Contents
tar -C /Applications/Dropbox.app/Contents -xjf /tmp/Dropbox-darwin-update-3.2.9.tar.bz2
chflags -R uchg /Applications/Dropbox.app
rm -r ~/Library/Application Support/Dropbox/Dropbox.app
chflag uchg ~//Library/Application Support/Dropbox
sudo dot_clean /Library/DropboxHelperTools
(system password might be asked after last command. Type Your password and press Enter. Letters of the password won't be displayed while typing)
some explanation, and future changes when more problems arise:
https://gist.github.com/peter-kolenic/7718b6d75a13c17effd0

"Server Admin" tool does not have proper listing of SMB Share directories

I've been stuck on this one for a while and am looking for any thoughts/help on how to unstick things.
BACKGROUND
I have an SMB share that works (about 10 users banging on it). There are lots of subdirectories to this share and all is fine. The share location is /Users/myshare and I can browse to directories that have the effective path of:
/Users/myshare/mydir1/subdir
/Users/myshare/mydir1/subdir2
PROBLEM
The problem is that Server Admin simply has lost some of the "subdir" directories. It just doesn't think they exist anymore. Specifically, when going into the Server Admin SMB panel under Share Points, I can select my sharepoint and Browse the directory structure.....I might see myshare/mydir1/subdir2 and subdir3 and subdir5, but Server Admin just won't see "subdir1" or "subdir4".
I have checked permissions, and "subdir1" and "subdir2" are identical. I have re-applied permissions and even run mdutil -E on the volume.
Does anyone know any what to force Server Admin to re-index it's listing of a sharepoint???
Message was edited by: mizraith

I ended up filing a formal bug through Apple on this one, as there was definitely and issue with something on the share and how permissions were propagating and Server Admin was pretty much worthless at browsing the share (and setting permissions).
The solution was painful, but basically involved: (a) Cloning the internal server drive and booting off of that. (b) Booting off the external clone, then deleting the entire /Users directory on the the original internal (c) cloning back to the internal drive (thereby replacing the /Users directory). Somehow this re-wrote permissions from scratch and fixed whatever corruption was stuck in the way.

Windows 7 Guest Access to SMB Share

I have a 10.8 server setup. I have a share that is available via both AFP and SMB. I have guest access turned on. Why can't I access this share as a guest using Windows 7? Am I doing something wrong?
Windows 7 client is bound to an AD domain, but the Mac Server is not, it is stand alone.
How can I access the guest SMB share with Windows 7 client?
Thanks!

If lagagnon's suggestion doesn't work, I would say try this:
[global]
client lanman auth = no
client ntlmv2 auth = yes
Where I work we are on an Active Directory in which *only* NTLMv2 is allowed to authenticate, and Samba clients must explicitly set "client ntlmv2 auth = yes" in order for them to connect to shares.

WRT350N - V2.00.20: Write access problem to SMB share from Mac OS X 10.6.2

Hi everyone, i've got a problem trying to write a file on the SMB share of the wireless router WRT350N from a MAC OS X 10.6.2 Finder (but also from a Leopard).
I've got no problem neither reading from mac or writing from win.
I've tried to write by cp command from terminal without problem.
Sorry for my english and thanks everyone,
Mr Proc

Same issue on my WRT610N V2. I am using iMac Intel running 10.6.2. Error -36 prompted when copying files to the USB share disk from the Finder. Working fine when on PC running XP.
Another issue is DDNS can't report the router IP to DynDNS.com although it status that the update is successful and completed. After updated, the router's IP is still different to the IP shown on the DynDNS.com. I need to type the IP manually to the DynDNS.com
Hope the new firmware would fix these problems.
Thanks
Message Edited by rickysuper on 11-27-2009 12:00 AM

Creating a folder on an SMB share using a Mac

Hi everyone,
This is more of a question than a problem I'm trying to solve, really. Though the answer might help me better explain the issue to our security team.
Our environment has multiple Windows file servers, both 2003 and 2008. If one of these SMB shares is accessed from a Mac and the user creates a folder, will the ACLs on the share that are set to cascade actually cascade to this newly created folder? We've had issues in the past where ACLs that are supposedly set to cascade on a shared folder are not present on sub-folders created from Macs.
Next question: if the share resides on a netapp device, do the same rules apply? The Macs are still connecting to these shared folders using the SMB protocol.
All Macs are bound to our 2008 AD domain and use network accounts with local homefolders. The issue seems to happen when one or both of the following things happen:
1. A Mac user copies/creates a folder on a Netapp share and for some reason it doesn’t inherit rights correctly
2. We move the folder from one share on an actual Windows server to the Netapp and it doesn’t take permissions correctly.
Please let me know if you need any other information.

Let's put it this way: I'm asking on a Mac site because the people on non-windows support sites are WAAAAY more interested in talking about problems and solutions involving things other than Windows.
I'm fairly certain that the windows servers ARE respecting their own inheritance rules, barring any major bugs and the like which someone may know about...
The isue isn't with Macs moving shares to a netapp, it's with a share being moved to a NetApp that has folders created by a Mac. Talking with our security team further, it seems the problem may be limited to shares resident on a NetApp or moved from a Windows server to a NetApp.
I was primarily asking to see if anyone knew of any issues with these particular situations or had experienced something similar and had dug into it any deeper with F5 (NetApp vendor).

Difficulty Accessing Sub Directories on SMB Shares

Similar Messages

Maybe you are looking for