Suzanne
Yes it may just be SMB signing but it is particular to Word XP and Windows
2000 Server SP2 (not SP1 as the post suggests). However, a strong clue to
SMB bug is that the temp files remain in the source folder until the user
logs off the domain. It isn't necessary for the user to close the
Workstation, just logging off is sufficient to unlock the locking files.
Terry
If your folder permissions are in order (see Terry's post), then that's not
the problem. ISTR that the answer to this has been found, and I have a vague
idea it's related to SMB packet signing, but I'm afraid I don't remember
what the solution is. A Google search turned up this post by Tim Daly in
this NG last April:
For many months I suffered with slow network file
retrieval in Office XP applications. It would sometimes
take up to sixty seconds to open a file or the
application would crash and then generate a temporary
file making the same file read only when the user tried
to open it again. After much research I found that these
symptoms were only occurring on machines with Windows XP
Pro with service pack one installed, and the files that
were acting up were stored on a Windows 2000 server.
The root of this problem seemed to be SMB packet signing,
which Microsoft admits is a known incompatibility between
Windows XP SP1 and Windows 2000 server in Knowledge Base
Article - 810907. The problem is there really wasn't a
fix to deal with this intermittent problem, although the
files didn't hang or crash every single time, it was
common enough to drive my users crazy and create a
support nightmare for myself. I started monitoring
several machines and noticed that an "application hang"
event 1001 would be generated in their event viewer every
time the symptoms would occur. Microsoft said there
would be a fix in the next service pack but it would be
impossible to wait for whenever that would be, I was
planning to upgrade some 1000 computers to the same
configuration and couldn't fathom dealing with these same
problems campus wide. So, I went back to the research
and finally found an article that saved the day:
http://asia.cnet.com/itmanager/netadmin/0,39006400,3910828
1,00.htm
This article provides a simple fix to a giant headache by
just altering some group policy objects on the domain
controllers. After monitoring several machines for a
month, the problem is completely resolved. It is beyond
my comprehension why Microsoft would not publish this
simple fix affecting their flagship product. End users
are always apposed to change and when performance
degrades with new software and updates, their apposition
is somewhat justified. If Microsoft wants IT managers to
migrate to their new products they better come up with a
better system for informing us of these problems, as you
will see in the above article this fix was found by an IT
manager who struggled for months as I did and then passed
on his good fortune once he found a fix; I am trying to
save other people the same headaches by doing the same.
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site:
http://www.mvps.org/word
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.
