Right, on XP, I have never seen this happen on our DFS shares. It's only my Vistamachine, and even on this machine/build, it used to work right. My users work primarily out of our DFS shares - and knowing them, I would hear about it since I doubt they grasp the idea of 'Refresh' or F5 ;)
-----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 3:21 PM To: NT System Admin Issues Subject: Re: Manual Refresh required on Network Shares On Wed, May 21, 2008 at 12:07 PM, Sam Cayze <[EMAIL PROTECTED]> wrote: > I think I saw this once on XP, but now it is happening on my Vista > machine, when working in Network Shares in a 2003 Domain (DFS Shares > only seem to be affected. Other shares, like \\name\c$ work fine) I thought that was the expected behavior. Any time I've set-up a DFS tree, it has behaved that way. Specifically, any changes to a folder's contents that happen after Explorer first reads the directory are not noticed automatically. You have to manually refresh. That includes creating folders and files, moves, copies, deletes, etc. It's like Explore isn't getting the filesystem change notification messages. I always figured it was just a bug/limitation with DFS. Are you saying you've actually seen it work *right* before? :-) -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
