DFS

  • Thread starter Thread starter Steven Colligan
  • Start date Start date
S

Steven Colligan

Hi,

I'm currently looking into using DFS to advertise a single entry point for
the home drives for our students and also using a GPO to re-direct users
data to their home drive.

The problem that I am having is that when a user creates a document on say
their desktop, just by right clicking and selecting new text document, the
icon for the file does not appear until the F5 key is pressed.

I have seen other postings with similar problems but never a solution -
these postings were almost a year ago.

OS is Windows 2000 Server and Professional, with service pack 4.

Has anybody a solution to this problem?

Regards,

Steve Colligan.
Senior Information Specialist.
University of Abertay Dundee.
 
I haven't seen that specific issue, but I have seen another strange
issue with DFS. When our XP users go to edit a file on the DFS share,
it opens up the wk9blah.tmp file in the same directory as the file.
When they go to save it, it causes a delayed write failed error. I
thought that temp files were supposed to save to the local %temp%
variable directory, but this doesn't seem to be the case. I saw the
MS-KB article saying to disable write caching on the drive, but that's
ridiculous. Write caching worked before, and we just applied all of
the latest patches, and it stopped working giving us about 150
machines who can't save to DFS period -- unless I disable write
caching. Even then, they still get the error, just not as often. All
of them have DMA capable hard drives which are set correctly in the
bios. Only after forcing the windowsupdates on the machines did they
have the problem. The DFS root is on a w2k active directory domain
controller. The actual volumes mounted are all on separate member
servers (w2k). Like I said, the only ones having this trouble are XP
clients. We are 100% AD integrated, and were working great until
three weeks ago, when we hit the whole host of patches that just came
out.

Now we have 150 machines whose event logs verge on full with delayed
write failed messages... Something's amiss...

--d
 
Back
Top