Can not edit file on network shared folder after upgrading to windows 7

Question

Merry Christmas and happy new year,
Due to some configuration changes on a specific application, I have forced to upgrade OS of a few number of workstations from Windows XP to windows 7. After upgrading I am facing a strange problem on WIN7 workstations. These workstation are member of a Windows
2008 R2 Active Directory domain which also has a Windows 2003 advanced server additional domain controller. Also there are a number of shared folders on some member servers (all windows 2003) which are mapped as network drives at user logon. Before upgrading
mentioned workstations to WIN7, users was able to edit his/her files on all of mapped network drive according to his/her permissions without any problem on their WINXP workstations, But after installing windows 7 they begin facing problem on one of these mapped
network drives and the problem exactly is when they edit a file, in more specific word an excel file, and then try to save, the excel returns an error message of "document not saved" and exit the excel program. It becomes more strange when you learn
that the edited excel file is disappeared and replace with some "tmp" file. If user copy the excel file to his/her own desktop, edit it and then copy it back to its original place on mapped network drive, it will be replaced normally with its older
version. In other words if user wants to edit an excel file on that specific network drive, he/she must edits it somewhere else and then replace it on the network drive. If the same user uses a WINXP box, there will be no problem.
Can anybody help me to fix the issue?
TIA
Bijan

Answer 1

Thank you Karen,
The problem is fixed, but my case was none of what you suggested. In fact I have
another problem which I described in another question and it was of the root of this excel file issue. I describe what I have done to fix the latter problem hope to help fixing similar issues to mine.
Okay, as it is described in the
question, I was not able to open a shared folder with its UNC address while it could be mapped as a network drive without any problem. I examined what I was replied and some other ways, came to no result. I decided investigate a similar shared folder in
permissions to problematic one to see if the problem is repeated. So I created a folder and shared it with similar permissions and examined it. Surprisingly there was no problem. It was wise to remove sharing of the problematic folder and share it again to
see if the problem resist. But when I tried to remove sharing I received an error message saying that
the shared folder is related to a DFS root. When I took a look at the DFS roots of domain there was no sign of the problematic folder (that made me recall that I created a DFS root with problematic folder mistakenly and removed that DFS root).
After little searching, I found out that the problem could be caused by traces of the removed DFS root. Yep! I found the suspect! The registry key
HKLM\Software\Microsoft\DFS\Domain\problematic shared folder. I removed the key restarted DFS service and log off and on and Bingo!
This problem pops up a few more questions:
1) Why is not the registry key related to removed DFS root deleted from the registry of windows 2003 server?
2) Why was I able to browse this ex-DFS root shared folder without any problem in windows XP while it was problematic in windows 7?
3) As there is no special client service for DFS and user can access DFS root targets like other shared folders what is the deference between shared resource access mechanisms in windows XP and windows 7 that caused the problem?
Bests,
Bijan