Connecting to smb servers

Will Yosemite address the Mavericks problem in connecting to smb servers?

We have this problem in our office too. Have talked to apple support, microsoft support, two different IT consulting companies, and multiple "techy" friends of the company - all to no avail. Most seem to say the same thing "there's nothing wrong with your connection" - I suppose because technically it can still connect to the server. But yes it IS a real PROBLEM! So here's the specifics on our end:
MS Server 2012 - Multi volume/drive server managed by IT consultant, all service packs, patches, yada yada, etc. installed and functioning
To connect (mount) - In finder, use command K to connect to server. Address: smb://XXX.XXX.X.XX/Volume Name
Enter credentials for access
Spinning Wheel
Eventually volume mounts.
Try to open a folder - folder content empty.
Wait 10 minutes or so, folder content populates.
Open sub-folder
folder content empty.
Wait 10 minutes or so, folder content populates.
and so on.
Also drops connection completely if the screen saver comes on - then you have to start the process over.
This was not how the system behaved previous to Mavericks update.
Workarounds we have tried:
Use cifs instead of smb - a bit faster but connection is still lost on sleep and folders still take a long time to populate.
Use 3rd Party app like Pathfinder - works much better but really?! I have to pay $40 per user to do something the OS should already be doing at a basic minimum!
Specify port 139 - trying this now - seems a bit faster but too soon to tell.
Bottom line - I really hope this is addressed in Yosemite too - otherwise I'm going to wipe my system and go back to an earlier OS version. fun.

Similar Messages

HT200158 Connecting to older SMB servers from Mountain Lion

Lion had depreacated support to older SMB servers. I get following error on trying to do that:
The version of the server you are trying to connect to is not supported. Please contact your system administrator to resolve the problem.
But I could still connect using the workaround given in the knowledge base article.
sudo sysctl -w net.smb.fs.kern_deprecatePreXPServers=0
HT4697: OS X Lion: Connecting to older SMB servers that do not support UNICODE or NT style commands
http://support.apple.com/kb/HT4697
This does not work in Mountain Lion. I get an error. net:class not implemented. Anybody help?
When I tried sysctl -a | grep smb, I only see following options.
net.smb.fs.version: 107000
net.smb.fs.loglevel: 0
net.smb.fs.kern_deadtimer: 60
net.smb.fs.kern_hard_deadtimer: 600
net.smb.fs.kern_soft_deadtimer: 30
net.smb.fs.tcpsndbuf: 261120
net.smb.fs.tcprcvbuf: 261120
There is no option about net.smb.fs.kern_deprecatePreXPServers.

