this was the method I initially used. However, it didn't work properly. the first problem was that it would see the shares but wouldn't mount them. the second problem was that attempting to mount would result in an error (cannot mount, authentication error. this problem was caused by the session not providing an authicantation window.
trying this method under snow leopard seemed to work properly. Unfortunately, my mac no longer has snow leopard on it. rolling back to the previous OS has problems of its own and I am not willing to go through those hassles at this time. -eric On Oct 29, 2012, at 3:46 PM, Tim Kilburn wrote: > Hi, > > I'm not sure what's broken for you. To connect to an SMB Server, do the > following: > > 1. Go to the Finder. > 2. Press cmd-k or up to the Go menu and choose Connect to Server. > 3. Enter smb://Server_Name.domain.com > > If DNS is set up properly, which I expect it is at a University, you > shouldn't actually need to put the .domain.com at the end, just the > smb://Server_Name. You can substitute the Server_Name with an IP address if > DNS still doesn't allow you to connect. > > 4. Press return. > 5. Enter your username and password, press return. > 6. Select the volume you wish to mount. > > You're done. I just checked this at school here on our Windows server and > had no problem connecting using smb. > > Good luck. > > Later... > > Tim Kilburn > Fort McMurray, AB Canada > > On 2012-10-29, at 3:56 PM, Eric Oyen <[email protected]> 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 [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
