Mac OS X 10.3.5 (#22): File Sharing quirks; solutions and workarounds

Entering server names manually We previously noted that entering the desired server's IP address in the "Connect to Server" window usually allows access to machines that do not show up in Network Browse mode. MacFixIt reader John notes that, in some cases, simply entering the desired machine's name allows connection:

"An alternative, though, to entering the IP address of the target computer in the 'Connect To Server' window is to enter the target computer's name, as specified in the Sharing preference panel. This is much more convenient than the actual IP address, especially for those who network their computers via DHCP routers like an Airport base station. Computers that get their IP addresses via DHCP are not guaranteed to receive the same IP address over and over again. But the computer's name doesn't change (unless you change it)."

Non-booting volumes and permissions We also previously noted a problem where sharing issue where non-boot volumes do not show up when connecting to the Mac sharing those volumes, and that restarting file sharing services sometimes resolves this issue.

MacFixIt reader Simon Craig now reports a separate issue, where non-booting volumes on a server are not accessible with administrator privileges:

"I have 2 macs in the house, networked via Airport and have had this set up using various forms of OS X for years. One of the macs has a Firewire non-booting drive connected to it and I have been successfully using this as a network volume for all this time - simply by logging on to the Mac with the Firewire drive as the administrator on that mac (the only user account set up).

"Recently (since 10.3.5 or later security updates, I'm not sure which) I have been able to mount the drive as before (never had an issue with it not being visible) but when I log on as the admin on the first mac I no longer have read and write access to this Firewire drive. The drive permissions do not recognize that I have logged on as the admin, and restrict me to read access only - despite me logging in as the only user on the Mac.

"Multiple re-starts and File-sharing stop-starts on both machines have failed to cure this very recent problem. Having 'ignore ownership on this volume' checked also does not seem to affect this.

A simple workaround is to allow everyone read/write access to the desired volume (accomplished by selecting the disk in the Finder, accessing the File > Get Info Menu, and changing the values in the "Ownership and Permissions" section), but this will obviously also ruin any security measures put in place to block access for outside network users.

If you are experiencing a similar issue, please drop us a line at late-breakers@macfixit.com.

Patience is key Meanwhile, a number of users note that Network Browse can sometimes be frustratingly slow -- requiring up to 60 seconds to display available volumes on the network.

Rob White writes "I've noticed that, if you try to browse the network to find Windows shares in our environment that patience is the key-if you simply click on "Browse", wait for up to 60 seconds (!), then click on the server icon and wait another up to sixty seconds (!) that, like magic, the share icons to connect will pop up like little mushrooms and you can connect.

Derek Rawson adds "I think that the Network Browser just takes time to see network devices. We're used to this being instantaneous in the Chooser with OS 9, but with both the OS 9 Network Browser and the OS X Network Browser (with 10.3 built into the Finder) there is a delay in finding networked machines and also printers when trying to add them in Print Setup. If you're impatient it can seem like it's not working."

Resources