M
Michael Thornton
We are rolling out Windows 2000 sp4 to all of our clients (upgrading from
WinNT via a ghost image) however we are having an issue with one particular
office location.
At this particular office, the users are having intermittent problems saving
to the loacl file server (W2K sp4) with the new image on their pc. They
authenticate locally to a DC in the office there (again, W2K sp4) when they
log in. When they try to save a file to the file server thru Wordperfect
(version 8 - unfortunately our word processor of choice), it fails and the
error message says "Access denied: you do not have permission to do this."
If they wait an hour it will work...sometimes...sometiomes not.
These things I know:
1. The NT images never had the problem.
2. If they try to save to another file server (same specs) in a remote
location it never fails.
3. If a user at a remote location using the new image tries to save to the
suspect file server it works fine.
4. None of our other locations (same specs and images all over) have had
this problem.
5. The ghosted W2K image is standard across the board.
6. We have checked and double checked acl's and permissions.
7. We are using AD (2000).
Any thoughts on this would be appreciated...I am sorry if I have not
provided more in depth specs....please let me know if that would help and
what you need..
WinNT via a ghost image) however we are having an issue with one particular
office location.
At this particular office, the users are having intermittent problems saving
to the loacl file server (W2K sp4) with the new image on their pc. They
authenticate locally to a DC in the office there (again, W2K sp4) when they
log in. When they try to save a file to the file server thru Wordperfect
(version 8 - unfortunately our word processor of choice), it fails and the
error message says "Access denied: you do not have permission to do this."
If they wait an hour it will work...sometimes...sometiomes not.
These things I know:
1. The NT images never had the problem.
2. If they try to save to another file server (same specs) in a remote
location it never fails.
3. If a user at a remote location using the new image tries to save to the
suspect file server it works fine.
4. None of our other locations (same specs and images all over) have had
this problem.
5. The ghosted W2K image is standard across the board.
6. We have checked and double checked acl's and permissions.
7. We are using AD (2000).
Any thoughts on this would be appreciated...I am sorry if I have not
provided more in depth specs....please let me know if that would help and
what you need..