File access issue
Got a strange one here. Over the last two days we have had some file access problems.
In one instance, a user could navigate to a word doc on the network through explorer, double click it and open it in word, but if he opened word first, then tried to navigate to the file within word, he could not see the file. It doesn't even work if you navigate (within word) to the directory then type in the file name in the File Name box. It just doesn't recognize that the file is there.
In another instance we have a file that is generated daily called output.txt. THis file is then ftp'd to another location. Except now, when you ftp the file, you get the previous days data. There is only one output.txt file in the directory and if you open that file, you see today's data, but after you ftp it and open it on the other end of the ftp, the data inside the file is old.
To get around these issues, we can rename the file or make a copy of the file in the same directory, then name it back to the original name or delete the copy and it seems to clear up the problem for the day.
Anybody have a clue?? We are going to bounce the box today, but would like to know what is causing the problem.
The server is Windows 2000 Server SP3
The clients are Windows 2000 Pro SP3
In one instance, a user could navigate to a word doc on the network through explorer, double click it and open it in word, but if he opened word first, then tried to navigate to the file within word, he could not see the file. It doesn't even work if you navigate (within word) to the directory then type in the file name in the File Name box. It just doesn't recognize that the file is there.
In another instance we have a file that is generated daily called output.txt. THis file is then ftp'd to another location. Except now, when you ftp the file, you get the previous days data. There is only one output.txt file in the directory and if you open that file, you see today's data, but after you ftp it and open it on the other end of the ftp, the data inside the file is old.
To get around these issues, we can rename the file or make a copy of the file in the same directory, then name it back to the original name or delete the copy and it seems to clear up the problem for the day.
Anybody have a clue?? We are going to bounce the box today, but would like to know what is causing the problem.
The server is Windows 2000 Server SP3
The clients are Windows 2000 Pro SP3
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.