AFP automount sharing broken in Lion Server?

Network rundown:
Mac Mini running Server
two MBPs (one upgraded to Lion, the other still running Snow Leopard)
The Mini is the OD Master for the three Macs and runs a number of services (Mail, Web, Wiki, VPN, etc.). The important service for this thread is that it serves out three shares via AFP, configured to be automounted on the two laptops. Normally all three shares are set up (via Workgroup Manager / Directory Utility) to use the Kerberos v2 UAM; however, for testing purposes I've temporarily adjusted the UAMs as follows:
/Groups -> afp://myserver/Groups
/Volumes/Attic -> afp://;AUTH=No%20User%20Authent@myserver/Attic
/Volumes/Multimedia -> afp://;AUTH=Client%20Krb%20v2@myserver/Multimedia
When the Mini is running Snow Leopard Server (10.6.8), the automounting behavior works as expected when connecting from a laptop without a valid Kerberos ticket:
lionmbp:~>klist -f
klist: krb5_cc_get_principal: No credentials cache file found
lionmbp:~>ls /Groups
ls: Groups: Invalid argument
lionmbp:~>ls /Volumes/Attic
[snip - file listing]
lionmbp:~>df -h /Volumes/Attic
Filesystem                                Size   Used  Avail Capacity  Mounted on
afp_000000004oMw0oYHtK4AvcMP-1.2d00010a  466Gi  277Gi  189Gi    60%    /Volumes/Attic
lionmbp:~>ls /Volumes/Multimedia
ls: Multimedia: Invalid argument
and then with a valid Kerberos ticket:
lionmbp:~>sudo umount /Volumes/Attic
Password:
lionmbp:~>df -h /Volumes/Attic
Filesystem    Size   Used  Avail Capacity  Mounted on
map -static    0Bi    0Bi    0Bi   100%    /Volumes/Attic
lionmbp:~>klist -f
[snip]
Sep 19 23:27:17  Sep 21 23:27:17  FPRIA  krbtgt/DOMAIN@DOMAIN
lionmbp:~>ls /Groups
[snip - file listing]
lionmbp:~>ls /Volumes/Attic
[snip - file listing]
lionmbp:~>ls /Volumes/Multimedia/
[snip - file listing]
However, after upgrading the Mini to Lion Server (10.7.1), attempting to automount the same shares does not work at all, regardless of whether a valid Kerberos ticket exists or not
lionmbp:~>klist -f
klist: krb5_cc_get_principal: No credentials cache file found
lionmbp:~>ls /Groups
ls: Groups: Authentication error
lionmbp:~>ls /Volumes/Attic
ls: Attic: Input/output error
lionmbp:~>ls /Volumes/Multimedia/
ls: : Invalid argument
lionmbp: /usr/bin/kinit
[snip - provide password]
lionmbp:~>klist -f
[snip]
Sep 19 23:15:09  Sep 21 23:15:09  FPRIA  krbtgt/DOMAIN@DOMAIN
lionmbp:~>date
Mon Sep 19 23:17:03 CDT 2011
lionmbp:~>ls /Groups
ls: Groups: Authentication error
lionmbp:~>ls /Volumes/Attic
ls: Attic: Input/output error
lionmbp:~>ls /Volumes/Multimedia/
ls: : Invalid argument
Anyone else encountering the same issues with AFP on Lion Server? Is AFP simply broken, or is there some poorly documented configuration/troubleshooting procedure that can resolve this issue?
Notes:
I only tried the automounting from the Lion MBP, I would expect that a Lion <-> Lion AFP connection would have fewer issues than Snow Leopard <-> Lion
The issue originally presented itself several weeks ago when I atttempted to upgrade the server; this AFP problem was a showstopper so I restored SL from a backup. I have since been testing by cloning the server drive to a USB drive, booting from it, and running the upgrade there.
In performing the Lion Server upgrade, I follow all the defaults. The server is booted off the USB drive to ensure it is in a working state before starting the upgrade. The only post-upgrade changes are to run Software Update (mainly to capture the recent security update) and then to follow the single signon instructions posted here

Some more testing hints in the direction of the problem:
aragorn:~>kinit -l 48h -r 48h -p -f [email protected]
[email protected]'s Password:
aragorn:~>klist -fCredentials cache: API:1501:10
        Principal: [email protected]
  Issued           Expires        Flags    Principal
Oct  1 17:05:53  Oct  3 17:05:50  FPRIA  krbtgt/[email protected]
aragorn:~>ls /Volumes/Multimedia
ls: Multimedia: Invalid argument
aragorn:~>mkdir /tmp/test; chmod 777 /tmp/test
aragorn:~>sudo mount_afp "afp://;AUTH=Client Krb [email protected]/Multimedia" /tmp/test
mount_afp: AFPMountURL returned error -50, errno is -50
Looking in MacErrors.h reveals
paramErr                      = -50,  /*error in user parameter list*/
That both ways of mounting AFP seem to be complaining of argument/parameter errors indicates something isn't being passed across the network correctly or is not being parsed properly on one end or the other. At the moment my dtrace-fu isn't strong enough to delve into this more deeply.
With 10.7.2 due out soon, I think I'll wait to see if Apple engineering caught this already. If not, I'll raise a bug ticket.

