Can't connect via SMB

I get prompted for credentials when I do this via the gui.

I also see on the server end that it is using the correct username (ie. the one i enter into the gui, not the Mac ones as you suggest)

Also, mounting the share manually via the command line still only works for access via the command line for me.

Glad it's working for you now though 🙂

The actual bug is that Lion is failing to pull the saved username from the Mac KeyChain.

Instead it is using your mac username.

Therefore if your mac username is not equal to your server account name; it will fail to mount, if you use saved credentials

*** Here's the tested workaround we are using.

1) Do NOT save the user credentials for the network share in the keychain. (If you already did; then use KeyChain program to delete the saved credentials ((search for server name and delete items of type "network password")) )

2) Change your Finder Cmd-K URLs to include your Network Short username (your NLTM username).

Examples:

smb://NETWORKUSERshortNAME@servername/SHARENAME

smb://networkdomain\networkusershortname@server/SHARENAME

You can't use UPN network names because the Extra @ symbol will confuse some servers.

Your mileage will vary if you do:

smb://username@domainname.com@servername/ShareName

3) Finally when prompted for username and password; enter your network password and click OK. Do not save the credentials.

Not a UI bug then, but a keychain bug?

Thing is I already tried emptying my keychain of any related items, and cleared the connection history, and even rebooted the system, and that prompt for credentials still doesn't come back up when I try to connect. Anymore tips for clearing connect to server save credentials flag?

I agree...it's not a keychain bug either. This step didn't work for me either. In fact, nothing is working for me. Seems there are 12 solution to 12 different people...

There's something seriously wrong (with Lion).

jan78 wrote:

A Solution for mounting Lion SMB Shares from a linux client.

(I'm using an ArchLinux with Samba 3.5.10-1 and cifs-utils 4.9-3, but it shouldn't matter)

mount.cifs needs the additional options "nounix,sec=ntlmssp"

i.e. mount.cifs //192.168.xxx.xxx/test /mnt/test/ -o user=******,password=******,nounix,sec=ntlmssp

I was getting the following:

WARN [negotiate.cpp:266] 192.168.1.33 SMB client not supported - Unicode, NT Errors, Long Names and Extended Security are required

And then I tried adding "sec=nltlmssp" to my mounting options and went away.

HOWEVER, I still get the following from "/usr/sbin/smbd -debug -stdout"

smb1_dispatch_one [smb_dispatch.cpp:377] dispatching SMB_COM_NEGOTIATE

socket_look [unix_socket.cpp:285] socket_look: rdsz 0 ---> EPIPE

Anybody else hit this and getting anything similar? I'm guessing my EPIPE is the problem. I even tried "/etc/init.d/iptables stop" on my Linux box to open up the firewall, but this was to avail.

Update:

I've been in email discussion with Apple bug report and after submitting error logs, dump files from Lion and SL OS running Macs from my workplace, they finally reported that it is a known bug. Let's hope it gets fixed.

i have this problem too, but only to one 2008 r2 server. i installed 2 new servers (different sites) they have the same firewall rules, same sp level same updates etc.

i can connect to both via smb on the lan but cannot talk to one of them when on the vpn.

i have tried mounting via terminal and also the smb://user:pass@server/share but does not work, i only get the error;

there was a problem connecting to <server name>

the server this file server will not allow any additional users to log on

connecting with 10.6 / xp / win7 via vpn is fine, it is just 10.7 lion with the problem (10.7 / 10.7.1 / 10.7.2)

i have tested this via mucomander and working ok, but dont really want to get users to use it they want to use the mounted drives on the desktop.

I spent this entire weekend trying to figure this out. So, I tried what Jagoan did with creating a "user" account and it worked!! Amazing, after racking my brains about this and that simple suggestion was the answer I needed all along. At least it's a temporary fix for now until Apple can fix the bug.

I'm connecting Mac OS X v10.7.2 Lion to Windows XP pro sp3

well nevermind. my excitement was flying high for about 10 minutes and then all of a sudden the connection disappeared and now I'm unable to reconnect. I tried logging out and restarting. nothing worked.

