Can't connect via SMB

Prior to installing Lion, I would connect to our shared drives at work via SMB. Today, after installing Lion, I can't connect to my shared drives. The one SMB connection that works is to an FTP server. I connect via SMB to map the drive in my Finder rather than using an FTP program. This still works fine.


However, I can't connect to the shared drive for file sharing. In the Connect to Server box, I have "smb://PathToFiles" . Is smb:// the correct prefix to use now that Lion is funky with SMB support?


I'm sorry...I really don't know much about SMB connections, what kind of server it is that I'm trying to connect to, or much else. I know we run Windows Exchange, but I'm not sure if that's the server that hosts these shared drives...I just need to connect to get back to work. Any help would be AWESOME.

Posted on Jul 21, 2011 1:55 PM

Reply
132 replies

Apr 28, 2012 8:37 AM in response to Hibernian56

No, no. Don't be confused. Putting aside your asterisk-ridden way of saying things I actually agree with you: Apple should not include in its OS ANY support for networks from competitors unless the network drivers are provided by said competitors.


When Novell Netware was a more commonplace networking protocol everyone was expected to download Novell's drivers for it. And this was good, this meant support was demanded to the one that should provide it, and stupid pieces like what we're seeing were rightly shot down as the mouth frothing non sequiturs they deserve to be seen as.


In this case, Apple has been forced out of using Samba and has had to implement their own version of the protocol. They shouldn't have, to my eyes, even attempted to do so. They did it probably because it made good business sense and they probably didn't count on the fact that Samba has made by now a monopoly of bad network implementations that, while faulty and bug-ridden, is a standard nobody else can copy without using their software. Since Samba has made all efforts to not be included in OS X they have succeeded in diverting the attention and complaints to Apple, which was part of their intended goals.


I agree with you: Apple should NOT provide this support. It shouldn't, actually, provide support for anything other than appletalk and NFS. That way people would realize that to be compatible with Windows Networking they need to get software installed that provides the compatibility. Either install Samba by themselves or one of the excellent Windows Networking alternatives that exist out there.


Now, feel free to keep trolling all similar threads in the discussion forums as you seem to be doing. I hope that works out for you.

Apr 28, 2012 9:27 AM in response to Eduardo Gutierrez De O.

Eduardo Gutierrez De O. wrote:


No, no. Don't be confused. Putting aside your asterisk-ridden way of saying things I actually agree with you: Apple should not include in its OS ANY support for networks from competitors unless the network drivers are provided by said competitors.

I'm not confused, I'm annoyed and frustrated that I have to spend my Saturday, and most likely tomorrow trying to get things working as they were before the mess that is OSX Lion entered my life.


Oh, and its not an asterik-ridden way of saying things, its called English, I generally don't use expletives, the word that caused offence to Apple was H E L L if you can believe that!!


I have no interest in Windows machines, our office was happily in the process of removing them entirely, if you have seen anything of Windows 8 you would probably agree that we will need to pick up the pace.


This is my point with Apple; they just do things their way regardless of impact and if something breaks (which is usually the case) they let the users generally find work-around's until they catch up. I filed a bug report about the Internet Sharing issue and it took four months for a response, which was cryptic at best and didn't work. My SMB bug Report has not been dealt with yet.


What's the point of beta testing if they ignore comments? They were told during beta testing of Lion that SMB was broken, but nothing was done.

I agree with you: Apple should NOT provide this support. It shouldn't, actually, provide support for anything other than appletalk and NFS. That way people would realize that to be compatible with Windows Networking they need to get software installed that provides the compatibility. Either install Samba by themselves or one of the excellent Windows Networking alternatives that exist out there.

