Windows 2000 Server and Professional, latest OS patches.
I have one user who has lost the ability to do anything with any of the files he has access to other than to list thenm and read them. He cqannot write to them, he cannot copy the files, etc.
I have checked the permissions for the directories involved, and tey have not changed. I gave him explicit rights to the directories giving him Full Control. I have deleted him from Active Directory Users and removed his local profile, then recreated the user.
I have cursed. I have sworn. Nothing seems to be working.
If I log in as another user, there is no problems. Only if I log in as this user. Interestingly enough, I cannot log into another machine with this user's credentials, but I can log into his machine with other users' credentials.
This user was fine on Monday. He was able to manipulate the files he needed to manipulate. Tuesday was moving day, and his office was moved to another location. Today, he logs in and cannot do what he needs to do.
Yes, he is connected to the network. Yes, he is logged into the domain.
Can anyone give me a clue as to how to proceed in this case?
Steve//
Software/Hardware used:
ASKED:
October 5, 2005 4:43 PM
UPDATED:
October 11, 2005 12:26 PM
It may also be a corrupt profile on the local machine causing this. Try creating a new local profile and see what happens.
It might have something to do with his computer name. Check Active Directory for Users and Computers. Look at his computer name and check his permissions there. Besides that I would probably just change his username, add an initial to it or something. Sorry not much help.
Gutzy63,
I knew there was another thing I could try, and removing his machine from the domain was it! I haven’t done that yet, but will e-mail the techs available tomorrow and have them do it. Yesterday was a day of sticky problems, and this machine was just one of them–my brain was pretty well fried by the end of the day.
Steve//
Juscelino,
Already tried the new profiles, both local and network. Was no go. I did not try Gutszy63′s suggestion yet, and I should of thought of that.
Steve//
Sheldonrw,
I don’t think the computer name would be the problem. The machine has been in place for a while, and it has been about a year since it was rebuilt. The problem just developed. I would think that if it was a computer name issue, it would have developed pretty much immediately.
It is in the back of my mind to rebuild again, but this guy uses a number of specialty programs, several of them older than Windows (even prior to even hearing about Windows) and it can be a pain to get them to work under WIN2K (I don’t even want to think about XP).
Thanks for the suggestion, though.
Hey Steve, Thanks for your reply and please let me know how you resoved your problem. Interested in finding out what worked for you. Hope that you don’t have to rebuild it.
Sheldon