Found a way for preXP Samba sharing to work.
Download & Install Oracle's Virtual Box.
Setup a Windows XP virtual machine.
(select the appropriate network and sharing settings)
Install Windows XP SP3 onto the virtual machine (you'll need a valid licence key).
And that's it.
I run a virtual box version of Windows XP on Mavericks every time I want to connect to an older Samba share.
It just works.
I have my Mac OS hard drive setup to be shared with the virtual Windows XP machine, so I can drag and drop anything from the Samba share to my Mac hard drive and vice versa, within the emulated windows environment.
I would have loved to run a virtual Snow Leopard instead of Windows XP, but couldn't get it booting correctly, =S. So went with XP instead. Simple, =).

HT200158 Connecting to older SMB servers in Mavericks

Have anyone got this work? I got Thomson router and FAT32 usb-drive connected into it and OS X is Mavericks.
There is a solution for this problem for OS X Lion (OS X Lion: Connecting to older SMB servers that do not support UNICODE or NT style commands), but I don't got it work in Mavericks.

Found a way for preXP Samba sharing to work.
Download & Install Oracle's Virtual Box.
Setup a Windows XP virtual machine.
(select the appropriate network and sharing settings)
Install Windows XP SP3 onto the virtual machine (you'll need a valid licence key).
And that's it.
I run a virtual box version of Windows XP on Mavericks every time I want to connect to an older Samba share.
It just works.
I have my Mac OS hard drive setup to be shared with the virtual Windows XP machine, so I can drag and drop anything from the Samba share to my Mac hard drive and vice versa, within the emulated windows environment.
I would have loved to run a virtual Snow Leopard instead of Windows XP, but couldn't get it booting correctly, =S. So went with XP instead. Simple, =).

Can't connect to SMB share on Windows server from only ONE mac

I have over 20 macs on my network. All are running the same version of the OS. (10.4.9) Almost all of the macs can connect, using SMB, to our Windows 2000 file servers...but only ONE of them can not. When I try from that mac, I get the following error:
"The finder cannot complete the operation because some data in "smb://myservername" could not be read or written. (Error code -36)"
This same mac that has this issue can connect to any of our other Win2K file servers and all my other macs can connect to the server that this mac can't...which is very confusing for me because that tells me that the mac is fine and the Win2K server is fine as well...
Any ideas?

-36 is a bit generic, but usually means the Windows® machine is denying because of bad Password. Have you tried deleting that particular reference/share in Keychain Access and redoing it?

10.9.5 update smb servers not working

I just updated to 10.9.5, one of the items was said to improve stability for smb servers, which I use and they have been somewhat unreliable. Immediately after the update I can't access them at all. Can I undo this update? Is there a way to fix this?
I get the following message:
The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.

You should have at least 2 backups or you could end up losing all your data. You can use Time Machine and or a clone.
Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
Feedback
Time Machine Basics
Time Machine Basics (2)
Clone software.
Clone - Carbon Copy Cloner (Often recommended as it has more features than some others)
Clone – Data Backup
Clone – Deja Vu
Clone - SuperDuper
Clone - Synk
Clone Software – 6 Applications Tested
Commonly Used Backup Methods

Can not connect to SMB network drive

After upgrading to Lion, I am not able to connect to my Buffalo Terastation NAS box through SMB or AFP. After some research on various boards, it appears that the samba implementation changed in Lion and will require an update to your NAS box firmware to get it to work. Since this is not possible for the vast majority of customers (lack of vendor support, end customer technical ability, etc), I'm wondering if there is any official word from Apple to provide support for the previous samba implementation.

This might help. I have a Seagate Dockstar (Pogoplug w/samba) with attached drives connected to my network that was easily discoverable with Bonjour in Snow.
From my experience -
I got the SMB share working (sort of) in Lion 10.7
While the network hub and connected drive(s) won't automatically appear as a Connected Server, or Bonjour Computer I was able to find the Dockstar by going to -
Go/Connect to Server and then enter it's specific info - smb://fabx2d09fe (my device's actual number was different than this).
The dialog pops up for name and password - or connect as Guest. I couldn't remember if I had set these so tried Guest and was able to access/mount the drive on the desktop and sucessfully read/write to/from it.
I may have to always connect to recent servers to get the thing to mount so it's not as automatic as Bonjour in the sidebar - but it does work!
This mostly solved the issue for my needs....maybe it would work for yours?

Lion can not connect to smb if use root login

I found if use root account login lion, that can't connect to smb but use other account ok.who can help me take a look?

This might help. I have a Seagate Dockstar (Pogoplug w/samba) with attached drives connected to my network that was easily discoverable with Bonjour in Snow.
From my experience -
I got the SMB share working (sort of) in Lion 10.7
While the network hub and connected drive(s) won't automatically appear as a Connected Server, or Bonjour Computer I was able to find the Dockstar by going to -
Go/Connect to Server and then enter it's specific info - smb://fabx2d09fe (my device's actual number was different than this).
The dialog pops up for name and password - or connect as Guest. I couldn't remember if I had set these so tried Guest and was able to access/mount the drive on the desktop and sucessfully read/write to/from it.
I may have to always connect to recent servers to get the thing to mount so it's not as automatic as Bonjour in the sidebar - but it does work!
This mostly solved the issue for my needs....maybe it would work for yours?

