Slashdot Mirror

← Back to Stories (view on slashdot.org)

File Sharing Difficulties Frustrate Tiger Admins

Posted by Zonk on from the catch-the-kitty-by-the-tail dept.

rmallico wrote in to mention a story currently running on Eweek about technical difficulties sites running Tiger are experiencing. From the article: "A number of sites running Apple's new 'Tiger' operating system are experiencing problems with SMB file sharing and authentication with Microsoft's Active Directory, Ziff Davis Internet News has learned. Although Apple Computer Inc.'s Tiger increases support for Server Message Block file sharing and Active Directory, several sources say that the Finder fails to log on to Windows and Linux Samba file servers."

4 of 334 comments (clear)

  1. Re:Oh, right, error code -36! by FidelCatsro · · Score: 5, Informative

    Its actualy very usefull if you have a list of the error codes and what they mean.
    http://www.appleerrorcodes.com/

    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though
  2. Work-around by Noksagt · · Score: 5, Informative

    Easy workaround:
    Command-K to bring up the connect menu and type in the full address INCLUDING THE SHARE NAME:

    smb://SERVER/folder

  3. Not sure if it's this... by mferrare · · Score: 5, Informative
    I had a problem with 10.3 authenticating to a W2k3 AD server and mounting shares. Turned out I had to modify the Domain Controller Security Policy on the server and set Microsoft Network Server: Digitally Sign Communications (always) to Disabled. I am now running 10.4 and I have no problems connecting to this w2k3 server.


    I got this solution from here by the way. Thanks to Drew McLelland.

    --
    Why would anyone want to use a text editor that is not vi?
  4. Re:Oh, right, error code -36! by FidelCatsro · · Score: 5, Informative
    More info can be obtained from console.app in the Utilities directory under Applications(/Applications/utilities , or just go through the system logs from the terminal , but console.app is a rather nice time saver), its just a colection of the systems logs but its rather usefull and searchable .
    It does give a more detailed output. for example when i try to connect to my existant SMB share it gives me
    May 7 11:32:53 Xcomp kernel[0]: netsmb_dev: loaded
    May 7 11:32:53 xcomp[0]: netsmb_dev: loaded
    May 7 11:35:39 xcomp[0]: smbfs_aclsflunksniff: user sid S-1-5-21-2466424394-2119469220-2469460652-2002 didnt map
    I would have given an example of the error output from the specific problem , but i am doing some work on the linux comp that runs my nfs and samba shares right now .
    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though