I don't know about that. Most SME's can't afford dedicated sys admin's (that why I'm here on a Weekend, a rare rain free one at that!!). We want and I think pay over the ods for Apple hardware that is purportedly more reliable and "Just Works". My biggest problem with Apple hardware is its sometimes inexplicable failure to interface with third party hardware and systems.

Now, feel free to keep trolling all similar threads in the discussion forums as you seem to be doing. I hope that works out for you.

Dear oh dear, why is posting on multiple threads seen as trolling, I posted links to your solution on other sites, is that Trolling too? It's funny, its the first time ever I have been accused of Trolling, I'm a moderator on several forums too. But that's what happens when you question Apple.


The above issues are why I check these threads, its not Trolling. If I or any other user that has invested many thousands of Euros, Dollars or whatever in Apple Hardware that doesn't work feel like they need to "vent" or share their pain, that's not trolling. A problem shared is a problem solved, it might also wake Apple up.


We upgraded machines in good faith, spending good money to discover they are only partially functional due to a purposeful ommision of STANDARD networking protocols made by Apple. You spent some of your time developing a free tool to help fix THEIR mess. They have done nothing about it. How do you feel about that? I appreciate your effort, do they?


Anyway, back to fiddling with SMBup now, thanks.

Apr 28, 2012 1:25 PM in response to Hibernian56

I wasn't clear.


I feel you're trolling not from what you're saying but from the tone and wording you choose to use to say it. You're free to do so, I'm free to interpret it this way (as it's how it looks to me).


Of course, you being free to say it doesn't mean you're right. Clearly to me you're wrong (not to feel wronged, though, that's your right) and your "reasons" don't hold water, but I don't need to convince you of it. Nothing I say will make you think otherwise.


I made SMBUp because a lot of people didn't understand Apple was not including Samba any more in OS X (most didn't know what Samba is) because the Samba license is not really compatible with their operating system. I was surprised both that it took them so long and that nobody had made something like SMBup before me.


Now, I don't think Apple should've EVER put Samba in OS X. Including it gave the incorrect impression that somehow they were supposed to support a networking technology owned by Microsoft (which, by virtue of being proprietary, required using a closed-room reverse-engineered implementation to run in non-Microsoft systems).


They should've never included it. That way the Internet would be full of "How can I connect my windows server/mediacenter/weird router with a usb drive to my mac?" tutorials, pointing to the still-current solutions of either installing Samba or purchasing one of the excellent SMB packages out there for OS X (Thursby's Dave being the most prominent one, Samba being always a worthy alternative).


By including a software they didn't have control of they set themselves up for the day they'd need to remove it due to this license clash, and then people would've "learned" OS X is supposed to support SMB/Windows Networking (IT'S NOT, and it's ridiculous to argue that it is).


My software (which doesn't help, to my knowledge, at mounting network drives, as it's main goal is to share them), doesn't path a screw-up by Apple but a common misconception from users, one that Apple unfortunately chose to feed by including functionality it should never have.


So, while I understand your frustration, I feel it's misdirected, misinformed and out of line. That's my personal opinion, of course. I don't think it's a bad thing to post negative feedback in forums, but I'm free to take offense in the wording used for these complaints, as it's my belief the way of saying things matters as much as what's actually being said.

Apr 28, 2012 3:12 PM in response to Eduardo Gutierrez De O.

As clear as mud. I really hope you don't interact with humans too often.


Anyway, we'll agree to differ, I'm done for the day 75% of the machines have been downgraded to 10.6, I will do the rest tomorrow so that my company can return to being productive on Monday.


We lost a valuable file last week thanks to the SMB issue. You can't back up a USB stick, which two people were sharing without backing up for over a week, madness. That will cost us three - four days for two teams to redraft off paper drawings next week. My boss is like an anti-christ. Your people skills remind me of him.


If I offended you, that's your issue not mine. Perhaps more human interaction would be good for you. I bet you're from Madrid, or is it Barcelona/? The football isn't going well is it? Maybe you need a holiday or a cat, something to stop you trolling.


Let me make the point ONE LAST TIME:


