SMB Issues in 10.6.8

We have an internal website that when you click a link it launches the "Connect to Server" box and mounts the smb:// share point to display the contents. The behavior of this is different between 10.6.8 and 10.8.3. Example:
10.8.3 -
1) Click link on site - smb://Example/Folder/Picture.jpg
2) Connect to Server box opens
3) Finder mounts the share smb://Example/Folder and displays the content contained in Folder
NOW, in 10.6.8
1) Click link on site - smb://Example/Folder/Picture.jpg
2) Connect to Server box opens
3) Finder tries to mount the entire path smb://Example/Folder/Picture.jpg and instead of showing the contents of Folder, it thinks it has mounted /Picture.jpg as a sharepoint. The finder window is blank with no files visible.
What config can we change on 10.6 that will produce the expected behavior of the 10.8.x machine?
Hope this makes sense. We are trying to make this compatible on all of our machines running 10.6.x to 10.8.x but the expected behavior only seems to be apparent in 10.8.x.
Thank you.

I don't see a question or request for help anywhere in there.
If you just wanted to vent, OK, that's done.
If you wanted to report your problem to Apple and "demand" that they address it, then this is the wrong place; this is a user forum. Try here:
https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn

Similar Messages

SMB issue in 10.9.2 Server

Hey everyone,
Hopefully I can get some help or at least someone else can recognize the issue at hand. We recently upgrade our Mac Mini Server to 10.9.2 and are having major SMB issues. It's hard to specifically tell but it seems like when we hit a magic number around 150~200 users the server shuts down all filesharing. When I look at Activity Monitor, SMBD is around 99% CPU usage. The only remedy is to restart the server.
Any help would be greatly appriciated. Thank you!

There have been some other posts suggesting that Apple might have messed up some default TCP configuration parameters in 10.5.2. It might be instructive to compare the result of:
sysctl -a | grep tcp
on otherwise similar 10.5.1 and 10.5.2 systems.

Upgraded from Snow Leopard to Lion, SMB issues - incorrect password

This is a very frustrating issue, and its affecting my work now.
Basically I used to use the SMB sharing quite a lot in work, it was an ideal way for our clients to get to data off my MBP and worked like a dream in OSX 10.6
I was an early adopter, and upgraded to Lion on release date. Problem is now, I have SMB sharing switched on, but no user accounts enabled. When I tick to enable one I get "Incorrect password" (see picture)
I tried disabling SMB and it again prompted me for my password, and to no avail, I got "incorrect password" again.
I updated to 10.7.1, and STILL unresolved. I am very disappointed that this, as well as the Guest account being disabled if you have FileVault enabled (which is a requirement of my employer due to the sensitive nature of the data we handle). I experience persistent Kernel panics triggered by my MBP switching from the Intel HD graphics to the Nvidia chipset, I am extremely frustrated and disappointed overall.

