I have a strange problem on a users machine that I can't correct.

We had to rebuild a users machine last week due to a hardware failure.

When we installed Visual Studio 6 w/SP5 and ran it locally it ran fine.
However, whenever we login to the network or as the user the Windows
Installer wants to run and just hangs there. If you quit the Windows
Installer the application quits or errors out. I've tested to see if it's
trying to go back to our installation share as some MS apps are prone to do
by logging on as myself to see if it was a share permissions issue, but I
have the same result.

I've checked all of the search pages and cannot find any information about
this problem. I sent in an error report and got back a message that VS SP6
was available so I tried that too and it didn't work.

When I check Task Manager VB6.EXE is always hung or stops responding and
doesn't close itself out when I quit the app. I have to manually remove it
from the processes list.

I thought it might be a system problem, so I swapped out the users machine
with a brand new one, manually reloaded all of the apps and still have the
same issue so I know it isn't the build.

Are we running into Legacy issues on Windows XP? Is this a known problem and
is there a fix other than upgrading to .NET?

Again, this only happens when you are logged into the Domain. I can run VB6
all day locally.

This machine is not running Windows XP SP2.

Anyone have any ideas?