We have been using Mac's for years. SMB has been intergrated for years. Apple NOW decides to effectively drop support for SMB. Apple does this quietly and tells no one. Apple customers suffer and we are left to find solutions. It is effecting our productivity and therefore adding cost to our business operations.


Do you understand now? Will I translate it for you?


WHY ARE YOU OFFENDED? Are you a founder of Apple? Do you have shares in Apple?


Maybe you should be part of Apple, perhaps you could then form their release policy, strip everything out of OS X, no drivers, no codecs, nothing. Let the user dowload only what he needs. Just have some pretty iOS interface, iPhoto and iTunes. Lock the user out of all system files.


Out of line? It's Saturday, I have been in the office since 9am this morning fixing a problem that is not of my or any other Apple user's fault. I am really glad we are not in the same room.


To sum up, stop being such a Pajero.

Apr 28, 2012 5:01 PM in response to Hibernian56

Hibernian56 wrote:


Perhaps more human interaction would be good for you. I bet you're from Madrid, or is it Barcelona/? The football isn't going well is it? Maybe you need a holiday or a cat, something to stop you trolling.


Do you understand now? Will I translate it for you?


To sum up, stop being such a Pajero.


So, you try to insult me at the same time you're accussing me of trolling and asking why I feel offended?


I'm not from neither. I don't follow Football. "Pajero" is not a word used in Spain at all (although it's common in Latin America).


I'm sorry if my explanations don't agree with you. You're entitled to being angry but that doesn't make you right on whose fault these problems are. If you provide support for your workplace (as I do mine) you should've known Windows Networking is not 100% compatible with all versions out there (as I did and you rightly say was reported in betas). You could've saved you a week of grief.


I pointed out the error I saw in your blaming not because I have any interest in Apple but because it was incorrect, just that. I feel Apple brought this unto themselves but disagree with you on their mistake. To me was including software completely outside their control, without any assurance of ongoing support and without control over its licensing. Had they not done that people would be used by now to simply getting a SMB driver and would be happy about it (as they do tons of other things without any issues).


I don't see people suffering for getting Windows Media codecs from Flip4Mac or Perian today? Do you really see a difference there? This is not different. The only difference is that Apple made the error to include Samba in 2002 and now they're regretting they ever did. OS X should've never included SMB Support because it's a closed proprietary protocol (bunch of protocols, actually). SMB2 on the other hand is an open protocol and Apple does well implementing it. They do well integrating everything they can, as long as they can be assured the protocol is either open (SMB2), licensable (H264) or has an agreement in place (Java), and they currently do. Samba was the odd one and they've paid for it.


The fact that I don't agree with what you consider the source of your problem doesn't mean I don't sympathize with it (if I didn't I wouldnt've made SMBUp, actually). Neither pointing it out. If you fell better lashing out and showering ad hominems and other fallacies at me for pointing it out then feel free to do so. I made my point but can't force it on anyone.

Apr 29, 2012 9:58 AM in response to upeace

Ok all done here. Thanks Apple, another two days of my life wasted fixing your problems.


Apple really are beginning to loose the run of themselves, they have lost focus of their customers, they are certainly not "thinking different" anymore, just thinking corporate.


I know this is off on a tangent, but it reinforces my point about their recent treatment of customers;

http://www.seattlerex.com/seattle-rex-vs-apple-the-verdict-is-in/


The interesting thing is, I have two of these macbook pro's, one with the screen removed sitting in an office connected to an LCD panel. They are still great machines let down by a crappy third party component. As I said, I had the same issue, dead screen on one of them, but after a fair bit of weekend diagnostics I realised it was not a fried video chip. The heat off the video chip had fried a unbranded MOSFET surface soldered BESIDE the chip. Only very close examination under magnification showed this. A high quality replacement cost me €0.55!!!


I replaced the chip, but unfortunately as with most modern tech, it uses multi layered PCB's it was beyond repair, the heat damage was in a layer I could not get at. In the end I managed to get it working by disconnecting the LCD panel completely (which was found but confusing a hardware check due to the fried chip, hence failing to boot up).


So as you can see, great hardware let down by a third party component. But at the end of the day I don't buy a laptop based on the brand of the MOSFET used do I?

Apr 29, 2012 10:20 AM in response to Hibernian56

I was truly hoping Rex won that thing. Apple's behaviour was apalling and should've been punished.


I see it's been closed now, sadly with just the minimum amount paid by Apple and not enough PR damage for this to affect them (I also did my bit sharing this story but I don't think it got the coverage it should've got).


Even if I've had nothing but excellent support every time I've had Apple fix my stuff I still think these cases should be publicized as loud and wide as possible.


I hope the class action suit goes through, too.


Incidentally, this is not "the new Apple". Stuff like this has happened since the Apple II and happens in all these corporations. It should not be allowed and the punishment should be big and swift but sadly it's not recent or exclusive of Apple. I suspect it comes with the territory of becoming a large corporation (as none seem immune).

Apr 29, 2012 10:45 AM in response to Eduardo Gutierrez De O.

True, once the "suits" move in we are all doomed. Its a simple case of profits come first. I think issues experienced by Apple in relation to the nVidia for example set in motion a mindset of "deny at all costs" driven by the legal section of the suits. This unfortunately is part and parcel of the corporate world.


Both of the laptop I mentioned experienced the "exploding battery" phenomenon, remember that? Apple refused to acknowledge the problem as the product was out of warranty. That is until I was on the phone one day to Apple support telling them that I intended to use my laptop wearing shorts exclusively, and any resulting injury would be their issue despite their claims the batteries were no longer covered. I got my battery replaced soon afterwards.


As I said though, in my opinion Apple make great hardware, possibly the best. Having "fixed" my better half's HP DV6000 laptop four or five times, the pure frustration in opening it with it's nearly 60 screws, all of different lenght's with lots of ribbon cables that are just the right size, I had huge respect for the people that assemble the HP but utter disgust at the persons involved in its design.


I ended up giving her my old reliable Macbook Pro. Overkill for Facebook, but that's life!! I know it should run for ever as the programs she will run won't punish it as much as I used to.


Anyway, hopefully Apple will begin to listen, just like they used to. I don't really think a class action solves anything, only the solicitors win in the end, I think they just need to shift their sights back to the existing loyal (for now) customer and not the solely new customer.

Feb 24, 2013 12:24 PM in response to Eduardo Gutierrez De O.

Hey Eduardo...


I recently upgraded to Mountain Lion on my iMac but left my MBP alone for now. I have a Gen1 AppleTV that I use as a streamer running XBMC. I had problems keeping the "connection" between the ATV and the USB Media drive that I use so I installed SMBup. The ATV is hardwired (no wifi) to my network directly to my Airport Extreme. So now I can connect but upon power down of the ATV and re-powering the next day it "loses" the connection to stream. The ATV shows all the XMBC menus and is fully functional otherwise, but while it lists a movie that is on the USB drive, it won't play it saying the movie is no longer available. I went back to SMBup, unlocked and stopped Samba, then re-started it, locked it... and my movies stream just fine until the next power down.


Is there something in the settings that can be changed to ensure that the iMac/USB Drive/ATV talk to each other all the time when they are booted? I am not a technician so please explain in layman's terms LOL.😕


Mike

Feb 26, 2013 7:17 AM in response to Peter The Greater

As noted in last sentence LOL... I need a layman's explanation on why an Apple iMac combined with an Apple TV Gen1 won't stay "connected" for more than 24 hours. The link goes right to a Microsoft solution for a Windows PC running a MS operating system. I wouldn't have a clue how to find the iMac's registry and how to modify it.


Thanks for trying to help though. Maybe if you can explain it it would make sense.


Mike

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Can't connect via SMB

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.