Similar Messages

  • Screen sharing not working Lion Server

    I can't connect to my Lion Server from any other Mac. I got it working for a few minutes after the first restart but I can't get it to work now. It's a Mac mini server runnning headless. I've even tried connecting it to a TV for a screen and it looks like everything is still set correctly for screen sharing under remote management. I can connect via the Server Admin app (pretty slim compared to 10.6) and via ssh fine. Services seem to be running OK.
    For the life of me I can't see what the problem is. It worked fine under 10.6.8 before upgrading.

    My Mini is running server headless and it works fine for Remote Desktop.  Are you using ARD or standard Screen Sharing from OSX?  Or a VNC client?
    Take a look at:
    http://technotes.twosmallcoins.com/?p=279
    For some notes on how to start the VNC server from the SSH command line.
    But, screen sharing should work for you. 

  • Connecting SL clients to Lion Server issues

    After  a week of use , Snow leopard clients are now no longer able to connect to an afp shared drive on Lion Server.  Worked fine for the first week.
    Here is a crash report from one of the clients:
    Process:         NetAuthAgent [160]
    Path:            /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent
    Identifier:      com.apple.NetAuthAgent
    Version:         2.1 (2.1)
    Build Info:      NetAuth-710100~1
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [95]
    Date/Time:       2011-09-12 16:13:25.230 -0400
    OS Version:      Mac OS X 10.6.6 (10J567)
    Report Version:  6
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
    Crashed Thread:  3
    Thread 0:  Dispatch queue: com.apple.main-thread
    0   libSystem.B.dylib                       0x00007fff860272da mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff8602794d mach_msg + 59
    2   com.apple.CoreFoundation                0x00007fff817c7932 __CFRunLoopRun + 1698
    3   com.apple.CoreFoundation                0x00007fff817c6dbf CFRunLoopRunSpecific + 575
    4   com.apple.HIToolbox                     0x00007fff86f9a93a RunCurrentEventLoopInMode + 333
    5   com.apple.HIToolbox                     0x00007fff86f9a73f ReceiveNextEventCommon + 310
    6   com.apple.HIToolbox                     0x00007fff86f9a5f8 BlockUntilNextEventMatchingListInMode + 59
    7   com.apple.AppKit                        0x00007fff83658e64 _DPSNextEvent + 718
    8   com.apple.AppKit                        0x00007fff836587a9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
    9   com.apple.AppKit                        0x00007fff8361e48b -[NSApplication run] + 395
    10  com.apple.NetAuthAgent                  0x000000010000be31 0x100000000 + 48689
    11  com.apple.NetAuthAgent                  0x0000000100001478 0x100000000 + 5240
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                       0x00007fff8604016a kevent + 10
    1   libSystem.B.dylib                       0x00007fff8604203d _dispatch_mgr_invoke + 154
    2   libSystem.B.dylib                       0x00007fff86041d14 _dispatch_queue_invoke + 185
    3   libSystem.B.dylib                       0x00007fff8604183e _dispatch_worker_thread2 + 252
    4   libSystem.B.dylib                       0x00007fff86041168 _pthread_wqthread + 353
    5   libSystem.B.dylib                       0x00007fff86041005 start_wqthread + 13
    Thread 2:
    0   libSystem.B.dylib                       0x00007fff86040f8a __workq_kernreturn + 10
    1   libSystem.B.dylib                       0x00007fff8604139c _pthread_wqthread + 917
    2   libSystem.B.dylib                       0x00007fff86041005 start_wqthread + 13
    Thread 3 Crashed:
    0   libSystem.B.dylib                       0x00007fff8602a160 strlen + 16
    1   libSystem.B.dylib                       0x00007fff86030d58 strdup + 28
    2   com.apple.KerberosHelper                0x00007fff818f6520 KRBCreateSessionInfo + 882
    3   com.apple.KerberosHelper                0x00007fff818f7453 KRBCreateSession + 158
    4   com.apple.NetAuthAgent                  0x0000000100019965 0x100000000 + 104805
    5   com.apple.NetAuthAgent                  0x0000000100019556 0x100000000 + 103766
    6   com.apple.NetAuthAgent                  0x000000010001a058 0x100000000 + 106584
    7   com.apple.NetAuthAgent                  0x00000001000087ee 0x100000000 + 34798
    8   com.apple.Foundation                    0x00007fff805040a5 __NSThread__main__ + 1429
    9   libSystem.B.dylib                       0x00007fff86060536 _pthread_start + 331
    10  libSystem.B.dylib                       0x00007fff860603e9 thread_start + 13
    Thread 3 crashed with X86 Thread State (64-bit):
    rax: 0x00000000ffffffff  rbx: 0x00000000fffffffd  rcx: 0x0000000000000000  rdx: 0x0000000000000000
    rdi: 0x0000000000000000  rsi: 0x0000000100614f61  rbp: 0x00000001138d5080  rsp: 0x00000001138d5058
      r8: 0x0000000000800000   r9: 0x00000000100614f7  r10: 0x0000000000000000  r11: 0x0000000100614f70
    r12: 0x00007fff70380490  r13: 0x0000000000000000  r14: 0x00000001006141c0  r15: 0x00000001138d5ab8
    rip: 0x00007fff8602a160  rfl: 0x0000000000010286  cr2: 0x0000000000000000
    Binary Images:
          0x100000000 -        0x100029fff  com.apple.NetAuthAgent 2.1 (2.1) <42B1CD13-9A8F-4882-F5B3-DB9BDB05B147> /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent
          0x1000e0000 -        0x1000e7fff  com.apple.URLMount.AFPPlugin 3.2.1 (3.2.1) <108073AE-9E03-4455-296C-144C2FCF013C> /System/Library/Filesystems/NetFSPlugins/afp.bundle/Contents/MacOS/afp
          0x100783000 -        0x1007cdfff  com.apple.AppleShareClientCore 2.0 (2.0) <2604D912-AE13-00F6-1C8C-A54A5D1A4923> /System/Library/Frameworks/AppleShareClientCore.framework/Versions/A/AppleShare ClientCore
       0x7fff5fc00000 -     0x7fff5fc3bdef  dyld 132.1 (???) <B536F2F1-9DF1-3B6C-1C2C-9075EA219A06> /usr/lib/dyld
       0x7fff804f3000 -     0x7fff80776ff7  com.apple.Foundation 6.6.4 (751.42) <9A99D378-E97A-8C0F-3857-D0FAA30FCDD5> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
       0x7fff807c1000 -     0x7fff807d7fe7  com.apple.MultitouchSupport.framework 207.10 (207.10) <1828C264-A54A-7FDD-FE1B-49DDE3F50779> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
       0x7fff807d8000 -     0x7fff807eafe7  libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <30FE378B-99FE-8C7C-06D0-A3AA0A0A70D4> /usr/lib/libsasl2.2.dylib
       0x7fff807eb000 -     0x7fff8089afff  edu.mit.Kerberos 6.5.10 (6.5.10) <F3F76EDF-5660-78F0-FE6E-33B6174F55A4> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
       0x7fff808ad000 -     0x7fff8092afef  libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
       0x7fff80986000 -     0x7fff80987ff7  com.apple.TrustEvaluationAgent 1.1 (1) <A91CE5B9-3C63-5F8C-5052-95CCAB866F72> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
       0x7fff8101c000 -     0x7fff8101cff7  com.apple.Cocoa 6.6 (???) <C69E895A-1C66-3DA9-5F63-8BE85DB9C4E1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
       0x7fff8101d000 -     0x7fff8103aff7  libPng.dylib ??? (???) <14043CBC-329F-4009-299E-DEE411E16134> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
       0x7fff8121a000 -     0x7fff8122efff  libGL.dylib ??? (???) <1EB1BD0F-C17F-55DF-B8B4-8E9CF99359D4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
       0x7fff8126a000 -     0x7fff81428fff  libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <781E7B63-2AD0-E9BA-927C-4521DB616D02> /usr/lib/libicucore.A.dylib
       0x7fff814e2000 -     0x7fff814e5ff7  libCoreVMClient.dylib ??? (???) <609598E6-195D-E5D4-3B92-AE8D9768829C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
       0x7fff816b7000 -     0x7fff81743fef  SecurityFoundation ??? (???) <6860DE26-0D42-D1E8-CD7C-5B42D78C1E1D> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
       0x7fff81744000 -     0x7fff8174aff7  com.apple.DiskArbitration 2.3 (2.3) <AAB5CC56-334A-3C60-3C27-54E8F34D754E> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
       0x7fff8177b000 -     0x7fff818f2fe7  com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
       0x7fff818f3000 -     0x7fff818faff7  com.apple.KerberosHelper 2.1 (1.0) <AD86E835-8CD3-11C6-339C-95A439A9F0E9> /System/Library/PrivateFrameworks/KerberosHelper.framework/Versions/A/KerberosH elper
       0x7fff818fb000 -     0x7fff819b4fff  libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib
       0x7fff81a28000 -     0x7fff81ae9fe7  libFontParser.dylib ??? (???) <8B12D37E-3A95-5A73-509C-3AA991E0C546> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
       0x7fff81bee000 -     0x7fff81bf3fff  libGFXShared.dylib ??? (???) <991F8197-FD06-2AF1-F99B-E448ED4FB2AC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
       0x7fff828fc000 -     0x7fff828fcff7  com.apple.vecLib 3.6 (vecLib 3.6) <96FB6BAD-5568-C4E0-6FA7-02791A58B584> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
       0x7fff82b0c000 -     0x7fff82b53ff7  com.apple.coreui 2 (114) <31118426-355F-206A-65AB-CCA2D2D3EBD7> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
       0x7fff82bb0000 -     0x7fff82e36fff  com.apple.security 6.1.1 (37594) <1B4E1ABD-1BB3-DA49-F574-0EEB23E73C6A> /System/Library/Frameworks/Security.framework/Versions/A/Security
       0x7fff82e37000 -     0x7fff82e57ff7  com.apple.DirectoryService.Framework 3.6 (621.9) <FF6567B5-56BD-F3EC-E59D-1EC583C3CF73> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
       0x7fff830a1000 -     0x7fff83173fe7  com.apple.CFNetwork 454.11.5 (454.11.5) <B3E2BE12-D7AA-5940-632A-1E5E7BF8E6E3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
       0x7fff83203000 -     0x7fff83217ff7  com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <574C1BE0-5E5E-CCAF-06F8-92A69CB2892D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
       0x7fff83219000 -     0x7fff83261ff7  libvDSP.dylib 268.0.1 (compatibility 1.0.0) <98FC4457-F405-0262-00F7-56119CA107B6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
       0x7fff83262000 -     0x7fff83419fef  com.apple.ImageIO.framework 3.0.4 (3.0.4) <2CB9997A-A28D-80BC-5921-E7D50BBCACA7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
       0x7fff83451000 -     0x7fff83451ff7  com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <4CCE5D69-F1B3-8FD3-1483-E0271DB2CCF3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
       0x7fff83452000 -     0x7fff83507fe7  com.apple.ink.framework 1.3.3 (107) <A68339AA-909D-E46C-35C0-72808EE3D043> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
       0x7fff83508000 -     0x7fff83554fff  libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib
       0x7fff83555000 -     0x7fff83576fff  libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <6993F348-428F-C97E-7A84-7BD2EDC46A62> /usr/lib/libresolv.9.dylib
       0x7fff83577000 -     0x7fff835c6ff7  com.apple.DirectoryService.PasswordServerFramework 6.0 (6.0) <F5B744D7-AEAF-6B66-43CF-6E31CDA18EAB> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordS erver
       0x7fff83615000 -     0x7fff8400bfff  com.apple.AppKit 6.6.7 (1038.35) <9F4DF818-9DB9-98DA-490C-EF29EA757A97> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
       0x7fff8400c000 -     0x7fff8409cfff  com.apple.SearchKit 1.3.0 (1.3.0) <45BA1053-9196-3C2F-2421-AFF5E09627CC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
       0x7fff842dd000 -     0x7fff842eeff7  libz.1.dylib 1.2.3 (compatibility 1.0.0) <FB5EE53A-0534-0FFA-B2ED-486609433717> /usr/lib/libz.1.dylib
       0x7fff842ef000 -     0x7fff8436dfff  com.apple.CoreText 3.5.0 (???) <4D5C7932-293B-17FF-7309-B580BB1953EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
       0x7fff8436e000 -     0x7fff843b7ff7  com.apple.securityinterface 4.0.1 (40418) <E2DC796D-84EC-48F5-34A9-DF614573BE74> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
       0x7fff843b8000 -     0x7fff843b9fff  liblangid.dylib ??? (???) <D0666597-B331-C43C-67BB-F2E754079A7A> /usr/lib/liblangid.dylib
       0x7fff843ba000 -     0x7fff843bbff7  com.apple.audio.units.AudioUnit 1.6.5 (1.6.5) <14F14B5E-9287-BC36-0C3F-6592E6696CD4> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
       0x7fff843bc000 -     0x7fff8443bfe7  com.apple.audio.CoreAudio 3.2.6 (3.2.6) <1DD64A62-0DE4-223F-F781-B272FECF80F0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
       0x7fff8443c000 -     0x7fff84485fef  libGLU.dylib ??? (???) <CCE779A9-2467-A5AA-A558-691E43A1105F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
       0x7fff84582000 -     0x7fff845b3fff  libGLImage.dylib ??? (???) <1A8E58CF-FA2F-14F7-A097-D34EEA8A7D03> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
       0x7fff845b4000 -     0x7fff84671ff7  com.apple.CoreServices.OSServices 357 (357) <718F0719-DC9F-E392-7C64-9D7DFE3D02E2> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
       0x7fff84672000 -     0x7fff84793fe7  libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <48AEAFE1-21F4-B3C8-4199-35AD5E8D0613> /usr/lib/libcrypto.0.9.8.dylib
       0x7fff84794000 -     0x7fff84819ff7  com.apple.print.framework.PrintCore 6.3 (312.7) <CDFE82DD-D811-A091-179F-6E76069B432D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
       0x7fff84835000 -     0x7fff8483cfff  com.apple.OpenDirectory 10.6 (10.6) <4200CFB0-DBA1-62B8-7C7C-91446D89551F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
       0x7fff8483d000 -     0x7fff848a7fe7  libvMisc.dylib 268.0.1 (compatibility 1.0.0) <7BD7F19B-ACD4-186C-B42D-4DEBA6795628> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
       0x7fff84908000 -     0x7fff8492efe7  libJPEG.dylib ??? (???) <6690F15D-E970-2678-430E-590A94F5C8E9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
       0x7fff8492f000 -     0x7fff84981ff7  com.apple.HIServices 1.8.2 (???) <7C91D07D-FA20-0882-632F-0CAE4FAC2B79> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
       0x7fff84d5d000 -     0x7fff84db2ff7  com.apple.framework.familycontrols 2.0.2 (2020) <A3CFF697-B9DB-A7E5-3B39-9DA9B34F0595> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
       0x7fff84e4a000 -     0x7fff84e5fff7  com.apple.LangAnalysis 1.6.6 (1.6.6) <DC999B32-BF41-94C8-0583-27D9AB463E8B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
       0x7fff84e60000 -     0x7fff84e6bff7  com.apple.speech.recognition.framework 3.11.1 (3.11.1) <C359B93B-CC9B-FC0B-959E-FB10674103A7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
       0x7fff84e6c000 -     0x7fff851a0fff  com.apple.CoreServices.CarbonCore 861.23 (861.23) <08F360FA-1771-4F0B-F356-BEF68BB9D421> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
       0x7fff8521e000 -     0x7fff85246fff  com.apple.DictionaryServices 1.1.2 (1.1.2) <E9269069-93FA-2B71-F9BA-FDDD23C4A65E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
       0x7fff85247000 -     0x7fff8524bff7  libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
       0x7fff8524c000 -     0x7fff85302fff  libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <1960E662-D35C-5D98-EB16-D43166AE6A22> /usr/lib/libobjc.A.dylib
       0x7fff85303000 -     0x7fff853a3fff  com.apple.LaunchServices 362.2 (362.2) <A8EDC37C-1D40-5ED0-49BE-90EF110A6B3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
       0x7fff857f3000 -     0x7fff85c36fef  libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <57D38705-6F21-2A82-F3F6-03CFFF214775> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
       0x7fff85c37000 -     0x7fff85c70fef  libcups.2.dylib 2.8.0 (compatibility 2.0.0) <561D0DCB-47AD-A12C-9066-70E4CBAD331C> /usr/lib/libcups.2.dylib
       0x7fff85d4a000 -     0x7fff85d58ff7  libkxld.dylib ??? (???) <4016E9E6-0645-5384-A697-2775B5228113> /usr/lib/system/libkxld.dylib
       0x7fff85d59000 -     0x7fff85d59ff7  com.apple.ApplicationServices 38 (38) <0E2FC75E-2BE2-D04D-CA78-76E38A89DD30> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
       0x7fff85d70000 -     0x7fff85e4afff  com.apple.vImage 4.0 (4.0) <B5A8B93B-D302-BC30-5A18-922645DB2F56> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
       0x7fff85e73000 -     0x7fff85ec2fef  libTIFF.dylib ??? (???) <AE9DC484-1382-F7AD-FE25-C28082FCB5D9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
       0x7fff86026000 -     0x7fff861e7fff  libSystem.B.dylib 125.2.1 (compatibility 1.0.0) <71E6D4C9-F945-6EC2-998C-D61AD590DAB6> /usr/lib/libSystem.B.dylib
       0x7fff861e8000 -     0x7fff8629dfe7  com.apple.ColorSync 4.6.3 (4.6.3) <AA93AD96-6974-9104-BF55-AF7A813C8A1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
       0x7fff862fa000 -     0x7fff86413fef  libGLProgrammability.dylib ??? (???) <4F2DC233-7DD2-1204-CAA5-3E6524F0AB75> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
       0x7fff8650d000 -     0x7fff86633fff  com.apple.audio.toolbox.AudioToolbox 1.6.5 (1.6.5) <B51023BB-A5C9-3C65-268B-6B86B901BB2C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
       0x7fff86634000 -     0x7fff8663aff7  IOSurface ??? (???) <04EDCEDE-E36F-15F8-DC67-E61E149D2C9A> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
       0x7fff8663b000 -     0x7fff8664afff  com.apple.opengl 1.6.12 (1.6.12) <DE3F0528-7759-CDFD-A2CF-C51D3C9C8B39> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
       0x7fff866c0000 -     0x7fff866c5fff  libGIF.dylib ??? (???) <9A2723D8-61F9-6D65-D254-4F9273CDA54A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
       0x7fff866c6000 -     0x7fff86701fff  com.apple.AE 496.4 (496.4) <CB905496-4D6B-F26A-399D-840D26DBEE5B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
       0x7fff86702000 -     0x7fff8672dff7  libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <6589F0FC-41DB-8494-CA8B-487F4E328EB9> /usr/lib/libxslt.1.dylib
       0x7fff867df000 -     0x7fff867dfff7  com.apple.Accelerate 1.6 (Accelerate 1.6) <15DF8B4A-96B2-CB4E-368D-DEC7DF6B62BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
       0x7fff86801000 -     0x7fff868e6fef  com.apple.DesktopServices 1.5.9 (1.5.9) <27890B2C-0CD2-7C27-9D0C-D5952C5E8438> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
       0x7fff86c3a000 -     0x7fff86c9afe7  com.apple.framework.IOKit 2.0 (???) <D107CB8A-5182-3AC4-35D0-07068A695C05> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
       0x7fff86c9b000 -     0x7fff86dd9fff  com.apple.CoreData 102.1 (251) <96C5E9A6-C28C-E9CC-A0DB-27801A22A49F> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
       0x7fff86dda000 -     0x7fff86ef1fef  libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <AFE91118-DBF3-6313-37B8-8A2002C6A46B> /usr/lib/libxml2.2.dylib
       0x7fff86f55000 -     0x7fff86f5bff7  com.apple.CommerceCore 1.0 (6) <E8A1144C-5666-9840-4729-256FE69CDBDB> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
       0x7fff86f5c000 -     0x7fff86f6bfff  com.apple.NetFS 3.2.1 (3.2.1) <DE59FB56-8536-9999-352A-2016ADCF4FCF> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
       0x7fff86f6c000 -     0x7fff8726afe7  com.apple.HIToolbox 1.6.4 (???) <263AD497-F4CC-9610-E7D3-B95CF6F02030> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
       0x7fff87277000 -     0x7fff87311fff  com.apple.ApplicationServices.ATS 4.4 (???) <395849EE-244A-7323-6CBA-E71E3B722984> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
       0x7fff873ea000 -     0x7fff87787fe7  com.apple.QuartzCore 1.6.3 (227.34) <215222AF-B30A-7CE5-C46C-1A766C1D1D2E> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
       0x7fff87ac1000 -     0x7fff881be06f  com.apple.CoreGraphics 1.545.0 (???) <356D59D6-1DD1-8BFF-F9B3-1CE51D2F1EC7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
       0x7fff881bf000 -     0x7fff88200fef  com.apple.QD 3.36 (???) <5DC41E81-32C9-65B2-5528-B33E934D5BB4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
       0x7fff88201000 -     0x7fff88217fef  libbsm.0.dylib ??? (???) <0321D32C-9FE1-3919-E03E-2530A0C1191B> /usr/lib/libbsm.0.dylib
       0x7fff8849d000 -     0x7fff8849ffff  libRadiance.dylib ??? (???) <76438F90-DD4B-9941-9367-F2DFDF927876> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
       0x7fff884a0000 -     0x7fff884eaff7  com.apple.Metadata 10.6.3 (507.15) <5170FCE0-ED6C-2E3E-AB28-1DDE3F628FC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
       0x7fff88652000 -     0x7fff88677ff7  com.apple.CoreVideo 1.6.2 (45.6) <E138C8E7-3CB6-55A9-0A2C-B73FE63EA288> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
       0x7fff88779000 -     0x7fff88779ff7  com.apple.CoreServices 44 (44) <DC7400FB-851E-7B8A-5BF6-6F50094302FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
       0x7fff887c5000 -     0x7fff887defff  com.apple.CFOpenDirectory 10.6 (10.6) <CCF79716-7CC6-2520-C6EB-A4F56AD0A207> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
       0x7fff887df000 -     0x7fff88fe9fe7  libBLAS.dylib 219.0.0 (compatibility 1.0.0) <2F26CDC7-DAE9-9ABE-6806-93BBBDA20DA0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
       0x7fff88fea000 -     0x7fff8902bfff  com.apple.SystemConfiguration 1.10.5 (1.10.2) <FB39F09C-57BB-D8CC-348D-93E00C602F7D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
       0x7fff89124000 -     0x7fff89147fff  com.apple.opencl 12.3 (12.3) <D30A45FC-4520-45AF-3CA5-092313DB5D54> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
       0x7fff89156000 -     0x7fff89163fe7  libCSync.A.dylib 545.0.0 (compatibility 64.0.0) <397B9057-5CDF-3B19-4E61-9DFD49369375> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
       0x7fffffe00000 -     0x7fffffe01fff  libSystem.B.dylib ??? (???) <71E6D4C9-F945-6EC2-998C-D61AD590DAB6> /usr/lib/libSystem.B.dylib

    Simplest way is to write the program to create anew thread to handle each client
    when the ServerSocket accepts a new connection a new thread should be created and that will handle the client. The main threadshould go back to accept next client
    while(true){
       Soeket socket = serverSocket.acept();
       new ClientHandler(socket).start(); /ClientHandler is the class that should be handling the communication with the client
    }

  • How to configure Airport Extreme AFP disk sharing to host multiple users' home-directories (Lion, using autofs)

    I have this working, but only by completely bypassing access control, using guest access with read+write permissions.
    Do I need to buy Lion Server, to do this. All my past unix/linux experience says Lion Server should _not_ be necessary.
    This seems like a simple & obvious setup objective, but it is proving to be harder than I would imagine.
    Setup:
    multiple users, sharing two mac mini's running OSX Lion
    connected to an Airport Extreme (4th gen) with a USB disk shared (either via disk password, AEBS password, or using AEBS user's passwords).
    After much experimentation and web research, I finally have managed to get the mini's to auto mount the Airport Extreme's AFP shared USB disk. Well almost... It only works if, on the Airport, I set the guest access permissions to read+write and select the "Secure Shared Disks" method to "With disk password" or "with Airport Extreme password".  In other words, it only works if I essentially bypass/disable access control by using the guest authentication mechanism to the AFP shared disk.
    On the Lion side of this, I am automounting the users directories via "autofs". The config files for this are
    /etc/auto_master:
    # Automounter master map
    +auto_master            # Use directory service
    /net                    -hosts          -nobrowse,hidefromfinder,nosuid
    /home                   auto_home       -nobrowse,hidefromfinder
    /Network/Servers        -fstab
    /-                      -static
    /-                      auto_afp
    /etc/auto_afp:
    # Automounter AFP master map
    # https://discussions.apple.com/thread/3336384?start=0&tstart=0
    /afp/users -fstype=afp afp://;AUTH=No%20User%[email protected]/Users/
    Then, after rebooting and verifying read+write access to the /afp/users directories, I change each user's home directory: In System Preferences > System > Users & Groups, I right-click over the users to access the Advanced Options, changing the Home directory field to point at the AFP-mounted /afp/users/Users/* home directories.
    I experimented with alternate UAM specifications, as well as both OSX and AESB users & passwords. Using guest access is the only thing that has worked.
    Any pointers would be appreciated...

    Based on lots more experimentation which confirms the information in a parallel discussion (cf. Automount share as non ROOT or SYSTEM user! https://discussions.apple.com/thread/3221944), I have concluded that the Lion 10.7.2 implementation of AutoFS mechanism is broken. I submitted a bug report via apple.com/feedback.
    Work arounds..?
    Earlier I wondered if installing Lion OSX Server was necessary.  The more I contemplate this, the more I am convinced it _should_not_ be necessary. The client-server architecture is clear: my mac's are the file-server client's and the Airport Extreme is supposed to act as the file server. The only thing instaling Lion Server would do (besides enriching Apple.com) is enable me to configure one of the mac's as the file server. This would require it to be "always on" (thus enriching my electric utility as wel).  Okay, an additional benefit would be configuring software RAID disks attached to the Lion server, but Time Machine has worked fine for me in the past, backing up to disks mounted on the Airport Extreme.
    One solution is to create a disk partition for each user and instruct each user to connect / authenticate to the Airport Extreme AFP share at login.  The multiplicity of partitions is necessary since the first user to mount the AFP share, takes ownership of it, blocking other users from accessing that disk partition.  A user can "steal" ownership by reconnecting, but this will leave the other user's applications & open files dangling.
    This disfunctional situation really *****.  Before instaling Lion, I put a 64 GB SSD (solid state disk) in each of our mac's. I did this expecting to easily configure the /Users/* data on external networked storage. I'm having a dejavu "Bill Gates"-ware moment; problems like this were why I abandoned Windoz.
    I will make a few more experiments using the depreciated /etc/fstab mechanism.  Maybe that will bypass the broken-ness of AutoFS...? Alternately, I guess I could also try to run Kerberos authentication to bypass whatever is broken in AutoFS, but that would require a running a Kerberos daemon somewhere.  Possibly I could configure a Kerberos service to run on both my mac's (without installing Apple's Lion Server)...?
    Stay tuned...

  • How do I set up file sharing in Lion Server to work like file sharing in Lion Client?

    I've just installed Lion Server on my home iMac to enable remote access via VPN to my home network.
    When the iMac was running Lion Client (before the upgrade to server), and when File Sharing was enabled on the iMac; when other Macs on the LAN connected to the iMac via AFP, they were always able to connect to (share) any mounted external volumes (external USB or FireWire drives connected to the iMac). e.g.
    Now that I've upgraded to Lion Server, when other Macs on the LAN connected to the iMac via AFP they are only able to connect to (share) the sharepoints listed in the File Sharing pane of Server.app. e.g.
    Is there any way to set up File Sharing in Lion Server so that it works the same way as it does in Lion Client with respect to mounted external volumes? i.e. they are automatically shared? I know I can add each volume manually to File Sharing in Server.app but this gets tedious.
    Many thanks!

    I normally have a Firewall enabled. I recently had to do an erase and install of Lion, followed by a one-by-one re-install of all of my software. One of the first things I did was to set up all of my System Preferences the way I like them; Turning the Firewall on was one of them. Later I noticed it was off and turned it on again. I had already set up sharing and was surprised to see the problem when I turned it back on.
    As to why do I think it needs to be on. It is another part of my security layer.

  • Lion Server file sharing

    Hi guys, I have a client running Lion server 10.4, and roughly 5 Mac's around the office all running lion 10.4. Everything was setup and running smoothly until this morning when he lost all file sharing to the server. (Data is stored on the server and Mac's connect through finder>network>server) When hitting "connect as" there is no login window, the black bar just says "connecting" and doesn't get any further. I have tried restarting the file sharing service from the server, connecting manually via its IP with both AFP and SMB to no avail. I have also tried turning off AFP on the server and restarting that, as well as adding other shared folders, opening up permission etc. Hoping someone has an idea of what's going on!

    No problem! We rebooted the server to no avail, and the client iMac. It's all sorted now, I was logged in remotely so I couldn't see all the machines at once, according to my client it just started working but I'm pretty sure there's some detail he left out in what he was doing. It did however seem to be an issue only on the one workstation so all good! Thanks for the quick response

  • Lion Server File Sharing Crashes

    We have a brand new Mac Pro (12 core with 64GB of RAM) running OS X Lion Server in a corporate environment. The server is running only file sharing and software update servers, and we have around 40 users who need to be connected over AFP at all times. This company runs 24/7 and we have an XSan environment using an ATTO Celerity 8GB 4 channel fiber card (84EN) along with a 6 port 10GB Ethernet card. The Ethernet card is configured in a link aggregation bond using ports 1-4. The idea is that clients who do not have fiber cards installed on their machines can still connect to the SAN via Ethernet and this file server. They AFP connect to the share, and of course the share is the SAN. It's a single mount point and everyone has read/write access.
    The issue is that this machine keeps crashing (multiple times per day) and I cannot find any reason why. Syslog shows nothing of value and I've called into Apple Enterprise Support who also brought nothing to the table.
    We initially had SMB and AFP file sharing activated but as soon as a Windows 7 client connected the machine was brought down. So, I disabled SMB via terminal (sudo serveradmin stop smb) and deactivated it via the Server app for the share point). That at least allows the machine to be up for 4-6 hours before crashing again.
    This is seemingly the simplest of setups for file sharing and I would've thought that this beast of a machine would be able to handle being a file server without issue for far more than 40 clients. I'm seeing high CPU usage, which Apple support told me was perfectly normal (around 60% on the kernel_task process and around 55% on the AppleFileServer process). It also seems to consume all 64GB of memory, though it shows 60GB as inactive, but at the same time it's paging in and out.
    Virtually all of the clients are running Lion (10.7.4), the server itself is running 10.7.4. There are a few ethernet connected clients running 10.6 along with two running 10.5. As I mentioned I disabled SMB so there are no Windows computers connecting to this machine at this time (though it would be nice to get that functionality back if AFP can be stabilized).
    None of this makes any sense to me and I'm hoping someone can shed some light on this issue. This company simply cannot be down, especially not multiple times per day. The only way to bring things back and running from a crash is to hard boot the machine via the power button as you cannot perform a restart or a shutdown. Once the machine comes back up everything is back to working order for a few more hours until it happens again.

    All the memory is fine. The server rarely if ever goes down when there are only around 10-12 users connected. When there are 20+ users connected and working heavily it goes down often. When I say working heavily, I mean they are transferring huge files to the SAN (100GB+), sometimes 5 at a time per user, and there are a bunch of others who are reading large video files at a minimum of 220MB/sec from the SAN.
    Though this worked on Snow Leopard without any issues, Lion just doesn't seem to be able to handle it. The odd thing is, on Snow Leopard there was only a single 1GB ethernet connection to a NAS system, whereas with Lion we have a much more powerful machine with a 6-port 10GB ethernet card and a 4 lane 8GB fiber card to a true SAN. You would think that the newer scenario with Lion would handle far more users with ease.
    So far, very disappointing with regards to Lion's file serving performance.

  • Sharing only users cannot connect to Lion Server

    Dear all,
    I stumbled across a funny problem, that I tried to resolve all day. I just wanted to add a sharing only user for my girlfriends new MacBook that she could use to connect to a shared Time Machine Volume.
    If I add a new standard user, this user can connect to my server via finder (connect as...) and see the shared drives. If the same user tries to connect to the Time Machine Backup Volume via the settings dialog, it receives an error message (OSStatus-error 5).
    If I add a sharing only user, this user cannot connect via finder or Time Machine (same error). The clients console states the following error message:
    /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[2471]      AFP error -5018 mapped to EIO
    Does anybody have an Idea?

    That is my point.  Yes, Apple still lets you add users via users and groups in system preferences but that is not how you should be adding users.  I've seen nothing but trouble when that option is used to add users and I believe that the Lion server docs say to not use that.  If you are using lion server why not use it the way it was meant to be.  Just create a account in OD and only give her access to the Time Machine Service and none of the others.

  • Automount using OpenLDAP broken on Lion

    Hi everyone,
    Having a wierd issue with my new MacBook Air with Lion. I have the OpenLDAP server set up and can successfully authenticate and login users on it. The only thing that is broken is the automount. The Lion MacBook Air can read the automount keys from the LDAP server (verified with dscl), but automount refuses to use them (even when /etc/auto_master has only one line "+auto_master" uncommented). Using automount with the /etc/auto_master and /etc/auto_home works fine.
    I'm using the same configuration that is working just fine with my other Mac running Snow Leopard, so the issue can't be on the server side.
    The automount doc on the Lion MacBook is the same as on Snow Leopard, but following it does not help.
    Anybody run into similar issues? any ideas? is there an equivalent to nsswitch.conf on Macs?
    Thanks!

    Here's the skeleton of my configurations, for Autofs Linux and OSX interoperability :
    dn: automountMapName=auto.master,dc=example,dc=com
    objectClass: top
    objectClass: automountMap
    automountMapName: auto.master
    dn: automountKey=/home,automountMapName=auto.master,dc=example,dc=com
    objectClass: automount
    automountInformation: auto_home
    automountKey: /home
    dn: automountMapName=auto_master,dc=example,dc=com
    objectClass: top
    objectClass: automountMap
    automountMapName: auto_master
    dn: automountKey=/home,automountMapName=auto_master,dc=example,dc=com
    objectClass: automount
    automountInformation: auto_home -nobrowse,hidefromfinder
    automountKey: /home
    dn: automountMapName=auto_home,dc=example,dc=com
    objectClass: automountMap
    automountMapName: auto_home
    dn: automountKey=an_user,automountMapName=auto_home,dc=example,dc=com
    objectClass: automount
    automountInformation: -fstype=nfs,vers=3,soft,intr,rsize=16384,wsize=16384,nosuid fileserver.example.com:/vol/home/&
    automountKey: an_user

  • Sharing a Calendar from Mountain Lion server with Snow Leopard users on local network

    Hello.
    I have a new Mac Mini Server running Mountain Lion Server and I want to create a shared calender for a mix of Lion, Mountain Lion and Snow Leopard users on our local network. Does anyone have any info on how to do this? I have tried using the Server App and Calender Help within the applications, but the content isn't available. I have managed to create a Shared Calender  from the Mini's Calendar App where I've  added users and I can see a 'wireless' transmit icon to the right of the Calendar name - but I cant get any of the users' iCal or Calendar apps to recognise the Calendar on the local network. I've also created a Location in the Server App under Calendar and still can't see anything on the local network. Am I missing something really obvious?
    Thanks in advance!

    Sorry, I hadn't explained everything fully. I don't want to open up my VPN to friends and family. I do have the router assigning the NAS a fixed IP, so that when I connect over the VPN I can use the local IP address to connect, as you have mentioned.
    What I would like is for my friends or family to connect to my server over AFP or SMB using the public IP of my network, which my router then forwards onto my server, and display the available sharepoints configured using Mountain Lion server. However, the NAS drive is not an available option this way as it has a separate IP to the server.
    As the NAS alllows guest access, I also don't want to configure the router to forward a specific port to it, as this way it will be open to the internet. I wanted to try and use my server as an authentication point, with profiles set using Mountain Lion server, and limited to file sharing services only.
    Hope this makes sense.

  • Lion Server 10.7.3 file sharing permissions

    I'm having really strange issues with Lion Server. Since upgrading to 10.7.3 I no longer have permissions to modify files on Share Points that I was once able to in 10.7.2. When I go to modify certain files or folders I get "The operation can’t be completed because you don’t have permission to modify some items."

    Background
    Access Control Lists (ACLs) are  applied to folders and files to define user (and group) access privileges.
    I have setup two Mac mini Servers at our company – one in our Melbourne office and one in our Sydney office. Each file server is made up of the following hardware:
    1x Mac mini Server (with Lion Server).
    2x Promise Pegasus 12TB (6x2TB) R6 RAID System (thunderbolt) in RAID5 configuration. The two Pegasus unit are mirrored (RAID1) using SoftRAID.
    Users and Groups are replicated between the two servers via Open Directory.
    The PeachPit book "OS X Lion Server Essentials" is the best book I've found that explains OS X Server services and configuration. It has a  good explanation of POSIX and ACLs.
    The Problem
    It seems there is a bug in Lion Server that causes ACLs be ignored. A couple of times I've managed to fix the problem using these steps:
       1. Remove the share-point.
       2. Setup up the share-point. /Volumes/promiseraid/work
       3. Apply an ACL to a folder.
       5. Propagate the ACL to sub-folders.
    When ACLs are not applied to a folder the older POSIX permission define access privileges. With POSIX mechanism the user, group and other access privileges applied to new files and folders is defined in the 'unmask' value. The default 'unmask' value sets file/folder group to read-only access. The upshot is when POSIX mechanism is used and a member of staff creates a file or folder it is read-only to colleagues. System Administrators shouldn't need to change the 'unmask' value – too technical. Apple documentation encourages System Administrators to use ACLs to define access privileges – use ACLs to overcome the limitations of POSIX.
    The workarounds I've been considering
    Stick with Lion Server, apply POSIX read&write (group and others) permissions to all folders at regular intervals (daily) and wait for Mac Apple to fix the problem.
    Abandon Lion Server (10.7) and revert to Snow Leopard Server (10.6).
    Abandon Lion Server (10.7) and setup a Microsoft Windows Server solution.
    A solution?
    Scanning the several threads here I think I discovered a "fix". Mac OS Lion doesn't seem to honour ACLs if
    it is a volume is being shared (AFP and/or SMB), or
    it a folder at the root level of the volume is being shared (AFP and/or SMB).
    However, if the folder being shared is at least one folder deep ACLs seem to be honoured!
        !!! This did not work – ACLs are not honoured !!!!!
        /Volumes/promiseraid
        /Volumes/promiseraid
        /Volumes/promiseraid
        !!! This did not work – ACLs are not honoured !!!!!
        /Volumes/promiseraid/share1
        /Volumes/promiseraid/share2
        /Volumes/promiseraid/share3
        !!! This works – ACLs are honoured !!!!!
        /Volumes/promiseraid/shareditems/share1
        /Volumes/promiseraid/shareditems/share2
        /Volumes/promiseraid/shareditems/share3
    Acknowledgement
    I should acknowledge gmbion for his time troubleshooting this and reporting his findings to this thread.
    A response from Apple
    It would be good if Apple could address this limitation with either:
    A note from Apple acknowledging this limitation ("undocumented feature") witch advice to not share a volume or a folder at the root level of a volulme. Instead, share a folder at least one level deep; or
    Fix Lion Server so that any volume or folder can be shared and ACLs will be honoured.

  • Lion server file sharing issue with windows API read/write ini file (GetPrivateProfileString)

    Hello,
    I try to config lion server as file server for a windows application we use at work. All other computers are windows 7 or XP, lion server is the only mac. I choose lion server because it's size, quality and personal love of apple products.
    10.7.2 lion server's samba file sharing works almost perfectly with all my windows machines, I can copy, delete, modify any text files or office files without any issue, but the most important windows application for my business doesn't work with samba file sharing. After some digging, I found it is because windows program can't read or write INI file stored on lion share. Windows API GetPrivateProfileString always returns empty if the INI file is store on lion share.
    You can download a small application for read/write windows INI file from codeproject.com to test this problem:
    http://www.codeproject.com/KB/files/ini.aspx
    I can open/edit the in file using any text editor without any problem. The only problem is with those windows APIs. ACL is turned on for my lion share and assigned "delete" rights to samba users.
    I install samba3 on the same server; it works perfectly with windows API. My windows program also works. Looks like there is something wrong with lion server's sambax.
    I'd prefer to use built-in samba even I have samba3 working. Built-in samba is very immature right now, but considered how young it is, I will give apple some time to make it mature.
    Does anyone have same issue or knows how to fix it?
    Thanks,
    Michael.

    All the memory is fine. The server rarely if ever goes down when there are only around 10-12 users connected. When there are 20+ users connected and working heavily it goes down often. When I say working heavily, I mean they are transferring huge files to the SAN (100GB+), sometimes 5 at a time per user, and there are a bunch of others who are reading large video files at a minimum of 220MB/sec from the SAN.
    Though this worked on Snow Leopard without any issues, Lion just doesn't seem to be able to handle it. The odd thing is, on Snow Leopard there was only a single 1GB ethernet connection to a NAS system, whereas with Lion we have a much more powerful machine with a 6-port 10GB ethernet card and a 4 lane 8GB fiber card to a true SAN. You would think that the newer scenario with Lion would handle far more users with ease.
    So far, very disappointing with regards to Lion's file serving performance.

  • Files cannot be unlocked on AFP Share on Lion Server

    I have an environement with a Mac Pro Server (10.7.4) running as an Open Directory Master, DNS, with AFP file sharing enabled. All clients are running 10.7.4, none are bound to the domain and all home folders are local on the users machine. The users simply have an account in OD that they use to access a file share. The file share is "Public" in that the permissions are fully liberalized so that all users in the domain have read/write access. Whenever a user edits a Pages, Keynote, Numbers, Text Edit (anything that supports versions) and then saves the file, the next user to access the document finds that the document is locked. They cannot unlock it and must create a duplicate. Only the original user that opened the document can reopen it without facing the lock and having to duplicate it. Anyone have any ideas as to what might be causing this? Thank you.

    How about setting ACL's for the share?

  • Screen sharing to OS X Lion Server with non-admin account

    I have set up a Lion Server with one admin (in addition to the root user) and several non-admin normal accounts. In Server.app, I have enabled remote login with ssh, and remote management via screen sharing.  I am unable to use Screen Sharing to connect to the server from the non-admin accounts, but able to use the admin account. I've read that it is only enabled for admin users, but need to access from non-admin accounts, and I can't add these accounts to the admin group. Is there a way to do this with Workgroup Manager? I tried changing the Remote Management settings in System Preferences by adding the non-admin, but when selecting 'Observe' and 'Control' in the options for the user, they are not saved.

    I resolved this issue by deselecting the "Enable screen sharing and remote management" in Server.app and going to System Preferences, Sharing Preferences, Screen Sharing, and allowing access for "All Users".  If you have some users you want to allow VNC, you can create a group, add the allowed users to the group, and add the group under "Only these users".

  • How to view file access log (AFP) on Mac OS X Lion (10.7) server?

    I want to track the files beeing uploaded and downloaded or deleted on the shares on the server by different users. There has to be some log where the Mac OS writes an entry for every file access (like upload / download / rename / delete) for each user. How can I access it? How can I filter the actions by user account? Do I have to first activate such a logging or is it activated from the first (standard) setup of the Mac OS X Lion server?

    try:
    sudo serveradmin settings afp:activityLog=yes
    then the log entries should be at
    /Library/Logs/AppleFileService/AppleFileServiceAccess.log

Maybe you are looking for

  • Multiple email accounts on Lumia 800

    Dear All I have a question about email accounts on the Lumia 800. I have two email accounts, one linked to our website (pop 3) and also my personal Live account.  The account linked to the website can only receive (it costs more and thus was deemed u

  • Please!!! help me with my zen v

    i really need some help please!! my sister gave me this 2G creative zen v that?I really like and?I love it...but the problem is that after a certain number of songs (usually less than a 00) an error message?display on the screen, and I don't know wha

  • How do I transfer my data from my old iMac(05) to the new iMac(12)?

    I bought a new iMac and went through the setup process, however I did not have the ability to transfer my data from my old iMac to the new one because I didn't have a cable.  I have new iPhones, iPods and Apps that need transfering.  Can someone prov

  • Add selected value to holding table

    hi i have a situation where i search user from the table,and go and add those selected user in OID,But now before i add those user to OID i what to add tham in holding table not database table, where i can see all user i have selected,and have a chec

  • Movement type 501 in MIGO doing GR for FG Product

    I am using movement type 501 in MIGO doing GR for FG Product, at that time its giving error 'no manual posting allow to GL Account' We dont want to allow any manual posting in this GL . Can be configure this Movement type like that whenever we do GR