VB6 and .Net running slow on only one computer

[Twodogs]

Hi all,
I have a very strange problem - we have a number of vb6 and vb.net applications that have been written in house. These are used by a number of users with no problems, however one user is experiencing extremely slow response from all our vb6 and .net applications.

So far, we have:
a. plugged another computer with the same configuration into his network port - great response.
b. run the same sql stored procs through SQL Advantage (like sql server manager) - great response, even when returning > 1mb of records
c. run "winstress" to check that his memory wasn't corrupt (or used by "midnight spares") - no problems (1gb RAM)
d. defragged his hard drive - no difference
e. had the user sign on to a different machine - great response
f. checked running processes to see if he has something running that he shouldn't - no difference between his and my machine.
g. checked the network topology - both his and my machine are computer->switch->firewall->switch->switch->server
h. checked other (MS) applications that go to the server - great response

No other user is experiencing these problems - does anyone have any ideas what it could be?

[dglienna]

Is the Indexing Service slowing things down?

[Twodogs]

good question - checking now

[Twodogs]

Indexing service is turned off but the problem still exists.
We're about to re-image the PC with one (exact same configuration) that actually works. Our suspicion is that the user has installed / reconfigured something - any ideas will still be greatfully received.

[PeejAvery]

You're first stop should be Task Manager to see to see what processes are involved in the slow take down. From there, you would want a process investigator to see what part of the processes are being tied down.

[Twodogs]

That was what I did yesterday (I guess I should've mentioned that...) I found two possibilities, WUAUCLT.exe and SYSTEM - googling both of them showed that while both are valid files, there are two trojans which imitate (overwrite) the original files.

Currently, we have re-imaged an identical machine, which is running fine. We are going to re-image the 'rogue' machine tomorrow and see what happens, which *should* eliminate any hardware/network fault.

I'll keep you posted - but please, keep coming up with suggestions.

[moa]

Hello,

I would check for the possible presence of KOGOR ...
We never know ...

[Luthv]

try this utility from sysinternals

http://www.microsoft.com/technet/sys.../autoruns.mspx

it should show all autostart entry points for applications or components.

[PeejAvery]

WUAUCLT.exe is for Automatic updates. Go to Internet Explorer and under the Tools menu, choose Windows Updates. Patch up the machine entirely.