MBPro Can't Connect through SMB, Can VNC to iMac then SMB though

Hey guys,
I have an MBP with 10.5.6 and an iMac with 10.5.6
I have SMB connections to a file server that I can connect to. On the iMac (hard wired into the network/domain), all connections are fine and I can connect to the server whenever.
On the MBP, though, i can only connect to the server during what seems liek specific times of the day. For example in the morning, I can connect and transfer files without a problem, but in the evening, it won't let me connect. The servers do not have any time of day preference and do not regulate users based on time of day either. Also, my VPN is working fine and is a non issue.
What is strangest though, is that I can VNC to my iMac, then connect to those very same servers even though I couldn't directly from the MBP.
Any ideas?

I have also noticed that this is happening to a few other people in my department, so it seems like it may be an OS thing, but I am still not sure. Anybody?

Does Lion support connecting to SMB shares?

Hi there,
Has anyone else had issues connecting to SMB shares since upgrading to Lion?
I am unable to connect to any previously accessible shares hosted on local Linux or Windows servers.
Thanks,
Bob

For those of you trying to access SMB shares, I found a free and easy solution.
Since a lot of people report they are able to access their NAS using apps other than the Finder itself, I decided to look for a free Lion-compatible File Manager to use instead of Finder.
I have found muCommander ( http://www.mucommander.com/ ) and indeed it works fine. All I did was click on the button highlighted bellow, go to "bonjour services" and select my NAS. It prompted me for my username and password and voilá, it works fine.
I keep Finder for everyday use and just load muCommander when I want to access the NAS. At least now I don't have to start my WinXP VM anymore just to access it.
Hope it helps you all.

Can't connect using SMB, but can with CIFS

I'm trying to connect to a windows share from my PB running tiger. I can connect fine in finder going 'Network/Workgroup/PC_Name/' but if I us the 'Go > connect to server' in finder I cannot.
I click go, connect to server and type "//192.168.0.3/My Documents/' it says cannot find sever. Same if is use the smb prefix.
When I get info on the share it says CIFS://WORKGROUP;MARK@PC_NAME/My Documents/
so I can't understand why I cant connect using SMB, I've checked directory access and SMB is enabled, workgroup is set. I know I've been able to connect via SMB before, not sure why I can't now?

For the longest time I have had an Alias of all my remote PC servers in the Dock. One click and I'm connected. As of 10.4.5 those Alias' no longer work. When I click on them instead of getting the volume mounted and ready, I get a the login window with the Workgroup and User Name asking for the password that should be in the Keychain. I enter the password and click connect and get nothing. No errors, no pings, just the Network icon in the Dock turns into a ?.
I go to the Network Browser and the servers show up in their proper workgroups. I click the server, get the login window, put in the password and get an error that the "Server" could not be opened, because the original item cannot be found. With three buttons "Delete Alias", Fix Alias", and "OK". If it can't be found, then what is it showing me in the browser?
I have 10.4.4 on another partition for emergency backup use in the event 10.4.5 fails (and it is). I went to 10.4.4 and all works just fine. All this started in 10.4.5.
G4 FW800 Mac OS X (10.4.5) Totally Stuffed/Max'd Out with lots of great toys.

WinXP AD users can't connect via SMB

Server is an Intel Xserve, 10.5.8.
Windows users get authentication errors when attempting to connect via SMB on the Mac server. The server is bound to Active Directory, and the Mac users are able to connect via AFP just fine. Macs also cannot connect via SMB. I get the error message "NTSTATUS_WRONGPASSWORD" when the user attempts to log in.
Local users are able to connect via SMB, but I don't want to re-enter a dozen or so PC users on this server if I can avoid it.
In the /var/db/smb.conf file there is an entry for a password server that may not be correct, but if I change it to the password server I've been instructed to use, the file flips back to the original setting when I stop and start the SMB service. I think if I make changes to the /etc/smb.conf file outside the END section, where the comments say to make changes, they will carry over to /var/db/smb.conf, but I'm not sure of the syntax.
If you need me to post the testparm output I can do that.

You're going to have to look into potential underlying issues.
I don't know what's happened for you, but I have an identical type setup for a client done over a year ago and no such problems have occurred.
What does the UNEDITED (please !) result of (using the Terminal) the following show:
cat /Library/Preferences/edu.mit.Kerberos
What happens when a user can't connect (error message, loginwindow shake) ? Are all client machines & the server using a common (eg internal) time-server ?
Be sure to see http://docs.info.apple.com/article.html?artnum=300765
And certainly read through Bombich' excellent PDF (click on the icon of it) at
http://www.bombich.com/mactips/activedir.html - esp. the troubleshooting section
for when a user is unable to login.
Currently, I'm not able to check/verify the settings for any of the servers I've setup for clients in a "magic triangle" setting. I'm not certain about the "passwordserver" entry,
on the one hand the actual passwordserver is actually part of

How to connect to two servers behind a firewall

Let's say I have a LAN with two independant servers, one at 192.168.2.10 and one at 192.168.2.20
As it is now, I can fwd the 548 port to one server and it works.
Is there a way i could connect to both servers, maybe having one and port 548 and one at 549, so if I connect using the default address, it will connect to server A and to the adress plus the port :549 it will connect to server B
I tried forwarding port 548 to one server and port 549 but for now, my router/firewall complains that I have a port conflict.
What's the simplest way to achieve what I would like.

Oh man, I think I've seen the answer to that in these treads, but it'd be around 20-30 pages back... iirc it would involve editing Hosts' or hppd file... BIG Help I know... but perhaps a real expert will be along shortly!

Why can´t i connect to Windows servers after installing Lion?

Why can´t i connect to Windows servers after installing Lion?

Me too!
MacBook Pro 15" 2011, OS X Lion 10.7

Not going to sleep when PC is connected via SMB

If I have my mac set to go to sleep after a period of inactivity, it goes to sleep while my PC is still connected to it via SMB. Not while any files are beig used, but if they're not used for a while. Is there any way I can change this anyone?

Sorry - I was very tired when I posted that - I guess it could have made more sense!!
What I want is for my mac to only go to sleep if there's nobody connected via SMB.
At the moment, I either have to set the sleep timer to never, or when I start to work on a file from the mac on the PC I find that the Mac's gone to sleep even though the PC's switched on and connected to it. Then I have to go and wake up the mac and reconnect with the PC.

Connecting two distant servers via a common WAN Internet connection.

Hi all,
I have two servers located in two different countries. For example Server A (Windows 2003 with Active directory) is located in Singapore. Another Server B (also Windows 2003 Server with Active Directory) is located in Kuala Lumpur. Both computers are connected to Internet via local ISP (WAN connection with dynamic IP) to respective countries. There is few local users at each places which are connected to local servers at both places with LAN.
I would like to connect these two servers togather via WAN (Internet- may be tunnelling, VPN, I don't know much what are other technologies) My objective is to connect both Server A and Server B so that I can keep track of active directory information, user management and authentication. Please let me know how can I achieve that? What are needed and what configuration and addition device, server needed. Please give me simple, detailed cost effective methods.
Thanks.

First you want to get static IP's and then you can setup an IPSEC tunnel or site to site VPN. Then you will want to creat a trust between the 2 domains if they are in different forests. Then you can add your user account to a universal group (forest functional level must be at Server 2003 level) for enterprise management.
James Goodwin - Senior Technical Instructor & Network Infrastructure Expert
MCT, MCP+ I, MCTS:Server 2008, MCTS: SCCM, MCTS:Vista
MCSA:S, MCSE:S, MCITP:SA, MCITP:EA , MCITP:ES, CCNA,
CCSI(# 32018),C|EH, C|HFI, C|EI, HDSA, A+, Network+, i-Net+, Server+, Security+
My Blog:http://thattrainerguy.blogspot.com/

Connecting to smb servers

Similar Messages

Maybe you are looking for