Copy command logs user off pc?

[Guest jrrieger]

I was wondering if anyone has some advise or experience with this issue. For around the last 6 months I have been having a problem with users getting logged completely out of windows when they issue a copy command, either by ctrl C or right click -> copy. We are basically a NT4 shop but I have had the problem on our 2k machines as well. I am completely dumbfounded. Its such a basic function of windows, I cant really troubleshoot this. HELP !

[Guest ellas]

I cannot help but I will bump it up so maybe someone else can,did get one link for you but have no idea if its any good for you :D http://support.microsoft.com/default.aspx?...kb;en-us;174273

[bvw]

The Yaha worm can swap left and right click functions about. Other than that I've no idea. <_>

[Guest Nellie2]

Bumping this back up to the top.......... can anyone help with this problem??

[Agent Smith]

Bear with us jrrieger, I am going to ask someone who knows a lot more about NT than I do. It may not be until monday though.

Regards. Mr. Mouse.

[Agent Smith]

Hi again jrrieger, right I've spoken to someone at work, and he is a bit stumped with this one as well. The problem being not having a machine in front of us that is doing the problem.

A couple of questions for you. When you say the users are logged out, do they actually get logged out all the way, or does the act of copying just bring up the "log out" dialog box, at which point this can be canceled. Is it happening to all users, and on all machines. What sort of network configuration are you using? ie peer to peer, connected to a server, a domain, active directory, any stand alone machines (and are they affected), any internet connection etc.

It is our obvious belief that something has hijacked the key sequence for copying and reassigned it to a log out sequence.

My friends immediate thoughts are that one of the following has occurred.

1. (Most likely) An upset member of staff, now probably an ex member of staff, with a knowledge of windows, has sabotaged your machines as either a practical joke or an act of revenge. If this is so, it will probably involve a fair bit of registry editing to solve.

2. (Possible) You have picked up a virus. Whilst we are unable to find any details about a virus which does this, it is possible. Do you have AV software installed, and are the definitions kept up to date. I would hope that you can work out what to do, if this is the problem.

3. (Possible) Assuming you machines are networked, can you unplug one from the network and log in, you may need administrator rights or to change some policy settings before disconnecting to do this. Once logged in to the desktop, does the same fault occur when you try to copy? Please post back with info regarding this one.

4. (Unlikely) Some software has become corrupted and affected the copy command. This would become apparent if you had similar events when using a certain piece of software. We feel this is unlikely, due to the fact that you have the problem on more than one machine, unless you are running any server based software (ie the application resides on and is run from a workstation via the server).

I hope this has given you something to start with, but perhaps you could post back with some more information. Any relevant information will help, and even if the info seems trivial or unconnected, it may be relevant when put into a different context, so don't worry about posting something which seems to be silly!

Good luck. Regards. Mr. Mouse.