Hi, I've tested this again today with a less privileged user. As long as the user has, minimum, Read permissions to the SharePoint, then everything works as it should both in Lion and Mountain Lion. If the user does not have proper permissions to the SharePoint, then the errors you mentioned may appear.
You can try to connect by using a more full path approach such as: smb://Server_Name.MyDomain.com/SharePoint/MyFolderName Problems may still arise though if the permissions are not set correctly to the parent SharePoint. So, it doesn't appear to be a problem with smb in Lion or Mountain Lion. It looks to me that it is a permission issue at the Server end. What needs to happen is that you, or most likely, the Group you belong to should have Read privileges within the Security pane of the SharePoint. Because it is Windows, there is also another level of security at the Share itself, I usually allow the specific Group to have Change privileges there as the Security pane is the major factor in controlling access. HTH. Later... Tim Kilburn Fort McMurray, AB Canada On 2012-10-30, at 12:00 PM, Chris Blouch <cblo...@aol.com> wrote: > I guess I'm not clear on what the problem is. I'm on OSX 10.7.5 and to > connect to a windows share I just do command-K to connect to a server and > then use the smb://servername.blah.com/folder/path nomenclature to connect to > where I want to go. It prompts for my name and password and then the drive > appears on my desktop just like any other. Is this not the case for you? > > CB > > On 10/29/12 5:56 PM, Eric Oyen wrote: >> hey guys, >> >> has anyone found a work around to connecting to windows shares from a OS X >> Lion client. I seriously need to be able to do this so that I can save >> documents to my user account at school. otherwise, its a pain in the a$$ to >> have to find the files, place them on a usb stick, unmount it, move it to >> the school windows machine and then copy it to my account drive. >> >> I have tried to find information on this via a google search. so far, none >> of the solutions are workable here (one app available is not voiceover >> usable at all and the other solutions are either unworkable or unsupported). >> anyone have any usable solutions that do not involve having to hack the >> system files? >> >> -eric >> > > -- > ¯\_(ツ)_/¯ > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionaries@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
