New answers tagged server-message-block
For me, it was a matter of looking at what was IN my keychain… and matching that up with my auto_smb map... /../Volumes/ServiceData -fstype=smbfs,soft ://home._smb._tcp.local/ServiceData
My mistake, I had previously disabled "client for Microsoft Networks". After re-enabling this it's working fine.
you can do it very simple with de following command: icacls "\\path" /grant DOMAIN\User:(OI)(CI)M me M of Modify gives you permission in all the path you selected but without the permission "take ownership" or "set permissions" hope this helps!
Since posting we've narrowed it down to the ShoreTel 655 phone the workstation is plugged into. Why it would affect only SMB traffic we don't know yet, but if we bypass the phone entirely everything returns to normal, so despite the signs pointing to software (only the one protocol is affected, other performance tests are normal), I think we might end up ...
You can achieve this via AD Users and Computers GUI and via Powershell. What I did in the past is open AD U & C GUI, right click on the new AD user, go to Profile and type in the information below. What I did in the GUI is select "Connect" under Home Folder, choose my preferred drive letter (in this example, G:) and assign the following user share \ ...
I don't know if it is still relevant, but I too had the same issue as you described and I solved it by editing the /etc/sysctl.conf file on the mac clients. I have found these settings to work in my situation, but perhaps they might need some tweaking in your situation. net.inet.tcp.win_scale_factor=8 net.inet.tcp.autorcvbufmax=16777216 ...
Top 50 recent answers are included