10.5 SMB PDC Problems

Hi,
I'm having issues starting up SMB as a Primary Domain Controller. My machine is a Open Directory Master. Every time I start up the service as a PDC it changes my role back to Stand Alone Server. I've read through the documentation and it doesn't seem to list any other requirements other than being an OD master. Is there something I'm missing?
Thanks.
-Matt
Here's my current settings through the cli utility (after my PDC configuration is 'reset'):
bash-3.2# serveradmin settings smb
smb:realm = "DC01.INSIDE.AMI.NC"
smb:enable disk services = "yes"
smb:lanman auth = "no"
smb:workgroup = "WORKGROUP"
smb:wins support = no
smb:domain master = yes
smb:map to guest = "Never"
smb:enable print services = "yes"
smb:wins server = emptyarray
smb:use spnego = yes
smb:use kerberos keytab = yes
smb:security = "USER"
smb:server string = "dc01.inside.ami.nc"
smb:auth methods = "odsam"
smb:ntlm auth = "no"
smb:netbios name = "dc01"
smb:max smbd processes = 100
smb:adminCommands:homes = yes
smb:adminCommands:serverRole = "standalone"
smb:adminCommands:ldapRole = "1.1 - hosting a master LDAP directory server\n"
smb:dos charset = "437"
smb:log level = 2
smb:preferred master = yes
smb:os level = 65

Hi
If your server is in an Open Directory Master role then selecting Primary Domain Controller in the SMB Service will present you with a prompt to supply an administrator name and password. This name and password will be the one created when you promoted from Standalone to Open Directory Master: Directory Administrator (UID 1000) diradmin.
If you put in any other name and password it won't work and will keep demoting itself back to Standalone.
If it still does not work after that, demote your OD Master back to Standalone, sort out your DNS and try again. Firstly with Open Directory and then with SMB.
Tony

Similar Messages

Windows 8.1 Pro SMB Sharing problem

Hi,
Would love some help.
I have a file server that I recently upgraded from Windows 8 to Windows 8.1. Problem is, it broke my smb share to 2 Dune Media players and another PC running XBMC on the Openelec platform. I have spent days scouring forums for information and tried
every reg hack and security/sharing fix I found but to no avail. I have since refreshed windows 8.1. I did however just have a breakthrough.
The problem is that the 3 devices above all worked great before the update, now I'm getting errors when ever I try to access a file on the smb share. On my Windows 8.1 file server I have am running storage spaces with about 8 discs amounting to about
16TB of storage, plus an SSD with the operating system. What I just discovered is that if I share a folder on the C drive, it can be scanned and accessed from any of the media players. Therefore it's only the 'storage space' drive that won't authenticate
an smb client.
Thanks
Allan Phillips

