SMB Sharing - Mac OS X Server 10.5.8 - Windows XP 64

Hi,
we are sharing a (metaSAN) volume via SMB and AFP from an Xserve with Mac OS X Server 10.5.8. Everything seems to be fine except SMB/CIFS connections from clients with Windows XP x64 to the Xserve: when copying files from the server to the client the process suddenly gets very slow, it stucks... Sometimes it is copying continously. AFP/SMB connections from Mac OS X clients are working fine...
Any ideas?
Kind regards,
Martin.

I don't have a solution for you. But I do remember reading about this one. Apparently what happens is that beneath the surface, the connection attempt is repeated on failure, using differnet authentication protocols. And so one user login attempt with a bad password, leads to three attempts beneath the surface, and "the boot". But unfortunately I don't remember what the solution is, as I was researching for a completely different issue when I read this.

Similar Messages

  • MAC OS X server - file services for Windows

    I have the Xserve setup and it's available for Mac clients to add data. Problem is, I can see it with windows machines, but can't access it.
    If I do run-->\\server--> it prompts me for a username and password. I'm a domain admin and that should allow me in as it is integrated with AD.
    any suggestions?
    MacBook PRO   Mac OS X (10.4.8)   IBM T60P

    In addition to the directory question, have you shared specific directories via SMB?
    By default, nothing is shared via SMB - you need to use Workgroup Manager to enable the directories you want to share.

  • SMB Sharing, my entire "username"/"account" is visible from Windows 7

    I have a windows sharing enabled, my username's public folder,
    but when I view the files share on the network, the entire user account is visible,
    I even manage to copy files to the "Desktop" of the mac.
    Could this be due to me renaming my "account".

    me too, help!

  • Windows Client log to the Mac Os X Server ?

    Hello everybody
    I would like to create a network with Mac OS X Server. I have Windows PC's that would also be in the network.
    Does windows clients can connect to the Mac Server with a username and password ?
    Thank you.

    At the simplest, sure, Microsoft Windows clients can connect to OS X Server services with appropriate credentials.  Mail and file sharing, for instance. 
    Beyond password-based authentication, a more advanced configuration is probably not as simple nor as easy as you might want.   Windows clients really want to use Microsoft Active Directory here and Kerberos authentication probably won't get you where you want.   (This assuming that you can get the Windows clients to accept OS X Server Kerberos authentication.)  
    The usual approach for single sign-on in heterogeneous environments is the so-called Magic Triangle configuration with both Microsoft Active Directory running on a Windows Server and Open Directory running on OS X Server.   This involves the two domains communicating.  It might be easier to get OS X clients operating off Windows Server, particularly with the use of profiles in more recent versions.
    As an alternative to Windows Server, recent versions of the Samba server package include authentication services compatible with Active Directory, and you may be able to get your Windows clients to authenticate to that, and build that as part of a Magic Triangle configuration.  You'd need to download and configure the Samba server, and get the Samba AD support working.
    Related discussions and documentation here and here and maybe this thread.  There are other discussions.

  • SMB Slow connection with upgrade to SnoW Leopard and Windows Clients.

    <pre>
    Dear,
    I have now upgraded my MAC OS X LEOPARD 10,5,8 to new SNOW LEOPARD 10,6,2 and if some problems disappear I have a newer big one !
    Now every time a Windows CLient try to connect to a SMB Share of SL server that take a long time about 10-15 seconds to open after that depending on client OS that could be nice for a moment (windows 7 and XP) or browsing stay very slow like for 2003 server connecting to Share on S.Leopard.
    Could you please help me.
    My SL are the main SMB share computer with all data it is connect like other clients to AD (SBS2003).
    I have a SBS2003 server that are Master of Domain
    and a Server 2008 acting like Terminal Server also member server of domain.
    Here are kind of log I receive from SMBD.LOG: I suppose the Credentials problem when connecting are my explanation but how to avoid that !
    2009/11/14 13:37:06, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/reply.c:reply_special(332)
    netbios connect: name1=MACSRV name2=NOMAD
    2009/11/14 13:37:06, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/reply.c:reply_special(339)
    netbios connect: local=macsrv remote=nomad, name type = 0
    2009/11/14 13:37:08, 2, pid=64794 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
    Module '/usr/lib/samba/auth/odsam.dylib' loaded
    2009/11/14 13:37:10, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/sesssetup.c:setupnew_vcsession(1273)
    setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
    2009/11/14 13:37:10, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
    Module '/usr/lib/samba/auth/odsam.dylib' loaded
    2009/11/14 13:37:18, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/sesssetup.c:setupnew_vcsession(1273)
    setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
    2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:getopendirectoryauthenticator(247)
    failed to read DomainAdmin credentials, err=67 fd=15 errno=2
    2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:opendirectoryuser_auth_and_sessionkey(580)
    dsDoDirNodeAuthOnRecordType gave -14091 eDSAuthMethodNotSupported
    2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/auth/authodsam.c:opendirectory_smb_pwd_checkntlmv1(387)
    opendirectoryuser_auth_and_sessionkey gave -14091 eDSAuthMethodNotSupported
    2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:getopendirectoryauthenticator(247)
    failed to read DomainAdmin credentials, err=67 fd=28 errno=2
    2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/auth/auth.c:checkntlmpassword(309)
    checkntlmpassword: authentication for user fabrice -> fabrice -> fabrice succeeded
    2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
    Module '/usr/lib/samba/vfs/darwin_streams.dylib' loaded
    2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
    Module '/usr/lib/samba/vfs/darwinacl.dylib' loaded
    2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
    Module '/usr/lib/samba/vfs/notify_kqueue.dylib' loaded
    2009/11/14 13:37:28, 1, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/service.c:makeconnectionsnum(1092)
    nomad (192.168.2.20) connect to service NetDown initially as user fabrice (uid=501, gid=20) (pid 64803)
    I also have some kind of following message:
    2009/11/14 13:35:18, 0, pid=64579 /SourceCache/samba/samba-235/samba/source/lib/utilsock.c:readdata(534)
    read_data: read failure for 4 bytes to client 192.168.2.20. Error = Connection reset by peer
    NOte that initialy I don't have problem with MAC OS Client but to be sure they use SMB I have desactived AFP server on SNOW LEOPARD SERVER and now they can't browse the share in finder but when connection via COMMAND+K and SMB://server/share that give now the same error but a little bit faster than windows clients.
    Could you help me to troubleshout that problem ?
    Thanks for your help.
    Felee
    </pre>

    Dear CarlosGBA,
    So when you put 2 computers of your network in WORKGROUP in place of DOMAIN the 38 others works fine ? Strange ?
    I have about 15 computers, some are already in workgroup other are linux smb other MAC, the data server are MAC OS X SL, the problem appear for all windows machines, I have try to dissable NTLMV2 and Kerberos since it is probably the faulty element with opendirectory,but always without success !
    I don't know what I can do to trouble shout, I hope next release 10.6.3 come soon and correct about all SMB problem ! Probably a dream only ! Since I ask my self if Apple want to correct something andwhy is this problem let without solutionso long ! For a company it is a big problem.I suppose that Apple never read this forum and never answer our problem ! May be I should contact the support phone to be helped !
    Thanks for you help.

  • OS 10.4 clients cannot access Shared Mac folder on W2k Server - URGENT

    We have a network of about 25 computers, 10 or so of them are Mac OS 10.4, the rest are Win XP Pro PCs. We have a server dedicated to file sharing. We basically have one main shared folder called "FILES". This is shared for PCs and Macs. Recently after a restart of the server (for regular maintenance), the Macs could not see the shared Mac volume (FILES), PCs could access the share without a problem. After a few minutes (15 or so) the Macs could all of a sudden see the share and
    everything was fine.
    However, we just restarted the server again and we're having the same issue again. The difference is, this time, after waiting for a few hours, the Macs still cannot see the Mac Share. The macs connect to the server via TCP/IP, the users use their usernames and passwords and can connect to the server, however, the only volume they see is the Micrsoft UAM volume.
    When we created a different folder and shared it (through MMC), the Macs could see and access that one.
    We get an Event ID 12061 in the System Event Log as the user tries to connect to the share. I found a Microsoft KB article, but no solution to the problem was given. http://support.microsoft.com/kb/q136300/
    Here are some things I have tried to remedy the issue, please keep in mind we cannot change the name of the share (FILES) becuase of the thousands of file mappings in quark, etc.:
    Again Restarted Server
    Stopped Sharing the folder, then reshared it
    Stopped sharing the folder
    Uninstalled / Reinstalled Appletalk Protocol from network adapter
    Uninstalled / Reinstalled File Services for Macintosh [Restarted]
    Uninstalled / Reinstalled Appletalk Protocol from network adapter again [Restarted]
    Reshared the folder
    Created a new mac share called TEST (Macs could see and access)
    Moved data from Files to TEST, now Macs could not see TEST
    Moved data back to FILES
    Created a folder called FILES2, moved data from FILES to FILES2
    Stopped sharing FILES (PC and Mac), renamed FILES to FILES1
    Renamed FILES2 to FILES (Macs could not see volume)
    It seems as though the problem is with an individual file or two, which sort of corresponds the what Microsoft has written regarding the error.
    Has anyone had any experience with this issue? Any insight or solution to this issue is greatly appreciated.
    Thank you!

    It's very important to be as specific as possible when discussion network service access. In your question, it sounds like you want the macs to attach to FILES using SMB/CIFS, but you also call it a Mac share, so it's not obvious if you mean an AFP share or just a share for Macs to use.
    You should know that the Macs can connect to either AFP or SMB volumes, and they can browse for SMB over TCP/IP and AFP over both TCP/IP and Appletalk (Appletalk must be turned on and browsing active in Directory Access).
    Connecting via SMB to a volume hosted on Windows2K or higher server will fail with the default settings, which require secure connections not supported by Mac OS X (because Samba doesn't support it). To overcome that problem, see this article:
    http://www.macosxhints.com/article.php?story=20030922153448490&query=-5000
    (scroll down to one of the top-level replies, which explains in detail how to deactivate secure connections)
    You might also be able to improve reliability by editing the SMB settings in Directory Access and setting a WINS server, but it depends on your network.

  • Mixed PC/Mac environment with Mac 10.6 server sharing issue

    In this mixed environment, I can't figure out how to get new documents created on the Macs (saved onto a shared folder on the server) to be set as read/write for the PC user. I'm not a Mac system admin, just to start with, but I do use Macs all the time and feel like I know what I'm doing. This is just escaping me.
    So new documents and folders, when created by a Mac, are created with permissions that give user group "staff" and "everyone" read only access, and give the "nobody" account ready and write access. If I manually go in I can change it so that staff has read/write, and propagate that to contained items, and then everything is editable. But new documents in that folder (any everywhere) are still not. Can anyone help me figure out what setting must be changed so that new documents and folders created by Mac clients are created with staff having read/write permissions?
    I'll be back at the client site tomorrow so I'm really hoping (and expectED) to have an answer by then.
    Thanks!

    http://manuals.info.apple.com/en_US/FileServerAdmin_v10.6.pdf
    Basically you want to have your members (or groups) added to the ACL under the filesystem being exported over AFP / SMB.

  • Mac OS X Server, File Sharing, Permission

    Hi All,
              I’m trying to use Mac os X server Maverick in a small team within my
              organization. I was able to successfully install and setup the server, which
              resides in a local network. I did the following setup:
         1 )  Open Directory Setup
          2 )  File Sharing ,  /Users , available for home directory over AFP
          3 )  Created Network users with home folder pointing to /Users
          4 )  Bound Clients to the server
          5 )  XCode Server Setup with git repository
          Users now can login using their own account and their home folder 
          is loaded from the server. Unfortunately there  are issues. Clients are having permission issues,
          which we have never encountered on local machines before we switched to using XCode Server. 
          Here is a list of some of the issues so far 
          Xcode issues on client computer:
               a)   When creating a XCode project, it reports the error “Couldn’t not find build module Drawin” when clicking create
                 button.I found online a workaround fix that supposedly works, which is to set "Enable Modules (C and Objective C)"
                  to No. But we didn’t have to do this before using XCode server.
               b )  When committing to git repo , the following error happens “fatal: Repository has been updated ,
                    but unable to write to new_index. Check the disk is not full or quota is not exceeded ,
                    and then "git reset HEAD"   to recover”  Another work around we found online is to do on the client, 
                   cp index backup ; mv backup index
           We don’t want to have to do this every time we create a project, what could be wrong with the setup?

    You need to run Server Admin and click on the File Sharing icon at the top. Then click on Share Points, and Browse. You then browse to the folder you want to set the permissions on.
    You will see in the bottom half of the window the current permissions. While in theory you can use just POSIX permissions, Snow Leopard prefers using ACL permissions. So as an example to set a folder to be only accessible by members of a specific group and to deny access to everyone else you would do the following.
    Click on the + symbol at the bottom
    A window will open listing all your users and groups, click on groups at the top
    Find the special 'Everyone' group and drag it to the ACL section
    Find the group you want to give access to and also drag that to the ACL section but make sure it is above the Everyone group as higher setting override lower settings
    Set the Everyone group to Deny Read permission, this will prevent them being able to access this folder
    Set the group you do want to have access to Allow Read or Allow Read/Write, the first would let them only be able to read, the second also allows them to create files or modify files.
    Now click on the Save button in the bottom right.
    You might also want to click on the gear wheel symbol and choose 'Propagate permissions' if you want to apply these permissions to all the files and folders within this folder.

  • Issues with Mac OS X Server 10.4.8 and Windows File sharing

    We are having lots of issues with our SMB share on Mac OS X Server 10.4.8. The main issues are the following:
    - Group ACLs seem to not work properly, and I have had to add dozens of manual permissions on a per-user basis
    - Often, users open a file in read-only mode, without any reason, and can't modify it
    - Often, users open a file with full write access, but then cannot save it and have to use a "save as function".
    After having looked all over the Internet and on the Apple's discussions forum, it seems like this issue has been around for quite some time now:
    http://discussions.apple.com/search.jspa?forumID=702&threadID=&q=smbANDpermissions&objID=f702&dateRange=thisyear&userID=&numResults=15&rankBy=10001
    http://discussions.apple.com/thread.jspa?messageID=1546867&#1546867
    http://discussions.apple.com/thread.jspa?messageID=647251
    And no real answer/solution has been provided by Apple yet.
    I also looked on Samba related pages, and it seems like these issues were Samba related (both ACL/OpenLDAP and Microsoft Office file handling issues), and the current version of Samba (3.0.23c) seem to have solved lots of issues in these areas:
    http://us1.samba.org/samba/history/samba-3.0.23c.html
    Apple ships Samba 3.0.10 (16 Dec 2004) with 10.4.8, which makes the shipping version at list 15 versions (and 18 months) behind the current Samba release (30 Aug 2006).
    People within the company are obviously quite unhappy with the situation and beyond me looking like a fool for migrating from Windows Server to OS X, I now need to find a solution to the issues.
    I would like to know what is the official and Apple recommended way to solve this issue.
    Kind regards,
    Pejvan
    It seems like Apple is totally ignoring the issues, users are facing with SMB shares, while their emphasize as a selling point how OS X Server is a great "windows file" server.

    Hiya
    Thanks for the reply.
    >Is there a UPS involved?
    I wish there had been. I might not be having to deal with it now! :-)
    >If you boot from the Install Disc & use System Profiler there, does the Same RAM situation? Did you physically >check those slots? Thinking maybe the OS is kicking them out on bootup?
    I've had the following suggested to me on another forum - "My guess on the RAM error is this. You have a processor that wants the RAM to be dual channeled and since it reads both A slot are populated it wants both B slots to be populated. Remove A2 and put it in B1"
    But unless it is degrading performance I'll probably just leave it.
    > Still can't get it to boot from the Clone holding the Option/alt key at bootup?
    I can get it to boot from the Clone using the option key but it's a pretty random event. I can try for ages and then suddenly it'll work. Or it may work first time. It does seems to work more easily after a PRAM zap. The funny thing is that once it is booted up it will re-start in any way I want it to (the boot volume, the clone, a disk, single user mode etc). It is just hard to boot from a full shutdown.
    I'm thinking that if I ca get the start-up issue fixed then I can fix the RAID issue at my leisure and even add the hard-drive that the clone is currently on to the RAID array.
    Thanks again.

  • Cannot access in a shared folder on Mac OsX Lion Server

    Hello, i've a strange issue with Mac Os X Server 10.7 :
    i created an shared folder, grant r/w permission to everyone group, but when i try to access to him from Pc with windows7 ask me te credential, however if i logon with a registered Mac OSx account it refuse the connection, obviously when connect to this shared folder from Mac i've no problem, of course...
    Someone can help me?
    Thanks Riccardo.

    Maybe someone in the Lion Server Forum would know the answer?
    Regards,
    Colin R.

  • [Mac OS 10.7]SMB sharing issue with IPv6

    Hi, Folks,
    I knew there are some big changes about SMB server and clients, the SMB sharing on IPv4 can work fine for me too. But the SMB sharing on IPv6 cannot work fine.
    After checking the TCP ports with IPv4, the port 139 is closed, and I only can telnet with port 445. For IPv6, both port 139 and 445 are all closed.
    Could you give more detail information about it? Or any solution to fix it?
    Thanks & Best Regards!
    Hao

    Read this:
    https://discussions.apple.com/thread/3823738?start=0&tstart=0
    It doesn't solve your problem, but does provide a work-around
    Diederick

  • OS 10.7, SMB Connection, Change to Unicode with Extended Security on Windows Server 2008 Standard

    Hi All,  I've searched Google, and I've also contacted Apple Support with no luck:  I want to implement unicode with extended security on Windows Server 2008 Standard server shared folders so that Lion can connect normally (i.e. Finder->Go->Connect to Server->IP Address or server name) to SMB shares and access files.  I'm lacking information; has anyone actually implemented unicode with extended security?  If so, how?
    Thanks in advance.
    Tom

    Thanks for the reply aorlich. Do you mean enable file sharing on my Mac? With file sharing enabled, I still cannot get to my Windows 7 shares, although the files on my Mac do become available to Windows. Thanks again.

  • Has anyone successfully set up scan to smb to mac os 10.7.x from a Konica Minolta bizhub

    Has anyone successfully set up scan to smb to mac os 10.7.x from a Konica Minolta bizhub. I'm using 10.7.3 on MacBook Pro. Don't care what model bizhub is being used as I have access to many. I've seen the posts for FTP workarounds but want to use SMB if that is an option. Any suggestions? Thank you!

    petermtnbk wrote:
    I've read other discussions that have suggested changing the format of the username and password when having login problems. I'm not familiar with NT-Status Codes. Could changing the format of the username make any difference? Something like... "workgroup/username" or "username@domain" or "domain/username" or some other combination of workgroup, domain, username, computername.
    The issue has nothing to do with the format of the user authentication. What you are reading is about the Lion Mac connecting to a Windows computer that is part of domain or workgroup. The method changed slightly compared to Snow Leopard.
    KM does support FTP so that is still an option, but I would ideally would like to set up SMB scanning. I'm not sure if KM is going to support AFP anytime soon.
    With the lack of SMB support and KM offering no alternative at this stage then I suggest you look at using FTP. While Lion removed the option to enable FTP via the Sharing pane in System Preferences, it can still be enabled via Terminal using the following command
    sudo -s launchctl load -w /System/Library/LaunchDaemons/ftp.plist
    You will be prompted to authenticate using your Mac's admin account & password. Once this is done, you can then configure the address on the copier to push scan using FTP. The keys are;
    The host name requires just the IP address. No leading slashes like SMB
    The path will be the folder that you want to scan to, also entered without a leading slash. For example, Desktop
    The user name will be the short name of the account who's folder you want to scan to.
    The only other option may be WebDAV if the KM supports it. We have this with our imageRUNNER ADVANCE and with a document scanned to a shared folder in the copier hard drive, we can then connect to that folder by using Finder's > Go > Connect to Server facility. You then just enter
    http://ipaddress/share
    which connects you to the shared folder and lets you see the document you scanned. You also have the facility to set subfolders for security of users documents.

  • Windows PC (XP) and Mac OS X Server 10.6 print service

    Can someone tell me if it is possible for a Windows PC running XP to make use of the Mac OS X Server 10.6 print service? Following the manual does not help. After enabling SMB I don't manage to connect to one of the shared printers. How could I make use of IPP and LPR support being built into Windows XP?

    I know the problems with Time Machine on Mac OS server. In your case: Look at the log files, searching for "backupd", if that tells you anything.
    In my case, Time Machine in the last year stopped several times. Occasionally, there was a helpful message in the log files where I could identify a file where it had hung -- typically intermediate build results of Xcode. After excluding or deleting the offending files (where possible), Time Machine ran successfully.
    Another situation which has repeatedly occurred is that time machine just hangs and does not progress, and no log entry helps. In 3 such cases what helped was to delete the spotlight index (e.g., with TinkerTool System) and let it rebuild. It took inordinately long (10 hrs) and there were log entries by mdworker that it had difficulty processing files. But when the spotlight index was finally rebuilt, Time Machine worked again.
    BTW: I don't need Time Machine to backup the server system, for that I run mirrors etc., but for user files it is most convenient and has helped several times. Thus I have excluded nearly everything but /User/*.

  • SMB Sharing User?

    Hello,
    Since a good long while i've been working with a Macbook. Being a long term windows user i gradually took the opportunity to study on more OS's than just Windows. However, one of the few things i still havn't figured out is the SMB Sharing capability.
    Let me sketch you an environment.
    Leopard 10.5.5 (And somewhat below) Allows you to share folders, much like windows with policies on what a user can do in a folder et cetera.
    When sharing a folder with Leopard, you go to File Sharing, toggle SMB on, and define an account you want people to use to get into the shared folder. Here, exactly lies my problem. With a guest account i am perfectly able to see the folder on a Windows computer.
    Once i define a user account, let's take "Test" as a subtle one for now. The password would be easily set to "test" aswell. In the User Management interface i've defined a sharing account under the name Test.
    This account will now show up at the File Sharing preference pane. I can select it, and attach permissions to it, such as "Test" may write in folder "X" but, "Everyone (also known as Guest, i suppose?)" May not see anything at all.
    Once i did this, i am unable to at all get connection to the shared folder through Windows, but when i toggle "Everyone" to Read or Read/Write, i can see the folders perfectly clear once again.
    My question is, How so i solve this problem. So that only an account "I" Define, may have access to the shared folder with the credentials "I" once again define?
    Thanks in advance, and i hope to see your responses soon.
    Rene

    Can't solve your problem as we are in the middle of setting up a mac mini snow leopard server with a couple of macs (absolutely fine!) and a couple of PC's both running XP. One will connect but one won't. How do you connect/have your's set up to connect. The problem PC will see the share point in workgroups and allow to enter username and password, but won't mount the volume. so annoying!

Maybe you are looking for