Skip navigation

smb shared files not appearing in DIR listing

269 Views 8 Replies Latest reply: Nov 20, 2012 5:24 AM by etresoft RSS
AHR2426 Calculating status...
Currently Being Moderated
Nov 19, 2012 1:50 PM

I've recently switched to Mountain Lion Server and moved over a large number of windows files. After a few problems with permissions, sorted by the ACL fix, I have anothe strange problem. One of our apps performs a DIR listing for file*.* and for some reason the SMB server reports file not found, even though if the whole file is typed in the DIR search it appears.

 

I need the file to show up on a directory listing with wildcards because the application calls for this. I've proved it isn't the filename of the command because having copied the directory to the local C: drive, the command returns the correct result.

 

Does anyone know if there is a way of fixing this?

 

Here is the output of the windows DIR command against identical files, one on the local drive, and one over the SMB share.

 

C:\Audio1>dir MYR00002*.*

Volume in drive C has no label.

Volume Serial Number is 18DB-DE36

 

Directory of C:\Audio1

 

19/11/2012  20:22           658,248 MYR00002.wav

               1 File(s)        658,248 bytes

               0 Dir(s)  82,869,899,264 bytes free

 

 

Q:\AudioTest>dir MYR00002*.*

Volume in drive Q is AHR-RAID

 

Directory of Q:\AudioTest

 

File Not Found

Mac mini, OS X Server, SMB Sharing
  • etresoft Level 7 Level 7 (23,900 points)
    Currently Being Moderated
    Nov 19, 2012 2:01 PM (in response to AHR2426)

    What do you get if you do "dir *.*"?

  • etresoft Level 7 Level 7 (23,900 points)
    Currently Being Moderated
    Nov 19, 2012 2:10 PM (in response to AHR2426)

    And that looks like what? You were so generous with actual output before...

  • etresoft Level 7 Level 7 (23,900 points)
    Currently Being Moderated
    Nov 19, 2012 4:34 PM (in response to AHR2426)

    For some reason, I was assuming that you were upgrading to Mountain Lion. Did you actually switch from some other system?

     

    DOS does not expand wildcards like other shells. It doesn't expand them at all. It is up to the individual programs to do the expansion. Apparently DOS just passed the wildcard on to the file system, which is going to follow UNIX rules for wildcard expansion. So, get rid of the ".*".

  • etresoft Level 7 Level 7 (23,900 points)
    Currently Being Moderated
    Nov 20, 2012 5:24 AM (in response to AHR2426)

    It would also be a good idea to repost your question (linking to this one) in both the OS X Server and Windows Compatibility forums. There may be people with better ideas who don't frequent this, more general forum.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.