Smb crash

Every time I turn on File sharing and select the SMB Windows file sharing the computer crashes.
Lion 10.7.1
Thanks in advance
OC

I have made a few searches and cannot find anything on this particular subject.

Similar Messages

  • SMB crashes Finder

    I have an Inoi NAS hard drive connected to my network using SAMBA. When I try to connect on my MacBook or another MacBook Pro, opening certain folders causes the Finder to crash. Same folder does it on both machines. However, on another Windows laptop, this volume connects flawlessly. I'm pretty sure the problem lays somewhere within OS X's implementation of SMB, but I have no idea what to do to remedy the problem.

    No, that doesn't change anything. I can access the drive from Parallels (XP) running on the MacBook Pro, but no go from within the Finder.

  • MASSIVE OS X Server crashing!  Please help me!  SMB crashes and kills OSXS

    OSX Srvr 10.4.7 on a Mac Pro. I dont know what I did or missed versus every other server I've ever done, but I've got a major problem on my hands. Once a day my users have their access shut off, and i have to re-enable them. Every other morning, smb will crash so hard it kicks everyone off, then workgroup mgr won't respond anymore, and i have to hard power off the computer. This is running my company of roughly 23 users, and this replaced a Windows Server 2003. Not a good impression so far. I have logs I'm happy to post or email to anyone. They're huge, so I've obviously loused something up big time.
    We're doing simple Windows file Sharing, Apple File Sharing, VPN, and eventually FTP. It's also running Kerio Mail Server. Someone please help me!
    Here are some log examples to start with.
    crashreporter.log:
    Wed Sep 20 17:49:42 2006 crashdump[16094]: crashdump started
    Wed Sep 20 17:49:42 2006 crashdump[16094]: Started writing crash report to: /Library/Logs/CrashReporter/smbd.crash.log
    Wed Sep 20 17:49:42 2006 crashdump[16094]: Finished writing crash report to: /Library/Logs/CrashReporter/smbd.crash.log
    Wed Sep 20 17:49:42 2006 crashdump[16097]: crashdump started
    Wed Sep 20 17:49:43 2006 crashdump[16097]: Started writing crash report to: /Library/Logs/CrashReporter/smbd.crash.log
    Wed Sep 20 17:49:43 2006 crashdump[16097]: Finished writing crash report to: /Library/Logs/CrashReporter/smbd.crash.log
    system.log:
    Sep 20 17:49:42 Genesis1 crashdump[16094]: smbd crashed
    Sep 20 17:49:42 Genesis1 crashdump[16094]: crash report written to: /Library/Logs/CrashReporter/smbd.crash.log
    Sep 20 17:49:43 Genesis1 crashdump[16097]: smbd crashed
    Sep 20 17:49:43 Genesis1 crashdump[16097]: crash report written to: /Library/Logs/CrashReporter/smbd.crash.log
    Sep 20 17:51:56 Genesis1 kernel[0]: (16266: ps)tfp: failed on 0:
    Sep 20 17:51:57 Genesis1 kernel[0]: (16267: ps)tfp: failed on 0:
    Sep 20 17:51:58 Genesis1 kernel[0]: (16268: ps)tfp: failed on 0:
    Sep 20 17:51:59 Genesis1 kernel[0]: (16269: ps)tfp: failed on 0:
    Sep 20 17:52:00 Genesis1 kernel[0]: (16270: ps)tfp: failed on 0:
    Sep 20 17:54:21 Genesis1 servermgrd: servermgr_dns: no name available via DNS for 192.168.200.250
    Sep 20 17:54:21 Genesis1 servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
    log.smbd:
    [2006/09/20 17:56:27, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
    writesocketdata: write failure. Error = Broken pipe
    [2006/09/20 17:56:27, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
    write_socket: Error writing 124 bytes to socket 6: ERRNO = Broken pipe
    [2006/09/20 17:56:27, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
    Error writing 124 bytes to client. -1. (Broken pipe)
    [2006/09/20 17:56:27, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
    writesocketdata: write failure. Error = Broken pipe
    [2006/09/20 17:56:27, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
    write_socket: Error writing 53 bytes to socket 6: ERRNO = Broken pipe
    [2006/09/20 17:56:27, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
    Error writing 53 bytes to client. -1. (Broken pipe)
    Please reply here or consider emailing me: [email protected]
    I'm desperate!
    Mac Pro dual 2.66 Xeon   Mac OS X (10.4.7)  

    Hi Bill.
    First please note:
    "servermgr_dns: no name available via DNS for 192.168.200.250
    Sep 20 17:54:21 Genesis1 servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair"
    Your first issue is you need to fix DNS.
    Something needs to be providing forward and reverse DNS lookup for your OS X Server.
    You might not have known this, but now you do: OS X Server -must- have working DNS. You don't need to run DNS on your OS X Server, but it needs working DNS.
    DNS configuration is a bit beyond the scope of this reply, however.
    In the meantime, edit /etc/hosts and do not touch any existing entries
    but add the following line:
    192.168.200.250 Genesis1
    and kill -HUP lookupd. If you're not sure how, perhaps just restart the computer.
    Next up, edit
    /System/Library/LaunchDaemons/smbd.plist , adding the line in bold below:
    <key>ProgramArguments</key>
    <array>
    <string>/usr/sbin/smbd</string>
    <string>-F</string>
    </array>
    Of course, the text in the file itself should NOT be "bold" formatted
    Be very sure to check the permissions on that file, and to leave them the same, or restore them if they change. It's really best to use nano/vi/emacs to edit the file, if you must use a GUI app, then go with TextWrangler or SubEthaEdit, both of which can be found at versiontracker.com
    Let us know how it goes, and I'll send this to your email as well.

  • Mac's and PCs can no longer connect after 10.4.10 Upgrade SMB Crash - Help

    This is my second post on this topic. I have read other similar threads, but none of the advice I have tried has worked so far. We have 4 PCs and 5 Macs at home that were networking nicely until we upgraded the G5 10.4.10. The G5 can browse and connect to any machine on the network. However, no other machine can connect to a shared folder on the G5.
    I installed a clean 10.4.10 on a second hard drive and it works fine. So that eliminates hardware and infrastructure. I really did not want to have to reinstall everything from scratch.
    I performed an Archive and Install and that did not work.
    1) On my G5 I turn on Personal or Windows File Sharing
    2) From another computer PC or Mac I attempt to connect to the shared files
    3) The connection is made most of the time and I can see the folders. However within a few minutes or the second time I attempt to browse the folders, I get an error.
    4) When I return to the G5, the Service is unchecked
    The console log is reporting...
    Aug 19 18:36:02 G5 crashdump14892: smbd crashed
    Aug 19 18:36:02 G5 crashdump14892: crash report written to: /Library/Logs/CrashReporter/smbd.crash.log
    Aug 19 18:59:51 G5 crashdump27414: AppleFileServer crashed
    Aug 19 18:59:52 G5 crashdump27414: crash report written to: /Library/Logs/CrashReporter/AppleFileServer.crash.log
    smbd will crash when attempting a connection from XP
    AppleFileServer will crash when attempting a connection from a Mac
    The AppleFileServer.crash.log reports (first few lines...)
    Binary Images Description:
    0x1000 - 0x132fff AppleFileServer /usr/sbin/AppleFileServer
    0x8fe00000 - 0x8fe52fff dyld 46.12 /usr/lib/dyld
    0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x907bb000 - 0x90894fff com.apple.CoreFoundation 6.4.7 (368.28) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x908dd000 - 0x908ddfff com.apple.CoreServices 10.4 (???)

    Usually whan an Archive & Install doesn't work, it's very few things...
    Bad prefs/plists carried over.
    Some APP or kext or support file not replaced due to permissions, HD Errors, bad aliases, etc.
    Bad info in caches.

  • Smb network shares from W7 PC stop working after a few hours

    I have a W7 pc sharing storage on my network.
    when connecting when first starting my macbook, it connects fine, but after a few hours it drops out, and i am unable to connect to it unless i restart my macbook.
    I have been using "connect to server" to connect my network shares, and when i try to reconnect them using this, it just keeps trying to connect, and wont ever connect even after leaving it to try for over 4 hours (connecting when first starting is fine, taking less than a minute).
    sounds similar to a problem with the 10.6 server, where smb crashes.
    is there a way to restart smb service on the macbook, or even fix it, so that it doesnt have to always be reconnected?
    computer_tim

    computer_tim wrote:
    I have a W7 pc sharing storage on my network.
    when connecting when first starting my macbook, it connects fine, but after a few hours it drops out,
    That's normal. Connections to non-server Windows machines will drop after a period of non-use.
    and i am unable to connect to it unless i restart my macbook.
    That's not normal. You should be able to reconnect at will.
    I have been using "connect to server" to connect my network shares, and when i try to reconnect them using this, it just keeps trying to connect, and wont ever connect even after leaving it to try for over 4 hours (connecting when first starting is fine, taking less than a minute).
    There's a network connectivity problem. That is not how things are supposed to work.
    sounds similar to a problem with the 10.6 server, where smb crashes.
    Okay, you definitely have a network connectivity problem. OS X Server is not supposed to behave that way. What kind of network infrastructure do you have? What make/model routers, switches, hubs, whatever? WIred/wireless? What class cabling or if wireless, what class wireless?
    is there a way to restart smb service on the macbook, or even fix it, so that it doesnt have to always be reconnected?
    Yes. Usually you just disconnect and reconnect at will.
    computer_tim

  • Continual SAMBA crashes - 10.3.9 (7W98)

    We were recently having AFP troubles and while digging through the logs I noticed pretty regular SMB crashes - probably twice a day. We only have a few Windows users and I hadn't heard any complaints so I concentrated on AFP.
    Now that the AFP issues are solved (decaying firewire drive with share BTW) I took the opportunity of the fileserver being down and ran the last two security updates, ran disk utility repair, repair permissions and rebooted 4 days ago. Today I noticed SAMBA crashes in the log about EVERY 10 MINUTES!
    SAMBA seems to be really thrashing and I don't know what to do about it. I would be suspicious of the new security updates if I hadn't seen the less frequent crashes in the log previously. I could trash smb.conf and start over but that seems pretty desperate without any hint of an actual cause. Most of the SAMBA threads seem to be a lot of complaints but without real solutions.
    Anyone have any luck?
    TIA,
    =Tod K
    ******** crash log sample - it appears to always be the same instructions in the crashed thread *********
    Host Name: xxxx.xxxx.edu
    Date/Time: 2005-12-07 13:32:03 -0800
    OS Version: 10.3.9 (Build 7W98)
    Report Version: 2
    Command: smbd
    Path: /usr/sbin/smbd
    Version: ??? (???)
    PID: 26858
    Thread: 0
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
    Thread 0 Crashed:
    0 libSystem.B.dylib 0x90007260 strlen + 0x20
    1 smbd 0x00144360 push_ascii + 0x28
    2 smbd 0x0001c210 reply_trans + 0x47f8
    3 smbd 0x000212f4 api_reply + 0x318
    4 smbd 0x000182fc reply_trans + 0x8e4
    5 smbd 0x00058b64 respondto_all_remaining_localmessages + 0x784
    6 smbd 0x00058c2c respondto_all_remaining_localmessages + 0x84c
    7 smbd 0x00058f90 process_smb + 0x1c8
    8 smbd 0x00059b94 smbd_process + 0x168
    9 smbd 0x001c49ec main + 0x6a4
    10 smbd 0x00003b5c start + 0x1bc
    11 smbd 0x000039d0 start + 0x30
    PPC Thread State:
    srr0: 0x90007260 srr1: 0x0200f030 vrsave: 0x00000000
    cr: 0x24000242 xer: 0x20000004 lr: 0x00144360 ctr: 0x90007240
    r0: 0x0001c210 r1: 0xbfffeae0 r2: 0x84000242 r3: 0xfffffffc
    r4: 0x00000000 r5: 0xfefefeff r6: 0x80808080 r7: 0x00000000
    r8: 0x00000000 r9: 0x00000000 r10: 0x00000006 r11: 0x00244350
    r12: 0x90007240 r13: 0x00000064 r14: 0xbffff2c0 r15: 0x0045a000
    r16: 0x00000013 r17: 0x0000ffe0 r18: 0x0182e800 r19: 0x00000000
    r20: 0x0000ffe0 r21: 0xbffff220 r22: 0xbffff228 r23: 0x0000005c
    r24: 0x00000001 r25: 0x000002b0 r26: 0x0000005c r27: 0xbfffef80
    r28: 0x00000001 r29: 0x00000100 r30: 0x000009e0 r31: 0x00000000
    Binary Images Description:
    0x1000 - 0x23cfff smbd /usr/sbin/smbd
    0x41f000 - 0x435fff opendirectorysam.so /usr/lib/samba/pdb/opendirectorysam.so
    0x47b000 - 0x48cfff opendirectory.so /usr/lib/samba/auth/opendirectory.so
    0x8fe00000 - 0x8fe4ffff dyld /usr/lib/dyld
    0x90000000 - 0x9014ffff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x901c0000 - 0x9026dfff com.apple.CoreFoundation 6.3.8 (299.36) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x902b0000 - 0x90529fff com.apple.CoreServices.CarbonCore 10.3.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x90584000 - 0x905f3fff com.apple.framework.IOKit 1.3.6 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x90610000 - 0x9069afff com.apple.CoreServices.OSServices 3.0.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x90700000 - 0x90700fff com.apple.CoreServices 10.3 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x907c7000 - 0x907cffff libbsm.dylib /usr/lib/libbsm.dylib
    0x907f0000 - 0x907f9fff com.apple.DiskArbitration 2.0.5 /System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbi tration
    0x90810000 - 0x90810fff com.apple.ApplicationServices 1.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x908c5000 - 0x90915fff com.apple.HIServices 1.4.1 (0.0.1d1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x90d00000 - 0x90d1bfff com.apple.SystemConfiguration 1.7.1 (???) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x90d70000 - 0x90dacfff com.apple.LDAPFramework 1.3.3 (37.3.1) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x90dd0000 - 0x90df0fff com.apple.DirectoryService.Framework 1.7.2 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x910b0000 - 0x91101fff com.apple.bom 1.2.5 (63.2) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x912e0000 - 0x912f7fff com.apple.LangAnalysis 1.5.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x913a0000 - 0x9145ffff ColorSync /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x915e0000 - 0x91699fff com.apple.QD 3.4.70 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x916e0000 - 0x91773fff com.apple.print.framework.PrintCore 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x91978000 - 0x91988fff libsasl2.2.0.1.dylib /usr/lib/libsasl2.2.0.1.dylib
    0x92070000 - 0x92096fff com.apple.FindByContent 1.4 (1.2) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
    0x920c0000 - 0x922a7fff com.apple.security 2.3 (176) /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x923c4000 - 0x923fcfff com.apple.AE 1.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
    0x92430000 - 0x92468fff com.apple.LaunchServices 10.3.5 (98.4) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
    0x927f0000 - 0x92827fff com.apple.CFNetwork 1.2.1 (7) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x939a0000 - 0x939b4fff libcups.2.dylib /usr/lib/libcups.2.dylib
    0x939d0000 - 0x939d4fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x943d0000 - 0x94508fff edu.mit.Kerberos 5.0.25 (5.0.1) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x945b0000 - 0x945b9fff libz.1.dylib /usr/lib/libz.1.dylib
    0x94610000 - 0x9462afff libresolv.9.dylib /usr/lib/libresolv.9.dylib
    0x94650000 - 0x946affff com.apple.SearchKit 1.0.2 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x946ed000 - 0x94705fff com.apple.WebServices 1.1.1 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
    0x94c57000 - 0x94f2ffff com.apple.CoreGraphics 1.203.30 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x968d0000 - 0x969b2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
    0x96aa0000 - 0x96acefff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
    0x96b50000 - 0x96bdffff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x96cb0000 - 0x96d9efff libiconv.2.dylib /usr/lib/libiconv.2.dylib
    0x96dc0000 - 0x96dd3fff libpam.1.dylib /usr/lib/libpam.1.dylib
    0x96e12000 - 0x96e25fff com.apple.speech.synthesis.framework 3.2 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x9784a000 - 0x97912fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
    ----- The last log for Windows file service log comes 7 minutes before -----
    [2005/12/07 13:26:15, 2] /SourceCache/samba/samba-60.2/samba/source/nmbd/nmbdbrowsesync.c:announce_local_master_browser_to_domain_masterbrowser(110)
    announcelocal_master_browser_to_domain_masterbrowser:
    We are both a domain and a local master browser for workgroup XMM. Do not announce to ourselves.
    [2005/12/07 13:26:15, 2] /SourceCache/samba/samba-60.2/samba/source/nmbd/nmbdbrowsesync.c:sync_withdmb(154)
    syncwithdmb:
    Initiating sync with domain master browser XSERVER<20> at IP xxx.xxx.171.76 for workgroup XMM
    ----- And the the boot sequence starts after crash ------
    [2005/12/07 13:32:03, 2] /SourceCache/samba/samba-60.2/samba/source/passdb/pdbinterface.c:make_pdb_methodsname(654)
    No builtin backend found, trying to load plugin
    [2005/12/07 13:32:03, 2] /SourceCache/samba/samba-60.2/samba/source/lib/module.c:dosmb_loadmodule(63)
    Module '/usr/lib/samba/pdb/opendirectorysam.so' loaded
    [2005/12/07 13:32:03, 2] /SourceCache/samba/samba-60.2/samba/source/lib/module.c:dosmb_loadmodule(63)
    Module '/usr/lib/samba/auth/opendirectory.so' loaded
    [2005/12/07 13:32:03, 1] pdbods.c:odssamgetsampwrid(2195)
    odssam_getsampwrid: rid <501>
    etc......

    FWIW, your messages were 6 minutes before the crashreport, but there was one thing that seemed odd:
    We are both a domain and a local master browser for workgroup XMM. Do not announce to ourselves.
    and:
    Initiating sync with domain master browser XSERVER<20> at IP xxx.xxx.171.76 for workgroup XMM
    AFAIK, there should only be one domain master browser, so why, if this machine is both domain and local master browser is it syncing with domain master browser XSERVER<20> at IP xxx.xxx.171.76?
    Roger

  • Clients can't rejoin domain after server clean install

    Hello, I've got an issue with having client computers rejoin the domain after reinstalling the server software. Another post I read suggested saving the plist files to get the settings the same, but I need to reconfigure manually to eliminate some other problems we've been having.
    We've got an Xserve running 10.4.8 with a mix of XP and Tiger clients all authenticating with the server. Our XP clients have remote profiles converted to local and our Tiger clients use mobile accounts. Generally things were running OK, but we kept having some authentication issues and have SMB crashes. In reviewing our log files it was suggested that our Open Directory was messed up (probably during our upgrade from 10.3 to 10.4) and that a clean install was the best course of action. The server has been running 24x7 for over 3 years without any signifigant maintenance, so this seemed like a good idea.
    Everything was going great. I did the clean install and had DNS and DHCP configured and working, then started setting up Open Directory as the PDC and Windows Services as the Primary WINS. I had intended to recreate the user accounts because I didn't want to reintroduce problems by restoring the settings, however when I added one account and tested logging in on a XP machine it couldn't authenticate even though the domain name and user name was the same as before (short names too). On a whim, I moved the computer from the domain to WORKGROUP and then rejoined the (new) domain. Upon login it created a new roaming profile named user.domain instead of using the other account already there. On the XP client in accounts, the old profile showed up as unknown. I then went to a Mac and tried to log in and had similiar issues not finding the authenticating server.
    After pulling my hair out this evening and realizing that there was no way I was going to have the office operation in the morning, I did a full restore from backup and pretended like I hadn't just wasted my weekend. After I got the server running, I was able to get my client machines to see the domain again and all is as it was.
    Soooo, now the question is how do I create a clean installation with newly created user accounts and get the client computers to recognize the domain server as the same old one? Is there a hidden domain ID or something that is telling the client computers that it isn't the same domain or LDAP server? Any suggestions would be greatly appreciated.
    Thanks.
    xserve G4 & XRaid   Mac OS X (10.4.8)  

    Sorry, to clarify I did not want to use the archive & restore because I didn't want to reintroduce the errors I was trying to eliminate. I setup the Open Directory as a PDC from scratch and then ran into the client authtenication issue. In a desperate attempt to salvage the situation I did restore the previous settings which (A) didn't work and (B) may have made things worse because I already had created some groups and a few users and ended up with groups with duplicate IDs. That was when I scrapped everything and restored the disk from backup.
    Your idea of using export/import is a slightly different avenue. However, now that I'm thinking about it, I didn't even get far enough for the user profiles to be an issue because the client computers weren't even communicating with the server to get the list of users (the Macs log-in by selecting a user name from a list).
    Does export/import of a computer list work? I think I tried to import the computer list last night and the one I had only contained the Macs and these didn't preserve the MAC address info for some reason. I didn't have an export of the XP machines, but tried to manually add them to the list with no success.
    Thanks again for your help.

  • Xserve disconnecting without warning

    At my work we have a Xserve server to backup and let us share files through our network. All our computers using Snow Leopard are frequently disconnected from folders we are in. The server brings us back to the home folder and we have to do all the path to the working folder again. This is really annoying and even the mac support where we bought the machine have no idea of what is happenning.
    Also it happens that a folder that has been used is flashing and duplicating it self onscreen (only virtually, not real duplicates).
    Please any help would be greatly appreciated,
    Éric

    Two really basic suggestions. First, have you looked at the server logs? What is happening at the moment of the reset. Use Console.app (found in /Applications/Utilities) to review logs. Also look in /Library/Logs/CrashReporter. Are there files in there associated with AFP or SMB crashing? Review those files to see if you can determine why. The system.log is also very useful as it will report the crash event.
    Secondly, have you checked the server's data volume for corruption?
    Hope this helps

  • Expanding XServe RAID set - stuck at 99%

    We have an XServe RAID.  One side had a RAID 5 set consisting of 6x500GB HDD's.  We came to within 60Gb of filling it up and therefore initiated expansion of RAID set to 7th drive on Saturday.  This was progressing 1% / 40 mins.  We calculated that it would not complete before Monday when users would start hammering it, but after testing it, it seemed to be working perfectly fine while expanding.  Writing/reading speed did not seem to be noticeably affected and we decided that all seemed well.
    Monday started off well.  Not not a single user noticed reduced speed or any other problems - This was until about 3pm when the file server hosting AFP & SMB crashed!  Not good!  Upon restart, the RAID set would not mount again.
    RAID Admin shows the expansion at 99%.   I was hoping that the RAID set could be mounted again once it completed to 100%, but it does not seem like this will be happening anytime soon - it has been stuck on 99% for about 6 hours now and I don't know when/if it will ever finish.  (Previously 1% every 40mins)
    The fibre channel preference pane shows "Link Established" to the XServe RAID, similarly the RAID Utility shows "Link Up" to server.  The RAID, however, does not appear in Disk Utility - even after restarts.
    Does anyone out there have experience expanding a RAID Set on an XServe RAID?  Does it usually stall at 99%?  How long does it take to finish once it has reached 99%?
    Is there anything I can do to try and get the RAID Set mounted before it finishes its expansion?  It's now 8pm here (GMT+8) and users have finished for the day, but we only have about 12 hours before it needs to be up and running again!
    I am out of ideas to try.  Any help would be greatly appreciated.
    Thanks

    Curiously, more output from the above-mentioned 3rd party tool gives:
    $ ./xserve-raid-info
    Use of uninitialized value in string at ./xserve-raid-info line 655.
    Use of uninitialized value in string at ./xserve-raid-info line 655.
    Use of uninitialized value in string at ./xserve-raid-info line 655.
    Use of uninitialized value in string at ./xserve-raid-info line 655.
    Name: Xserve-RAID
    States:
      RAIDs: optimal
      Components: optimal
      Fibre Channel: optimal
      Network: warning
    Warnings:
      The top network link is down.
    Upper Controller Info:
      Status: ok
      Firmware Version: 1.5.1f2/50
      Up Time: 262 days 1 hr
      Temperature: 75.2 deg F
      Write Cache: disabled
      Prefetch Size: 8 stripes (512 KB/disk)
      Fibre Channel: link up
        Topology: arbitrated loop
        Speed: 2Gb/sec
      Network: link down
        IP Address: 192.168.30.11
        Subnet Mask: 255.255.255.0
    Lower Controller Info:
      Status: ok
      Firmware Version: 1.5.1f2/50
      Up Time: 262 days 1 hr
      Temperature: 82.4 deg F
      Write Cache: disabled
      Prefetch Size: 8 stripes (512 KB/disk)
      Fibre Channel: link up
        Topology: arbitrated loop
        Speed: 2Gb/sec
      Network: link up
        IP Address: 192.168.30.21
        Subnet Mask: 255.255.255.0
    In RAID Admin, I've added systems using 192.168.30.11 (supposedly - link down).
    I can NOT connect using 192.168.30.21 - it says incorrect password even though I know I am entering the correct one...

  • HT4889 using migration from mac to mac, freezes after a few hours.

    I'm using migration from my old mac to my new one, it's taking forever and freezes after a few hours.
    Help

    computer_tim wrote:
    I have a W7 pc sharing storage on my network.
    when connecting when first starting my macbook, it connects fine, but after a few hours it drops out,
    That's normal. Connections to non-server Windows machines will drop after a period of non-use.
    and i am unable to connect to it unless i restart my macbook.
    That's not normal. You should be able to reconnect at will.
    I have been using "connect to server" to connect my network shares, and when i try to reconnect them using this, it just keeps trying to connect, and wont ever connect even after leaving it to try for over 4 hours (connecting when first starting is fine, taking less than a minute).
    There's a network connectivity problem. That is not how things are supposed to work.
    sounds similar to a problem with the 10.6 server, where smb crashes.
    Okay, you definitely have a network connectivity problem. OS X Server is not supposed to behave that way. What kind of network infrastructure do you have? What make/model routers, switches, hubs, whatever? WIred/wireless? What class cabling or if wireless, what class wireless?
    is there a way to restart smb service on the macbook, or even fix it, so that it doesnt have to always be reconnected?
    Yes. Usually you just disconnect and reconnect at will.
    computer_tim

  • Finder Crash when accessing SMB share

    iMac 2.16 GHz Intel Core Duo.
    When opening a particular share on an SMB server, the Finder crashes and relaunches. Does not happen on other shares on the same server. Happens for all users on this Mac. Does not happen on other Macs.
    Have tried deleting finder.plist and windowserver.plist, and cleaning caches with Onyx and Cocktail.
    Note: also crashes on some DMGs.
      Mac OS X (10.4.8)  

    I have also tried Techtool and Repair Permissions.

  • Mac 10.9.5, SMB and regular crashing

    Below is a crash log.  This is a regular occurrence, happens at least twice a week for many of my users.  Can someone please assist me?
    My users are all running Mac OS X 10.9.5, using Illustrator CC 2014 and connect to a SMB server.
    Anonymous UUID:       005681BE-D84C-3D16-0E6D-E29098E1760A
    Mon Dec 15 12:03:13 2014
    panic(cpu 3 caller 0xffffff800eedc43e): Kernel trap at 0xffffff7f913b157b, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x0000000100000028, CR3: 0x0000000137a62000, CR4: 0x0000000000000660
    RAX: 0x0000000100000028, RBX: 0xffffff802795f968, RCX: 0x00000000031f0000, RDX: 0xffffff802795f968
    RSP: 0xffffff811926a930, RBP: 0xffffff811926b190, RSI: 0x0000000000000000, RDI: 0xffffff802795f968
    R8:  0xffffff811926b1a0, R9:  0x000000000000000c, R10: 0x0000000000000270, R11: 0x0000000000000040
    R12: 0x0000000000000001, R13: 0xffffff811926a968, R14: 0x0000000100000000, R15: 0xffffff811926b1a0
    RFL: 0x0000000000010202, RIP: 0xffffff7f913b157b, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000100000028, Error code: 0x0000000000000000, Fault CPU: 0x3
    Backtrace (CPU 3), Frame : Return Address
    0xffffff811926a5c0 : 0xffffff800ee22f79
    0xffffff811926a640 : 0xffffff800eedc43e
    0xffffff811926a810 : 0xffffff800eef3976
    0xffffff811926a830 : 0xffffff7f913b157b
    0xffffff811926b190 : 0xffffff7f913e2373
    0xffffff811926b1d0 : 0xffffff7f913d4395
    0xffffff811926b270 : 0xffffff7f913dc0f2
    0xffffff811926b2d0 : 0xffffff7f913db8f2
    0xffffff811926b3d0 : 0xffffff7f913dfe19
    0xffffff811926b470 : 0xffffff7f913b54e0
    0xffffff811926b570 : 0xffffff7f913bf2ac
    0xffffff811926b710 : 0xffffff7f913b7c5c
    0xffffff811926b9f0 : 0xffffff800effd897
    0xffffff811926bad0 : 0xffffff800eff4bc0
    0xffffff811926bb70 : 0xffffff800efe6c65
    0xffffff811926bc20 : 0xffffff800efe7522
    0xffffff811926bf50 : 0xffffff800f240c63
    0xffffff811926bfb0 : 0xffffff800eef4176
          Kernel Extensions in backtrace:
             com.apple.filesystems.smbfs(2.0.3)[EC68D5F4-45EA-379A-B723-AEEDE9C94055]@0xffffff7f913a20 00->0xffffff7f913edfff
                dependency: com.apple.kec.corecrypto(1.0)[DB137B94-65D2-32AF-B5BC-80A360E104C3]@0xffffff7f8f829000
                dependency: com.apple.kext.triggers(1.0)[A7018A2E-1C0C-37B8-9382-67786A396EAF]@0xffffff7f8f870000
    BSD process name corresponding to current thread: Finder
    Mac OS version:
    13F34
    Kernel version:
    Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64
    Kernel UUID: 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0
    Kernel slide:     0x000000000ec00000
    Kernel text base: 0xffffff800ee00000
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 125133204294951
    last loaded kext at 113950837174360: com.apple.driver.AppleUSBHIDKeyboard 170.15 (addr 0xffffff7f9139e000, size 12288)
    last unloaded kext at 114074786416309: com.apple.driver.AppleUSBCDC 4.2.1b5 (addr 0xffffff7f91394000, size 16384)
    loaded kexts:

    Erik,
    Here it is always recommended to open/save AI documents from/to own harddisk, and to only copy from/to externals such as local server/whatever.
    The reason is that with the latter, AI files tend to get corrupted sooner or later, so you may be lucky for a while but it hurts when your luck runs out.
    In addition to the (far greater) risk of file corruption, some issues are mentioned here:
    http://helpx.adobe.com/illustrator/kb/illustrator-support-networks-removable-media.html

  • Smb sharing problem, smbd crash when connecting

    hi
    i installed leopard now 2 months ago and since then i try to connect to my mac from my linux vdr and from my windows xp laptop. when i try to connect, i get the following errors on the mac:
    in system log:
    +May 3 22:59:33 bkmac com.apple.launchd[1] (org.samba.smbd[189]): Stray process with PGID equal to this dead job: PID 262 PPID 1 smbd+
    +May 3 22:59:33 bkmac com.apple.launchd[1] (org.samba.smbd[189]): Stray process with PGID equal to this dead job: PID 191 PPID 1 smbd+
    +May 3 23:00:11 bkmac com.apple.launchd[1] (org.samba.smbd[297]): Stray process with PGID equal to this dead job: PID 300 PPID 1 smbd+
    +May 3 23:00:11 bkmac DirectoryService[11]: Failed Authentication return is being delayed due to over five recent auth failures for username: bk.+
    +May 3 23:00:55 bkmac ReportCrash[324]: Formulating crash report for process smbd[318]+
    +May 3 23:00:55 bkmac ReportCrash[324]: Saved crashreport to /Library/Logs/CrashReporter/smbd2009-05-03-230054bkmac.crash using uid: 0 gid: 0, euid: 0 egid: 0+
    in the log.smbd it says
    +2009/05/03 23:00:54, 0, pid=318] /SourceCache/samba/samba-187.8/samba/source/lib/fault.c:fault_report(41)+
    ===============================================================
    +2009/05/03 23:00:54, 0, pid=318] /SourceCache/samba/samba-187.8/samba/source/lib/fault.c:fault_report(42)+
    +INTERNAL ERROR: Signal 10 in pid 318 (3.0.25b-apple)+
    +Please read the Trouble-Shooting section of the Samba3-HOWTO+
    +2009/05/03 23:00:54, 0, pid=318] /SourceCache/samba/samba-187.8/samba/source/lib/fault.c:fault_report(44)+
    +From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf+
    +2009/05/03 23:00:54, 0, pid=318] /SourceCache/samba/samba-187.8/samba/source/lib/fault.c:fault_report(45)+
    ===============================================================
    +2009/05/03 23:00:54, 0, pid=318] /SourceCache/samba/samba-187.8/samba/source/lib/util.c:smb_panic(1650)+
    +PANIC (pid 318): internal error+
    and in the .crash file:
    +Process: smbd [318]+
    +Path: /usr/sbin/smbd+
    +Identifier: smbd+
    +Version: ??? (???)+
    +Code Type: X86 (Native)+
    +Parent Process: smbd [316]+
    +Date/Time: 2009-05-03 23:00:54.791 0200
    +OS Version: Mac OS X 10.5.6 (9G66)+
    +Report Version: 6+
    +Exception Type: EXCBADACCESS (SIGABRT)+
    +Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000014+
    +Crashed Thread: 0+
    +Application Specific Information:+
    +internal error+
    +* single-threaded process forked *+
    +Thread 0 Crashed:+
    + 0 libSystem.B.dylib 0x95d20e42 __kill 10+
    + 1 libSystem.B.dylib 0x95d9323a raise 26+
    + 2 libSystem.B.dylib 0x95d9f679 abort 73+
    + 3 smbd 0x001af62a dump_core 380+
    + 4 smbd 0x001bff90 readdirname 0+
    + 5 smbd 0x001af222 fault_setup 0+
    + 6 libSystem.B.dylib 0x95d1f2bb _sigtramp 43+
    + 7 ??? 0xffffffff 0 4294967295+
    + 8 smbd 0x0007f643 find_service 3897+
    + 9 smbd 0x0008149d make_connection 1682+
    + 10 smbd 0x0003a0e0 replytcon_andX 1160+
    + 11 smbd 0x0007d233 get_OutBuffer 1433+
    + 12 smbd 0x0007d506 chain_reply 577+
    + 13 smbd 0x00051e17 replysesssetup_andX 4836+
    + 14 smbd 0x0007d233 get_OutBuffer 1433+
    + 15 smbd 0x0007e017 smbd_process 2652+
    + 16 smbd 0x0027015f main 5076+
    + 17 smbd 0x000020ea start 54+
    +Thread 0 crashed with X86 Thread State (32-bit):+
    +eax: 0x00000000 ebx: 0x95d9f639 ecx: 0xbfffc3cc edx: 0x95d20e42+
    +edi: 0x002ca485 esi: 0x003176c0 ebp: 0xbfffc3e8 esp: 0xbfffc3cc+
    +ss: 0x0000001f efl: 0x00000282 eip: 0x95d20e42 cs: 0x00000007+
    +ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037+
    +cr2: 0x0034be4d+
    is there a known solution for this problem? any way to fix that?
    thanks
    bk

    You're sharing an SMB volume over the internet?
    I don't mean to sound rude, but are you nuts?
    I can't think of anyone, anywhere who would advocate this setup, especially since you're enabling guest access, too.
    If you really, really, really, really, really need to do it, have you checked your port forwarding on your router? and have you checked with your ISP to see if they have a clue, and if they're actively blocking port 139. Hopefully they are, since that will force you to use a different protocol.
    If you need to provide file access to remote users, consider enabling the VPN server built into Mac OS X Server and having the users connect over VPN. That way they appear as a local user, the data transfer is encrypted over the internet and you can control access to the resources.

  • Launch Services crashing - AFP, SMB, NTFS, exFAT, FAT32 all unmountable

    My Mac Pro was working fine until this month hit... first I noticed that I could no longer mount my network shares (AFP and SMB shares on a Drobo 5n). My first assumption was that there was something wrong with my shares, but that's not the case as every other computer and device I have has no issues connecting and mounting the shares. Not only that, but my Windows partition on this Mac Pro connects fine as well. That's when I noticed my Windows partitions were no longer mountable in OS X either. So I ran some tests with a flash drive in disk utility, after formatting the drive in exFAT, FAT32 or NTFS the flash drive is no longer mountable... HFS still mounts of course, but not anything else.
    So at this point, I've got AFP, SMB, NTFS, exFAT and FAT32 all completely unsuable in OS X. Pretty messed up.
    Taking a look at console shows the same messages over and over again:
    5/3/13 11:49:30.314 PM ReportCrash[11888]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    5/3/13 11:49:30.314 PM ReportCrash[11888]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    5/3/13 11:49:30.314 PM ReportCrash[11888]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    5/3/13 11:49:30.314 PM ReportCrash[11888]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    5/3/13 11:49:30.314 PM ReportCrash[11888]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    5/3/13 11:49:30.314 PM ReportCrash[11888]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    5/3/13 11:49:30.314 PM ReportCrash[11888]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    5/3/13 11:49:30.314 PM ReportCrash[11888]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    5/3/13 11:49:30.314 PM ReportCrash[11888]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    5/3/13 11:49:30.314 PM ReportCrash[11888]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    5/3/13 11:49:30.328 PM com.apple.kextcache[11922]: Child process /usr/sbin/kextcache[11923] exited due to signal 6.
    5/3/13 11:49:30.328 PM com.apple.kextcache[11922]: Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.
    5/3/13 11:49:30.329 PM com.apple.kextd[11869]: kextcache error while updating / (error count: 10)
    5/3/13 11:49:30.329 PM com.apple.kextd[11869]: async child pid 11922 exited with status 6
    5/3/13 11:49:30.362 PM ReportCrash[11888]: Saved crash report for kextcache[11923] version 268.12 to /Library/Logs/DiagnosticReports/kextcache_2013-05-03-234930_LaBonty.crash
    I've tried literally everything I can think of... clearing caches, repairing disk permissions, rebuilding launch services, rebuilding spotlight, rebuilding the kext cache, running maintence scripts, etc. etc.... nothing has helped.

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. You won't be able to mount network shares, but a flash drive should mount. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • App started from SMB-Share crashes frequently!

    Hello!
    I have a customer that has to start a medical program via SMB share. With Server 10.6.8 there was no trouble at all - since we replaced the server with Server 2.2.2 we are in big trouble
    The customer uses Windows 7 as client systems and connects to a share at the Mountain Lion server. The clients can connect to the share without any trouble, but when I start the application the trouble begins.
    Sometimes the app crashes immedialtly, sometimes the app runs for hours and suddently crashes. A message pops up telling "The program BlahBlah.exe does not react anymore" and thats it. Sometimes the application crashes five times a day at one client while at the same time at another client it runs stable.
    So the crashes do not occure at the same time on all clients, it is intermittend. Sometimes the app does not crash at all during the day at one client, the next day it crashes 5-10 times at the same client.
    Most of the clients are freshly installed Windows 7 systems.
    I setup the timeouts at the Registry as mentioned in another discussion - frist this seams to help, but today the customer called and told me that today every thing looks like before the app crashes intermittend on every client.
    I setup smbd with the -debug flag but I can not see that this changes anything in logging messages. The eventprotocol from Windows tells me that it tried to load a dll but the network share was not available.
    When I browse the network share when a crash occured I can not see any problems - but I see lots of SMB logins after a crash. Looks like Windows trys to reconnect. AFAIK the connection was never lost.
    The customer has a mac mini server, 16GB RAM with a Promise Thudnerbolt RAID running Mountain Lion Server 2.2.2.
    Every help is highly welcome, bye
    Christoph

    Hello!
    I have a customer that has to start a medical program via SMB share. With Server 10.6.8 there was no trouble at all - since we replaced the server with Server 2.2.2 we are in big trouble
    The customer uses Windows 7 as client systems and connects to a share at the Mountain Lion server. The clients can connect to the share without any trouble, but when I start the application the trouble begins.
    Sometimes the app crashes immedialtly, sometimes the app runs for hours and suddently crashes. A message pops up telling "The program BlahBlah.exe does not react anymore" and thats it. Sometimes the application crashes five times a day at one client while at the same time at another client it runs stable.
    So the crashes do not occure at the same time on all clients, it is intermittend. Sometimes the app does not crash at all during the day at one client, the next day it crashes 5-10 times at the same client.
    Most of the clients are freshly installed Windows 7 systems.
    I setup the timeouts at the Registry as mentioned in another discussion - frist this seams to help, but today the customer called and told me that today every thing looks like before the app crashes intermittend on every client.
    I setup smbd with the -debug flag but I can not see that this changes anything in logging messages. The eventprotocol from Windows tells me that it tried to load a dll but the network share was not available.
    When I browse the network share when a crash occured I can not see any problems - but I see lots of SMB logins after a crash. Looks like Windows trys to reconnect. AFAIK the connection was never lost.
    The customer has a mac mini server, 16GB RAM with a Promise Thudnerbolt RAID running Mountain Lion Server 2.2.2.
    Every help is highly welcome, bye
    Christoph

Maybe you are looking for