Cannot copy in Windows Explorer

[Antony13]

Hi all,

We're running a Windows 2000 Terminal Server built from scratch and have a problem where, when you try to cut and paste or copy a file within Windows Explorer, it does not copy - no error messages, just nothing happens at all. There is one user who can do this so I thought that it has to be something to do with his profile or local user registry entries which is causing the problem.

It's not admin rights as not even the local administrator can do the above. We've copied his profile to another user's profile to replace it and this has not worked. We've exported the user's local user registry hive and imported on another user and this hasn't worked.

One thing that did happen was a load of the VB references in MS Access were pointing to this one user's home drive which was causing other problems (e.g. VB scripts not running properly for other users) but I have now reset these all back to the local C: drive and the copy function still does not work except for this one user.

You can copy within a DOS session though, so I'm guessing the one user must have access to some DLL or something that the others don't and this is why it works for him and not anyone else. Does anyone know which DLL is involved in the Windows Explorer copy and paste process?

Any help / suggestions (other than rebuilding the machine!) would be much appreciated.

Cheers, Antony

 

[Antony13]

Just as an update to this, we reckon this is a result of the Blaster worm as there seems to be a lot of people with this problem as a result of the worm on other discussion groups at the moment.

Unlike others though, this was caused by massive changes in the registry (especially under HKEY_CLASSES_ROOT) where loads of DLLs have been referenced as being under P:\WINDOWS\*****.dll rather than C:\WINNT\system32\*****.dll. The one guy who could copy and paste had all of the relevant system files on his personal drive (i.e. under P:\WINDOWS). Whether it was him logged on when the virus hit and it did this or something else entirely, we don't know, but looks like the long term fix is to rebuild the server (DOH!).

Hope this info helps people.

Cheers, Antony