Thanks Alex, I had tried that a few times. Finally after 3 weeks I found the solution on the WD forum. Solution is as below.
Re: WD TV Live does not see shared windows USB drives that are connected via hub
Options
‎01-24-2014 12:46 PM
Well, nobody offered any opinion so far, but I was able to solve the mystery.
It is all about the old IPRStackSize of the LanmanServer (Windows NT is greeting us again).
I was taken off, because access seemed basically to work (at least with Windows machines).
But the Windows 8.1 event log then told me very clearly : event 2011, irpstacksize not large enough, please increase.
This event occurred whenever I tried to access the shared drives from my Android devices or especially from the WD TV Live. The only difference netween these 2 systems was that on the Android devices I could at
least see the drives (but could not really open them), while the WD TV Live did not even boither to show me the drives.
Now, I have no clue about the actual limits for the IRPStackSize in Windows 8.1 (the values changed from Windows version to Windows version). So I finally used the limit I found for older Windows systems :
32 (x20).
And it works now like a chram as it seems.
By the way - I found stories about older Windows systems, where people increased the value to 20 (x14). So I tried that value first. With the result that I could not access any drive from other network units at
all. So, the default value for this in Windows 8.1 must be even higher than that. I don;t know what it is, but 32 (x20) is obviously higher.
Long story short : it is a Windows 8.1 (possibly already Windows 8) problem. And it can be solved by creating manually an entry in the Registry to add the IRPStackSize parameter with the higher value (as you know,
when this parameter is missing, Windows uses a default value, which is obviously too small for drives connected to a hub and accessed by any kind of Linux systems.
I still don't have a clue, why the access request by a Linux based system requires obviously more stack size than a request by a Windows machine. That is still something that makes me shake my head.
Here a little procedure copied from Windows NT solutions :
1. Run regedit.
2. Navigate to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. In the right pane, double-click the IRPStackSize value.
4. In the Value Data box, type a value that is larger than the value that is listed.
If you created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and
then click OK.
5. Close the Registry Editor and restart the computer.
If the problem persists after you complete the preceding procedure, try to increase the value of IRPStackSize even more. The maximum value for Windows 2000 is 50 (0x32 hex).
NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:
a.
In the Parameters folder of the registry, right-click the right pane.
b.
Point to New, and then click DWord Value.
c.
Type IRPStackSize.
IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive.

OS X 10.5.8 Leopard Server & SMB authentication problems

Hi all,
I am in charge of a OSX Leopard server. The platform has Windows XP /Windows Vista / OSX computers and as the server has a high capacity NAS it seemed logical to share it using SMB.
The initial set up was done having in mind just the MACs, and they have no issues connecting to the SMB shares. The problem is on Windows side.
Windows machines are supposed to use the SMB shares with Open Directory Accounts. But whenever we create an SMB share, there is a strange behaviour: files could be uploaded to the server, but once copied, they can't be copied back to windows machines, triggering the error (more or less, as the error text is in spanish): "File operation could not be completed, source file could not be found"
For debugging purposes, we have just created a share, step by step , identify which the problem is:
1 - Create a user from Workgroup manager, no admin capabilities.
2 - Create a folder under "Shared Items" Folder.
3 - Disable "Enable Spotlight Search"
4 - Disable AFP, FTP, NFS (leaving just SMB as sharing protocol)
5 - SMB protocol options: Disable "Allow guest access", Asign permmissions as follows: Owner: RW, Group R, Everyone R.
6 - We then go to permissions and choose user created at step 1, set him ACL permissions as RW.
7 - Save changes.
After that, we reboot our Windows test machine, flushing its dns cache previously.
Then when trying to connect to the share,an error message on our XP box says that we have no permissions to connect to the sahre (using our test user credentials). SMB log displays the following:
+setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.+
+[2009/10/23 12:05:20, 2, pid=29029] /SourceCache/samba/samba-187.9/samba/source/auth/auth.c:checkntlmpassword(319)+
+checkntlmpassword: Authentication for user [] -> [] FAILED with error NTSTATUS_NO_SUCHUSER+
Thanks in advance and best regards.
Message was edited by: javierspn

Edit:
I can now connect with the new user. Something to do with DNS cache and opened sessions on the SMB server that I manually closed.
However, same problem: I can upload files but whenever I try to copy one from the server to any XP workstation:
http://yfrog.com/3oerrorjkj
Basically meaning in plain English that the source file could not be found.
Regards.

Smb protocol problem after upgrading to IOS 8

Hi,
I use SMB protocol to connect to Windows share folders in our company.
Using IOS 7 on the iPad was working great until i upgrade one iPad to IOS 8.
I can't connect using SMB protocol on the iPad with IOS 8. With an iPad with IOS 7 still works great.
The settings are the same. I tested Goodreader v3 and v4 and FileExplorer program on the iPad with IOS 8 and on the iPad with IOS 7.
The problem is only on the iPad with IOS 8. It does not matter which program I use. All are not working.
On the iPad with IOS 7 all the programs works just fine.
It seems that after upgrading to IOS 8, I have problem connecting to the share folders in Goodreader v3, v4 and in FileExplorer.
It seems the problem is not on the settings of the server, account etc, also not program related but with the IOS 8.
Does someone have this problem or now how to fix this?

Hi all,
I have run some more test and the problem is not with the SMB protocol but to connect to a DFS server.
One share name like company.local and behind this we have some servers.
The problem is with the DFS name (routing) When I connect directly to one server share location, it works fine.

SMB Share Problem

I have Windows Server 2003 with a couple SMB shares setup. My problem is that on my schools network I am able to connect no problem to the server when in my Dorm building. However when I go to a different building finder says "The server may not exist...Check the server name or ip address..." I am trying to connect using the Servers IP Address, I have also tried using DNS name and that doesnt work either. The catch is that when I am running Vista through Boot Camp I am able to connect no problem to the SMB Shares using the IP address, so Im curious as to whats different within the two OS's that one can connect and the other cannot.
All connections are Wired, the server is not behind a router within my room.
In finders connect to server i am enter smb://<ip address>

Your issue may be adressed by one of these threads:
http://www.macwindows.com/tiger.html
Good luck!

SMB ACL Problem

We have this problem that came up sense we upgraded our servers to Leopard. When Windows users are accessing files (over SMB), the POSIX permissions seem to override the ACLs. This is a problem because applications like Excel will change the permissions.
This worked perfectly in Tiger. The windows user would modify the POSIX permissions all they want, but it wouldn't matter because the ACLs were what mattered.
Does anyone know of a solution. This is a real problem.

OK, here's a tip that may get the situation going for you all. This involves making an adjustment to your server's Samba configuration file, which should be done with the Windows SMB services stopped.
In /etc/smb.conf, add the following line under [global]:
*acl check permissions = no*
This mailing list archive notes the same problem: http://lists.apple.com/archives/macos-x-server/2008/Jan/msg00759.html, and it offered the above solution.
Here's a little more about why this alteration is required: Windows clients work a little differently when determining if a file or folder (an item) can be deleted or not. With simple POSIX permissions, you're allowed to delete an item as long as you have write access to the item's parent folder and as long as the POSIX special permission sticky (owner only delete) bit is not set. With ACLs, deletion can be granted explicitly on the item via the use of delete or it can be granted via implication so long as the item's parent has delete_child. In short, to deny deletion of an item, you must deny delete on the item itself and delete_child on its parent. Now it's starting to get a bit more complicated to determine if some item can or cannot be deleted.
Apparently Windows clients perform a "pre-scan" of a folder's contents ahead of time to determine if an item can or cannot be deleted. The logic behind this "pre-scan" works like this: 1. Assume that the item cannot be deleted. 2. If the pre-scan evaluates effective permissions correctly, and those permissions allow delete, flag the item as being delete-able.
Now when you go to delete the item, Windows just checks the result of its pre-scan. With Leopard, Windows boxes are having trouble evaluating effective permissions from the Darwin ACL model. (I don't know why.) Thus, the pre-scan returns "deletion denied" because that's the default assumption. Windows didn't even try to delete the file; rather, it simply doesn't think this is possible.
The use of *acl check permissions = no* disables this Windows "pre-scanning" behavior. Unfortunately, this can mean that an item that really cannot be deleted appears to be delete-able. In this case the item will "magically reappear" the next time the folder's contents are refreshed in Windows.
Hope this helps! This is my present understanding of the need.
--Gerrit
Message was edited by: Gerrit DeWitt

SMB PDC setup-authentication

Hello, in a testing environment with a non-networked server (eth0 is on and all other settings and management are working correctly e.g. workgroup manager and server admin) I am interested in practicing setting OS X as a PDC. However, each time I try and establish this setting (SMB), I enter my domain and then attempt to authenticate as my DirAdmin only to receive a could not authenticate message and my settings reverted to previous.
I think I might just be confused on the domain entry - I don't have enough room in the input box for server17.pretendco.com and pretendco.com doesn't work (what I've been using for everything else). Apple Knowledge Base says: "Domain: Enter the name of the Windows domain that the server will host. The domain name cannot exceed 15 characters and cannot be “workgroup.”"
Any direction or sources please?
I've been following the Apple Training Series Server Essentials 10.6 book up to this point, but this configuration is skipped over in the exercises... kind of important to know I feel.

Just type PRETENDCO it doesn't want any .coms etc
I believe it must be in CAPS as well although i don't use this facility it is what i seem to recall it should be.
Windows 7 is not supported i believe and Vista may need some tweeking in the security policy.
Also login as diradmin before you try to modify anything as this will prove it is not an account issue with the diradmin login.
When you say non-networked server is a switch or router at least plugged in to your (eth0) as i have found that an OSX server with no network connection of any kind is not a friendly beast.

Samba As Windows PDC problem + AD

Hello All,
In an effort to minimize the amount of different logins my users have, I am trying to create a windows domain with Samba as a PDC in OSX Server 10.6.6. Before attempting to "create" this domain Samba was running on the server as a "Standalone" server with default settings. When the role of the SMB server is changed to "Primary Domain Controller" a Fatal Error shows up in the logs saying it cannot find its workgroup. Here is a sample:
# [2011/04/13 19:22:06, 0, pid=148] /SourceCache/samba/samba-235.5/samba/source/nmbd/nmbdserverlistdb.c:write_browselist(350)
writebrowselist: Fatal error - cannot find my workgroup "#####"
I have gone thru and tried to reset all settings for samba, shutting it down and restarting, deactivating the service. I have also scoured the internet to find a solution. Reading thru the manual for Samba PDC in apples documentation make this process seem as if it were as easy as pie. I am stumped.
My ultimate goal is to create this domain and have a Windows 2008 SBS authenticate to it. The SBS will be acting as a terminal services machine.
In everything I have read, the "Normal" or accepted setup is to have OD authenticate to AD, not the other way around. Since our system is entirely Mac(except the accounting server) and our OD is active and running, I would prefer not to change to AD.
Can anyone shed some light on what might be wrong? Any help is greatly appreciated.
Sincerely,
-Netti

Did I post this in the wrong place. Please, any advice is appreciated.

SMB Permission Problems

I have upgraded our G5 "server" to OSX Server 10.4.8 recently. For the past two years it has ran SMB on plain old OSX (Panther) flawlessly. Now that we have a true "server," we are experiencing difficulty in making it work.
I have configured all users and assigned them to a group called "employees." I have created a share under the /users folder, granted the group "employees" with read and write access, turned off AFP, turned on SMB, and checked "inherit permissions from parent." Oplocks, strict locking, and SMB guest access are all turned off.
When a client modifies a file, that file may or may not end up with read only access. Not good.
By reading other posts, it appears that others have been pointed toward ACL's, but it also appears to me that they don't really apply to a Samba only environment (choices are greyed out).
Any suggestions?
Thanks in advance....
Jack

Good news! I've solved my problem. I'm going to make another post for the purpose of giving a plain answer to others that I wish I had when I encountered my issue.

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.

Export using QuickTime Conversion + SMB automount problems

I have noticed an interesting (read bad) behavior in FCP (5.0.4) - If I try to do an export using quicktime conversion with the destination being an automounted (via netinfo) smb share as opposed to a apple-k mounted share in m4v, 3g, mp4, image sequence, still image or quicktime movie - I get a File Error: Unknown Folder. However if I do the same export but in avi, wmv, dv stream, or flc formats, it works fine.
Trying to do the same export operation in quicktime pro produces an error -120, which is equivalent to directory not found.
Seems like a quicktime problem dealing with the automounted shares, anyone else run into this issue? Have a fix?
Thanks!
C M I

I know I can save locally + that it is tied to the quicktime components - I'm looking for fix/workaround that addresses the issue and streamlines my workflow, thats the reason I set up the automounter in the first place.
So it's clear though, quicktime has no problem with smb in a general sense, it only has problems w/ the automounted smb shares - manual or command+k mounting of smb shares offer no problems.
I use the automounting for two reasons: first is to emulate unc paths for rush render queue and second is to have consistent working paths to static content on a file server so final cut docs can be passed from editor to editor and link consistently.

Connecting to SMB / PDC home share is read-only

I have an absolute mystery (to me at least). I have a Linux SMB server with home shares enabled. I connect to the home shares no problem from Windows. On my Mac (OS 10.6.3), one user is able to connect to their home share, but I cannot with my account. Investigating further using terminal, I noticed that the SMB mount (in /Volumes/%Username) is mounting with mode 555 (r xr xr x) instead of mode 755. I verified that there are no ACL's on these directories. The user that is working has their home directory with 755 as I would expect. Note - Mac OS GUI is doing the mounting automatically using the standard "connect to server" from Finder and just using smb://servername/username. It is bizarre, as I there is no difference that I can find between the two users on the SMB share and it works fine from Windows. I tried chmod'ing the smb mount to 755, but it just reverts to 555 on remount. I've done an "smbstatus" from the SMB server and it shows that my username is connected and shows no difference between the windows and mac, so all the permissions on the SMB server seem to be correct (I am connected to the home share with the correct username and not as "guest"). I'm at the limit of my expertise with this one.

Actually you do not have read/write access. Your Home folder is owned by the system user and the group is wheel. The correct values for a Home folder are:
Owner=you with r/w privileges
Group=staff with r/w or read-only privileges
Everyone=read-only privileges
Try this:
you can reset the ACLs on your home folder by the following series of terminal commands. It's up to you if you want to do that. I personally like them but I hate the way the ACLs are implemented in leopard so that many ACLs are invisible from GUI and yet can be propagated by using "apply to enclosed items" button. That's a major No-No in my book.
Here are the commands (in bold). just copy and paste the commands (they are in bold).
*chmod -R -N ~*
this removes all ACLs from files in the home directory.
The following two commands put the necessary ACLs back where they belong.
*chmod +a "everyone deny delete" ~/ ~/Desktop ~/Documents ~/Downloads ~/Library ~/Movies ~/Music ~/Pictures ~/Public ~/Sites*
*chmod +a "`id -un` allow list,addfile,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit" ~/Public/Drop\ Box*
The above was provided by user V.K. in this forum discussion.

SMB speed problems and NAS devices

I posted this under the Online networking section, but it drew no responses (no one actually read it). So clearly NAS and SMB is not much of an issue there. I apologies for the double posting but I hope to get some clarity here.
I appreciate that this has been raised a few times before, but searching the forum has not yielded a satisfactory answer and perhaps some solutions were lost in the the forum upgrade. So apologies in advance. My issues/concerns are as follows:
1. I have my PB 15 connected through SMB to an XP desktop (XP Home). I can access the shared drive/folder and the PC can access the PB. However, the SMB transfer is dreadfully slow. I have made some changes to the sysctl.conf file by entering the string 'large readwrite = no' and 'net.inet.tcp.delayed_ack=0' but this has yielded no tangible improvement in file transfer speed. I used the following website http://www.macosxhints.com/article.php?story=20051107090652912 for help. It seems that after 4 updates to Tiger and 9 updates to Panther, Apple has been unable to improve the transfer speed or at least that is my impression.
2. I now wish to install a NAS device. I run a Netgear DG834G wireless router with connection to Win2K, WinXP, OS X 10.4.4, Airport Express, Canon wireles iP4000R. The idea is of course to use the NAS device to store my music and photos and provide a central storage for documents/scans. In theory all seems fine, but I am dreading the slow transfer speeds. I notice that the NAS devices are either Linux based or Windows Server 2003 based (Lacie Ethernet disk). Now I also read that these devices have difficulty with filenames >31 characters. I would, therefore, very much appreciate some help as, although I can do some basic networking, I am quite poor on Unix and more sophisticated network commands.
I also have one other query which baffles me. I can read and write to my XP computer through SMB even though it is formatted in NTFS. However, if the NAS device is formatted in NTFS, the Mac cannot write to it. Why should this be the case? I always thought an NAS device is just a basic computer with some hard drives and if it is running the Windows kernel, and using SMB, why should it have a problem. Of course, the reverse is also true (i.e. formatting in HFS+).
I'm sure these appear quite basic questions, but I am unable to get answers by just 'Googling' and asking the Apple Store Geniuses these questions just draws blank responses (that is after all the effort to get to the store and make appointments etc.).
This is a long post, but I believe that for any NAS device to become truly useful on the Mac, Apple needs to fix the SMB speed. Backups will be inordinately slow and cumbersome and also sharing and moving large files will limit its usefulness. This issue is not of concern to most Windows users, as they are well catered for.
Regards
Nazir

I also have one other query which baffles me. I can
read and write to my XP computer through SMB even
though it is formatted in NTFS. However, if the NAS
device is formatted in NTFS, the Mac cannot write to
it. Why should this be the case?
Remember when writing from a Mac to a shared drive on an XP PC, the XP is doing the actual reading and the writing and not the Mac which is merely asking the XP PC to do so on its behalf.
iFelix

SMB Permissions problems...

We use Mac OS X 10.8.5 server and have set SMB share. After anybody from Mac or PC copy files or make folder on the share, the server add permissions only to this user and no one others can see, copy or use the files (only admin). We have try to have users free and in group but no change. Only the user who make the folder or copy the files can use it.
Please can anybody help to resolve this problem
Thanks.

https://discussions.apple.com/message/9212534#9212534

Smb resolution problem on one of two MBPs, same network

I have a MBP 2,2, 10.6.5 and a MBP 8,2, 10.6.7. Each connects to the local network via WiFi 802.11n. The router is a Netgear WNDR3700.
On the new MBP, I have connection problems when browsing to SMB shares in the Finder that are not named explicitly in /etc/hosts. All the shares I expect show up in the Finder. However, connections fail:
6/29/11 29 103715 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[210] SharePointBrowser::handleOpenCallBack returned 65
On the old MBP there is no problem.
What's been tried so far: make /etc/smb.conf identical on the two machines; twiddle name resolve order when that didn't work; examine /var/db/smb.conf (which on the new machine includes three Kerberos lines that do not appear in the old machine's /var/db/smb.conf, I've commented these out even though the file header says DO NOT EDIT); throwing away /Library/Caches and ~Library/Caches; adding hosts' names explicitly to /etc/hosts. Firewall settings on the two machines are identical.
Connections always work to shares named explicitly in /etc/hosts. They always work between the two MBPs. The new MBP can basically connect to nothing that isn't named in /etc/hosts on any reboot except the one immediately following deletion of the caches. If the machine is connecting properly and then allowed to sleep, on waking it can no longer connect to the shares.
What should I look for to figure out this behavior? The MBP 2,2 has been exemplary and it seems reasonable that the 8,2 can do the same things.
Thanks.

Yoo Chung,
Went into preferences and deleted all cookies. Then with Safari downloaded and installed 'Firefox Browser' and ran to see if we could break into Yahoo mail. Unfortunately, that didn't help. One thing that I didn't take into account was that I had reset the 'Parental Controls' after installing and updating Leopard.
I decided to uncheck the Parental Controls, log into Yahoo from 'Firefox', and got to the mail account page without any difficulty. We backed out, tried the same on Safari and everything worked just fine. I let her get into her email account and clean up the multitude of junk that collected since installing Leopard. Then reset the Parental Controls and then went back to the Yahoo mail account without any glitches.
Apparently, something triggered a fault and would let her go beyond the Yahoo opening page to mail. Everything is running great now, and we've an additional browser just in case.
Thanks for you help.

10.5 SMB PDC Problems

Similar Messages

Maybe you are looking for