Apple no longer supports SMB ?

Question

Level 1

50 points

Apple no longer supports SMB ?

I recently updated to os 10.7.4 and found that i could no longer mount SMB file shares

I reverted back to 10.7.3 and all is well, SMB File Shares mount with out issue. this issue persists accross multiple workstations.

I called Apple inquire and was told Lion no longer supports SBM. Im not sure I recived actual fact, or if the tier two apple care opp was just sadley missinformed.

Has anyone els had a hard time mounting SMB file shares after updating to 10.7.4 ?

Mac OS X (10.7.4)

Posted on May 23, 2012 6:45 AM

Reply

Answer 1

AOadmin Author

Level 1

50 points

May 23, 2012 8:21 AM in response to AOadmin

log of error event

May 22 17:10:44 Tests-MacBook-Pro NetAuthSysAgent[179]: checkForDfsReferral: mounting dfs url failed, syserr = Input/output error

May 22 17:10:44 Tests-MacBook-Pro NetAuthSysAgent[179]: smb_mount: mount failed to aofile1/data, syserr = Input/output error

May 22 17:11:18 Tests-MacBook-Pro NetAuthSysAgent[179]: checkForDfsReferral: mounting dfs url failed, syserr = Input/output error

May 22 17:11:18 Tests-MacBook-Pro NetAuthSysAgent[179]: smb_mount: mount failed to aofile1/data, syserr = Input/output error

May 22 17:21:48 Tests-MacBook-Pro com.apple.kextcache[203]: Created prelinked kernel /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.

May 22 17:35:22 Tests-MacBook-Pro Safari[215]: IPCClient: Server port 0 is invalid; looking it up again...

May 22 17:40:36 Tests-MacBook-Pro rpcsvchost[266]: sandbox_init: com.apple.msrpc.netlogon.sb succeeded

May 22 17:40:59 Tests-MacBook-Pro NetAuthSysAgent[241]: checkForDfsReferral: mounting dfs url failed, syserr = Input/output error

May 22 17:40:59 Tests-MacBook-Pro NetAuthSysAgent[241]: smb_mount: mount failed to aofile1/data, syserr = Input/output error

May 22 17:46:04 Tests-MacBook-Pro login[287]: USER_PROCESS: 287 ttys000

May 22 17:48:41 Tests-MacBook-Pro login[287]: DEAD_PROCESS: 287 ttys000

May 22 17:48:43 Tests-MacBook-Pro login[305]: USER_PROCESS: 305 ttys000

May 22 17:49:49 Tests-MacBook-Pro NetAuthSysAgent[313]: checkForDfsReferral: mounting dfs url failed, syserr = Input/output error

May 22 17:49:49 Tests-MacBook-Pro NetAuthSysAgent[313]: smb_mount: mount failed to aofile1/data, syserr = Input/output error

May 22 17:57:21 Tests-MacBook-Pro login[305]: DEAD_PROCESS: 305 ttys000

Reply

Answer 2

varjak paw

Level 10

170,200 points

May 23, 2012 10:13 AM in response to AOadmin

Mac OS X 10.7.4 most certainly still supports SMB connections. I use that feature every day to connect to Windows servers and have no problems. I don't know who you spoke to at Apple, but if they told you that Mac OS X no longer supports SMB, they were dead wrong. They may have been confused by Apple's use of CIFS, Microsoft's more current way of referring to SMB, as the terminology, though most things from Apple I've seen still refer to SMB.

What sort of server are you trying to connect to? Since the problem occurs with multiple workstations, it would seem more likely that the problem is with the server, either with setup or perhaps some incompatibility with 10.7.4 and that server's OS, rather than a blanket problem with your system.

Regards.

Reply

Answer 3

AOadmin Author

Level 1

50 points

May 23, 2012 11:05 AM in response to varjak paw

Hi varjak

thanks for your responce. were running windows server 2010.

the issue does seem local to 10.7.4

- ive experienced this issue on two workstations on seprate vLANs. Whats concerning is that when i revert the affacted workstations back to 10.7.3 I can conetect without issue.

On 10.7.4 i promt "connect to server" and im then prompted to enter user credentials, at that point i recive an error "there was an error connecting with (servername), contact your system admin (aka me) for more help.

I agree that the Applecare phone opp was more then likely missguided, Im sure apple will continue to support file sharing via SMB, i mean how could they expect to function in a corprate enviornment otherwise. I was really trying to partner with applecare for the means of escalating the issue to egenearing but i feel i was stonewalled. In the past i have had success when apple escalates such issues to a level beyond simple helpdesk tasks. Perhaps i will call and see if i have more success with another phone aganet.

thanks again

Reply