|
|
why do you need sharity?
Hi ,
why do you need sharity?
Because you cannot just use smb://server, you have to indicate the share explicitely like smb://server/share. In my working environment we have 20+ Windows NT/2000 servers and each one has a whole bunch of shares. Without using Sharity I have to go to one of the Windows machine to check which resource I am going to connect because I can't remember all of them. Well of course that's not a problem for those who has only one Windows server and a few shares. :-)
why do you need sharity?
Thank you. That is the single most useful thing I've read since installing Mac OSX.1. I've been trying to figure out how to do windows shares since then, and it turns out all I needed was the actual share name as well as the machine name.
why do you need sharity?
Based on my reading through newsgroups, macslash, this site, and certainly from my own experience over the past week, it seems that OSX.1's SMB mounting facilities (from Connect to Server or using mount_smbfs and/or smbutil from the command line, and even after adding the remote machine's hostname to NetInfo per Apple Knowledge Base article 88158), work only for some networks and under some situations. Exactly what circumstances it works under I haven't yet determined, but I know that my linux-hosted SMB share is a dirt simple, no-password-required share, and that OSX.1 absolutely refuses to see it under any circumstances (Win machines on the same network see it fine). |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.17 seconds |
|