Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Just Joined
  • Content count

  • Joined

  • Last visited

About deckeda

  • Rank
    InsanelyMac Protégé
  1. Notes on what you'll see/what I saw when working properly regarding the "multiple, ghost shares" anomaly mentioned earlier. 1. Prior to running Time Machine and after, nothing additional shows in /Volumes. This is consistent with any unmounted volume—they shouldn't appear as broken aliases there unless /Volumes/private/var/db/volinfo.database is corrupt. A logout usually cleans up the volinfo.database file. 2. While Time Machine is backing up, both sharevolume and sharevolume-1 appear in /Volumes 3. The .tmp sparsebundle mentioned previously won't be generated. That was a symptom of incorrect setup. 4. While waiting to run again, Time Machine's interface (i.e. in System Prefs) shows that it's gonna use sharename-1. Don't worry. Once it runs, it's using sharename now.
  2. It seems to now be working. The sparsebundle volume appeared on the desktop and is now backing up to it. I was connecting with smb://IP/username What I should have done is use smb://IP/sharename Windows Sharing is turned on too on the 10.4 Mac. Unlike yesterday, today the 10.4 Mac now appeared "as a PC" (generic PC icon) from the 10.6 Finder window's sidebar SHARED list, in addition to listed as normally (as a shared Mac.) Connecting from the PC icon starting point gave me access to the server from "an SMB point of view," and so the available volume had the 10.4 server's shared SMB name, not the Finder shared name. In fact that's how I connected at first, i.e. NOT via Cmd-K, inputting "smb:// …" etc. But another 10.6 wouldn't permit that because it never showed up in the sidebar. Bottom line, use the Connect to Server dialog and smb://IP/sharename or smb://servername/sharename
  3. OK, resolved the issue of the network drive mounting with AFP; I had been connecting via a Finder window instead of Cmd-K and entering the smb:// IP address. Otherwise I still have the same issue as mentioned above.
  4. I *think* this is the only post that mentions a Tiger server actually working, as opposed to supposedly working? Can't get it to work here for a 10.4.9 Mac serving a 10.6.2 client. I have SharePoints on the Tiger Mac; even sharing the desired network drive as SMB still shows it connected and mounted via AFP when viewed from the 10.6 client. I have no clue what's going on there but will look into that more. TM fails trying to "make available" or "preparing" the network disk with an error regarding a −1 copy of the network share. The .tmp sparsebundle mentioned before is also made during this process and then deletes. Before and after, adding the .plist file with UUID as shown in System Profiler produces the same result.