Last night, I was beginning to think that Apple got so excited about the iCloud that they probably purposely created this bug so that we would all get frustrated and subscribe to the iCloud and then our problems would all go away in an instant. But then I think it's a ridiculous thought because the SMB setting is still available under File Sharing in the prefs. I'm just frustrated because I need to get files off of my Mac (it says my startup drive is full) and I'm now unable to do so with my current hardware. I honestly believe that Lion has taken me back 12 yrs, to when I wasn't able to transfer files to/from a PC. I now regret purchasing Lion and wish that I kept Snow Leopard. Maybe I should tell all my friends to not purchase Lion for at least another 6 months and have them spread the word. I can't believe that Apple released an OS product having this bug. Didn't they test it prior to launch? Oh right, they tested iCloud instead. Now, they portray themselves as unreliable to me.

I'm getting a similar issue, that i cant quite find an answer to within these man posts.

I've jsut installed a new NSD, OS X 10.6 has connected to it as an SMB server, and teh access permissions are set through teh device's own software.

However, when another user accesses the drives they have restriced access, to sub folders, as you showed on once of your posts. The user has full access on the device itself, and when looked at through teh get info pane it shows no ablity to change their permissions only that they have no access.

futher when they create a subfolder this is restricted accessablity by them only, even though the drive controls permissions.

in my case the entire network is mac based there is only one virtual pc via vm fusion that needs to access the NSD....

I am pulling my hair out... any ideas would be very helpfull other wise the new NSD is a complete waist of time and money and its back to drop box....

For certain Windows versions you need to blank the DOMAIN, using the backslash character.

For example, if you want to connect with a Mac user like "pressctx", you need to introduce "\pressctx" as the username when connecting from Windows. This will blank the domain part that is NOT needed for a MacOS SMB share connection.

The password is, as normal, the password of the original Mac user account.

MacOS X version tested: Mac OS X Lion

Windows version tested: Windows 7 Home Premium

Share used: SMB network connection sharing for Mac OS X

Hi guys,

after carefully reading a million posts about this issue, I finally figured what would resolve it in my case.

What I did was:

1. Open Finder.

2. Select "Go" in the menu bar.

3. Select "Connect to Server" menu item.

4. Enter the server address as follows (this example fits of course only my environment): smb://workgroup;alexanderschott@192.168.178.100/media

Please note that

a) "workgroup" refers to the workgroup configured in the WINS settings in OSX Lion.

b) the ";" is important!

c) "192.168.178.100/media" points to the share on my NAS

d) LAST BUT MOST IMPORTANT: "alexanderschott" is my user in Lion. On my NAS I created a user with the SAME username (Seagate Blackarmor 110)!!

Hope this helps!

Alex

But what happens if the computer is part of a Windows domain? Wouldn't that take the computer out of your Windows domain entirely? If you want to re-join the Windows domain, then the domain users who log back in from this computer would lose their profiles and Windows re-creates an new profile for them. Is that the case? If not, how are you able to re-use the existing domain profiles every time you take the machine out and back in into the domain?

Just in case, I found an answer that worked for me under a Windows Forum. I don't want to copy and past the whole answer here, just in case it is agaist the rules, but it is under the question "Windows 7 cannot connect to Mac - Help!" The answer is from a Windows person, Shinmila H. Surprisingly the setting is in Windows, not in Mac. It has to do with LAN Manager Authentication in the Group Policy. She has two options, one for Windows 7 Pro under Group policy settings and the other is a direct edit to the registry for those who don't have Windows 7 Pro. My situation was that I did not have any problem connecting from XP Pro to Mac, but the Win 7 Pro machines wouldn't connect. My Win 7 machines would "see" the Mac Server, but wouldn't connect via the login options. Now they all open the folders right away without having to log in. (Same User ID and password on both sides; Windows and Mac.) Below is the link; not sure if it will work.

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/windows-7- cannot-connect-to-mac-help/a2a62c23-0aae-4b5a-a646-f089468bc6cc?page=1&tm=132803 0881784#footer