Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.3: Delete cached files to solve Windows networking issues Apps
I was having trouble with browsing and accessing certain directories and volumes on my work network after upgrading to Panther. I found that there were a few files (cached?) in /private/var/automount/Network/. After deleting these files, the problems went away and my Windows networking returned to normal.
    •    
  • Currently 2.50 / 5
  You rated: 1 / 5 (8 votes cast)
 
[19,240 views]  

10.3: Delete cached files to solve Windows networking issues | 10 comments | Create New Account
Click here to return to the '10.3: Delete cached files to solve Windows networking issues' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: Delete cached files to solve Windows networking issues
Authored by: MrToto on Jan 28, '04 12:26:35PM
Yes, I noticed this too, while trying to make a Carbon Cpoy Cloner copy of my HDD to a Firewire HDD. I wrote a little bit about this in my blog: (http://bitfever.blogger.de) This does see to bee a network cache if you are offline, but when you are connected to that network (no need to mount anything) it seems the directorys under /private/var/automount/Network lead to the network! Because auf this CCC tried to copy my whole 97GB Windows Drive onto the Firewire disk.

[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: DevNine on Jan 29, '04 07:06:11AM

I hope this works for me as I've been having some weird problems with Panther's samba of late.

---
http://www.dinneen.com/wirelessapple
http://www.corkwireless.com



[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: SSUJoe on Jan 28, '04 01:36:16PM

Please excuse my ignorance, but how can I view those directories? Are they hidden?



[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: Safar on Jan 28, '04 02:31:20PM

you can use the Finder menu "go..." and then choose "go to folder", then type the name of the folder



[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: bipto on Jan 28, '04 02:34:15PM

Or you can do it that way, too! ;)



[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: bipto on Jan 28, '04 02:32:38PM
Yeah, they're hidden. Just go get TinkerTool. Under Finder Options, choose 'Show hidden and system files', then relauch the finder using the button. Afterwards, you can turn off that option and relaunch the finder agian.

[ Reply to This | # ]
Contribute to Apple's Discussion thread to get this issue solved!
Authored by: aroubini on Jan 28, '04 01:48:16PM

If you go to Apple's discussion forum, and see what some people have been saying about Panther's Networking you'll discover that many people are infuriated by their half-finished or de-evolving solution to a networked environment. Go to: "Home - Mac OS X - Mac OS X v10.2 - Using Technologies - Networking and the Web - Networking is awful in 10.3 (Panther)" and put your 2 cents in to get this thing fixed in the next update. I love the rest of the work they do but this is a calamity.



[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: ahunter on Feb 01, '04 01:49:16PM

I've noticed this. This location is where the directories are actually mounted: so make sure that they are unmounted before deleting anything.

The problems are caused by the Finder fighting the automounter: when a server goes down, its shares are unmounted. But the finder doesn't notice this for a while, and can display the server as mounted but with no files... and then it creates a .DS_Store file in the now local directory. When the server comes back up again, the automounter notices the .DS_Store file and fails to mount the server, assuming the directory is now in use for something else.

Solution? Delete the .DS_Store files. Or just delete the whole directory. It seems sometimes you'll need to kick the automounter (killall -HUP automount), or the Finder (relaunch it using command-option-escape), or both. I suspect the problem doesn't happen if the remote servers remain up, which may be how it slipped through Apple QA.



[ Reply to This | # ]
10.3: Delete cached files to solve Windows networking issues
Authored by: osxfan57 on Mar 26, '04 10:08:26PM

Followed these suggestions. No dice. Still the shared Windows resources don't show up in the Network pane of the Finder. They do show up in the automount/Network folder using Terminal. I can also connect to them without any problem using command-K in the Finder. So what the heck is it with Apple's claim that networking is easier?? Where is the fix to make shared drives show up in the Finder?

---
iMac 17, OS 10.3



[ Reply to This | # ]
10.2.8--10.3.3 clash (related problem?)
Authored by: stmilne on May 17, '04 08:58:04PM

Forgive the newbie post; my question seems related to ths thread, so here goes.

I am having a problem with Mac OS X 10.2.8 (iMac) coexisting with 10.3.3 (TiBook) on the same (two-computer) Airport network. The iMac disk has two partitions, "A" (OS X partition) and "B" (OS 9 partition). Both are HFS+.

It seems that after I mounted "B" on the TiBook recently, and then ejected it after I was done, "B" was no longer visible on the iMac desktop, nor did it appear in Finder windows, Open dialogs, etc. [Heart stops momentarily.]

But "B" (and all its files) is still there, visible in /Volumes with ls from the terminal. Also, it can be seen by Disk Utility, which can mount and unmount it with no effect on its visibility. "B" is also visible to XRay. Oddly, its owner/group is now not "system/admin" but the user currently logged in. And, "B" is still visible to the TiBook, and can be mounted.

Restarting the iMac had no effect, nor did "repair" under Disk Utility. I also tried deleting the .DS_Store file in /Volumes, likewise to no effect.

How can I fix this (without backing up the entire machine and reformatting the disk, that is)? And how can I keep this from happening again?



[ Reply to This | # ]