I mistakedly posted this to another topic. It's something that worked for me, I hope it to be of help to others as well.
Try the following:
1. Create a Sharing Only account through "Users & Groups" preference pane, assign a password to the account. Suppose we you create an account named "mike".
2. In Network select your interface, go to Advanced and then WINS. Under Workgroup set the default WORKGROUP and under NetBIOS Name set whatever suits you (let's assume you put "imac").
3. Now go to Sharing select a folder to share and add the "mike" user account you just created for sharing-only purpose, go to Options tick the checkbox for SMB and then for the "mike" account and enter its password when asked for it.
4. When accessing the shares from Windows box enter username in format "imac\mike" and the password for the account.
This should set you up for accessing your Mac shares from your Windows machine.
There still is a problem with adding ad hoc sharing account from the Sharing preference pane, a bug hopefullly resolved in some of the upcoming updates.

SMB issues on 10.10.1 server 4

I am running file sharing on 10.10.1 with server version 4.
AFP continuously works but SMB will seem to stop functioning every few weeks. This will result in "There was a problem connecting to the server ...." when a user attempts to connect.
I've used serveradmin to restart the SMB service, but users are still unable to connect.
Restarting the server corrects the issue for a couple of weeks.
I'm curious if anyone has ran into similar issues and if they've come across a solution.
Thanks.

You might try the OS X Server forum.

10.8.1 Server and windows smb issues

Ever since upgrading to 10.8.1 server my windows clients now have issues copying to the share point on the server. "Network error, there is a problem accessing \\SERVER\WORK"
It's only with large file transfers 3GB and above. It also randomly shows the same warning when they are saving projects to the server occasionally and they have to manully reconnect.
Latest windows 7 64bit pro on all clients and latest mac os X on server.
The share point is an attached thunderbolt raid and has all permissions switched off, and is configured to RAID 0. This is backed up hourly by another drive.
Is there anyway of rolling back to lion? I no longer have a lion back up on my time machine.
Anyone else having these issues?

Apple's SMB implentation is weak and buggy. I feel like I'm back in 10.3 trying to talk to Windows servers. Those were horrible days.
To Fix.. go to your Mac and check to make sure that it has the correct WINS settings (network, advanced, WINS). Your server has to be on the same workgroup (domain) as your windows clients. For some reason, the setting does not stick on your Mac and that setting gets lost. And that is the bug...
To fix this (second part of your fix).. go ahead and turn off file sharing. Then add your settings under WINS as stated above, then turn sharing back on and your networking from windows to mac will start to work fine.
Fun bugs... please call Apple about this, so they can follow up. My case number is 357016704

Mac pro xserve 10.6.8 AD and SMB issue

Hi,
I have configured Mac OS XServe 10.6.8. This Server is joined with Windows 2008 AD Server.
I have done coming below:
1. Server Admin.app
2. File Sharing -> careated new share folder "test". This folder is located this path "/Volumes/Macintos HD/test"
3. Under Permisstion tab i have clicked + button, then i got new tab "Users & Groups". Their i can see all my windows AD users.
4. I have selacted my user name and two more users full access.
5. Then i have enabled AFP and SMB protocols.
6. Then i have saved the configrstion.
7. Then i went my mac book pro laptop i tryied connect to server afp://192.168.1.5/test
8. I can access the share Folder.
9. Then i have tried smb://192.168.1.5/test
10. User Name and Password not autendicating.
can some please help me how to resolve this issue.
Thanks

Before upgrading to Lion, I would recommend playing with OpLocks on the SMB share. Oplocks will not allow access to a folder if it is use by another share. Try turning these off and on and making sure that nobody is connected to the share by either protocol.
Worth a shot.

Older Clients cannot Authenticated to 10.10 Server ( Also SMB issues)

Hello
I am having a few issues with Server.app ( running on 10.10.2)
It appears older clients ( tested but 10.6 and 10.7) cannot log into the servers open directory. They can bind to it but cannot log in. If i log in with a local account they can still access file sharing etc.
10.10 clients are fine no issues whatsoever with logging in. ( i have not had a chance to test 10.9 and i don't have any 10.8 clients )
I am guessing its something to do with the way older OSs authenticate with the OD but i am not sure, don't have a huge amount of experience with OD outside of general admin.
My second issue is with SMB.
I am using SMB for file shares, everything was working well and then i started to have issues where users get a message saying the fire cannot be read or written error 36.
The file however would copy over no issue at all.
if i connect via cifs:// rather than smb:// it works ( this uses the older version of SMB ) but in an ideal world i would prefer if i did not have to use this as i would have to run a script on every client to force it to use cifs://
AFP works fine however i cannot use AFP for 2 reasons.
MS office for mac does not agree with it , accessing files over afp with this application causes files to be corrupted and become locked for editing. Apparently you need to have a globally writable folder called .TemporyItems in the root of the share for MS office to work correctly ( good design there microsoft) but this does not appear to work.
AFP does also not appear to make file inherit the permissions when you copy something into the directory so its no good for a shared folder .
Is there any way to force yosemite server to use SMB1 so i don't have to edit every single clients settings?
I would also be happy to use AFP if the 2 issues above can be solved.
This is so strange our old 10.6 server works just fine with MS office over AFP.

my 10.6 clients log in to new accounts with home folders on a new Yosemite server but take about 4 minutes...

SMB issue 10.4 client and 10.5 server solved?

I searched for days to solve the problem to connect via SMB from a 10.4 client on shared files on 10.5 server. But I did not find any answer except unable guest access (what is no real solution).
Why this error code -36 appears when trying to connect from the client (because encrypted password IS enabled)?
Why SMB still works using 10.5 clients and Windows PC's?
Why SMB works when guest access is unabled, but connected with defined accounts?
Does anybody can answer this questions?
Best regards,
Tom
Settings:
10.5.3 Server version
virtual LAN environment
mixed network (Mac, Windows)

I had a similar issue and I was able to make things a bit better by letting all users have access to SMB under the server access settings. You can still limit who has access to each individual share. I still have some other odd issues but I can at least connect.

Windows 2008 and Tiger SMB Issues

I've been pulling hair out all morning over this one.
We have a new Windows 2008 server for file sharing. We are trying to connect to it via SMB on our network (with AD domain). Works great on PC, works on Leopard, does not work on Tiger.
From connect I type “smb://xxxxxxxx” after a few minutes I get an error: “could not connect to the server because the name or password is not correct” which is odd because I haven’t entered any login credentials to begin with.
I’ve been pouring over Google, Microsoft KB and anything else I can come across with no luck. Things I’ve tried.
-Clearing keychain passwords for the server
-Setting the digital signing on the server to disable (most cited fix, but no go for me)
-Setting Sharing and Security model to “Classic – local users authenticate themselves”
-Setting LAN Manager authentication to “Send LM & NTLM – use NTLMv2 session security if negotiated”
-Editing the smb.conf file on the mac to no security
-Created the nsmb.conf file on the mac with minauth=none.
-Used Directory access on the mac to add the mac and bind it to the domain.
-Many Many restarts of the server and clients (and running gpupdate.exe on the server)
One thing that DOES work is a trial of ADmitmac… but this is not realistic for us if we have guest users needing to access the share.
I’ve been able to use smb before with tiger and windows xp and windows 2003… but the mac is throwing a fit over the new windows 2008. Also, we can’t upgrade all of our machines to Leopard (which does work) because it will break Quark 6.5.

Any relevant looking log messages if you browse in Console?
- cfr

Command Line SMB Issues

Greetings,
I scripted in 10.7 the mounting of a Windows share (SMB) for some back end tasks. My script needs to dump collected data over to a Windows share for further processing.
My code seems to have broken since my upgrade to 10.8.
Here is the line of code:
I first create the directory: /Volumes/SHARE
then:
/sbin/mount -o nobrowse -t smbfs //SERVICEACCT:[email protected]/SHAREhttp://winserver.sinc.stonybrook.edu/SHARE /Volumes/SHARE
That worked. But now, I get an authentication error. The problem seems to be that a domain needs to be attached to the name, but nothing works.
I tried:
/sbin/mount -o nobrowse -t smbfs //domain\SERVICEACCT:[email protected]/SHARE /Volumes/SHARE
/sbin/mount -o nobrowse -t smbfs //domain\\SERVICEACCT:[email protected]/SHARE /Volumes/SHARE
/sbin/mount -o nobrowse -t smbfs //domain.mydomain.edu@SERVICEACCT:[email protected]/SHARE /Volumes/SHARE
The last one confuses the heck out of the system. Any ideas?
Thanks,
Andrew
Andrew W. Johnson
Sr Macintosh Systems Administrator
Department of Teaching Learning & Technology
Division of Information Technology
Stony Brook University
Computing Center Room 115
Stony Brook, NY 11794-2400

Found the solution to my own problem. Syntax needs to be:
DOMAIN;USERNAME:[email protected]/SHARE

Office document sharing failure on server 2003 (SMB issue?)

We have a major issue running Office 2003 and 2010 on Windows server 2003 in a corporate AD environment. Since upgrading workstations from XP to Windows 7 we find that many users loose locking of Excel and Word files between 20 minutes and 6 hours
after opening. This allows a second user to open the file, save it, then the original user saves and the first users changes are lost.
We have tried everything we can think of, removing AV software from severe and client, patching completely, wiping serve rand building from scratch, etc. We have run out of ideas from Microsoft tech support, cannot get any joy from our account manager,
and are out of ideas. Office 2013 also seems to have the same problem from our testing.
The issue is active for files from Excel and Word, and does not matter whether it is a file format in the legacy 2003 format or the newer 2010 format.
FYI - This cannot be replaicted using Widnows XP on the same network / server / document - It is specific to WIndows 7 !
Has anyone had this problem and can anyone help?
...Jon.
...Jon.

Hi Jon,
When opening an Office file, a temp file will be created in the same folder. A second open session will check if any related temp file is already exists and if it does, Office will prompt that the file is "in use".
Thus please first check if a temp file will be created (it is a hidden file) when opening an Office file - have a try with creating a new shared folder with Everyone - Full Control for the test and if this will work, check permission settings of the original
shared folder.
If you have any feedback on our support, please send to [email protected]

SMB issue

Hi all,
I recently upgraded my Panther server to Leopard server and all my Windows machines can't connect to the smb service now. Any insight?

not much really, since there wasn't any problem with smb on my previous panther server, I never really looked at the log. It does, however, kind of keep repeating itself like this in the SMB file service log....
"[2008/03/22 23:16:35, 0] /SourceCache/samba/samba-187/samba/source/smbd/server.c:main(890)
smbd version 3.0.25b-apple started.
Copyright Andrew Tridgell and the Samba Team 1992-2007
[2008/03/22 23:16:35, 1, pid=54033] /SourceCache/samba/samba-187/samba/source/lib/utiltdb.c:tdblog(662)
tdb(unnamed): tdbopenex: spinlocks no longer supported
[2008/03/22 23:16:35, 1, pid=54033] /SourceCache/samba/samba-187/samba/source/lib/utiltdb.c:tdblog(662)
tdb(unnamed): tdbopenex: spinlocks no longer supported
[2008/03/22 23:16:35, 1, pid=54033] /SourceCache/samba/samba-187/samba/source/lib/utiltdb.c:tdblog(662)
tdb(unnamed): tdbopenex: spinlocks no longer supported
[2008/03/22 23:16:35, 0, pid=54033] /SourceCache/samba/samba-187/samba/source/registry/regdb.c:regdbinit(242)
regdb_init: Failed to open registry /private/var/samba/registry.tdb (Resource temporarily unavailable)
[2008/03/22 23:16:35, 0, pid=54033] /SourceCache/samba/samba-187/samba/source/registry/regfrontend.c:initregistry(114)
init_registry: failed to initialize the registry tdb!"
and in the name service log.............
"[2008/03/22 23:06:36, 1, pid=15774] /SourceCache/samba/samba-187.4/samba/source/lib/utiltdb.c:tdblog(662)
tdb(unnamed): tdbopenex: spinlocks no longer supported"
other than that, I don't see anything.

? SMB issue - anybody experienced this one?...

when PC clients log into our server, they see a number of network folders or 'shares' (6) and a Printers and faxes icon, and one share icon with their Forename Surname as its name .
These shares are all on internal drive of X-Serve.
If they access share/folder 2,3,4,5 or 6, they can navigate back to the top level of this directory and see shares 1 to 6.
However, if they access Share 1, and navigate back to the top level, they can only see shares 2 to 6?
Why should this be?
Share 1 has ACL set for 2 groups - Managers and STAFF with Permission to Read and Write
Shares 2-6 only set for STAFF, Permissions Full Control
Not sure why share 1 has 2 Groups as no sensitive data involved and Managers are already members of STAFF
New to this IT responsibility - quite what is the difference between ReadWrite and Full Control
Macs are internal to our part of organisation but client PCs are IT's and are locked down.

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
Since your post is off-topic, I am moving it to the
off topic forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

SMB/NAS connection issues

I've read through everything I can find on this issue and there appears to be no solution to SL breaking SMB connections to an NAS. I have a no-name NAS with no password protection at all (and I have no access to change/upgrade the firmware of the NAS). When I try to connect, via CMD-K or in Terminal, I get the same error as everyone else seems to be encountering. The solution to use a password in caps doesn't apply since the NAS isn't password protected. Nor does the port 139 solution or adding to my /etc/hosts file. Does anyone have a working solution, or should I just trash my NAS (with all my vids, music and pics on it) since Apple obviously doesn't want its users to use anything other than a Time Capsule.

Yes they have non-existent tech support, but since this NAS worked fine in 10.4 and 10.5, I don't believe it's a problem with the NAS. It was only after the upgrade to 10.6 that it could no longer connect. Since there's a couple of threads already about SL SMB issues, I definitely don't think i'm alone in having these issues. It's a shame that I have to consider downgrading to an older OS (or have to buy a new NAS) just to get what was previously working, working again. Buying a new NAS isn't really an option for me right now, since the NAS is working fine (all my Windows and other devices connect fine to it, just the MacBook can't anymore). My point of the question was really to see if anyone had a definitive answer or solution to this problem, since the ones i've seen suggested don't seem to solve the problem for everyone.

Multiple IP Address Issues

This has been driving me crazy for a while now. Mainly because I solved this once for myself earlier this year! I cannot find the solution again and I need help. Two Snow Leopard clients I have, (10.6.6) are returning three IP addresses in DNS. One for each is their correct static IP, the other two are odd.
For example (not actual IPs):
PowerMac1.domain.com is returning 192.168.1.38 (correct), 192.168.242.1, 192.168.138.1
iMac1.domain.com is returning 192.168.2.13 (correct), 172.168.28.1, 172.168.16.1
This happens with Windows nslookup or Apple's dig, of course.
Like I said, I managed to fix this on another system (running Snow Leopard server) a while back. I believe it was an SMB issue? Don't really remember.
Any help is greatly appreciated!

This has been driving me crazy for a while now. Mainly because I solved this once for myself earlier this year! I cannot find the solution again and I need help. Two Snow Leopard clients I have, (10.6.6) are returning three IP addresses in DNS. One for each is their correct static IP, the other two are odd.
For example (not actual IPs):
PowerMac1.domain.com is returning 192.168.1.38 (correct), 192.168.242.1, 192.168.138.1
iMac1.domain.com is returning 192.168.2.13 (correct), 172.168.28.1, 172.168.16.1
This happens with Windows nslookup or Apple's dig, of course.
Like I said, I managed to fix this on another system (running Snow Leopard server) a while back. I believe it was an SMB issue? Don't really remember.
Any help is greatly appreciated!

SMB Issues in 10.6.8

Similar Messages

Maybe you are looking for