I'm having some issues w/ a client's server lately. Running SBS2003 w/ SP2 and all updates. Workstations are all XP Pro SP2 w/ all the updates.
I recently had to install a new HDD in one of their workstations and then reload XP. Now I'm seeing issues on the domain controller that the CPU usage is almost 100% all the time when this machine is plugged into the network and turned on.
The lsass.exe and dfssvc.exe processes are using up all the cpu cycles on the domain controller. I went through a bunch of troubleshooting on the M$ site and narrowed it down to the fact that something is wrong w/ the workstation. When I examine the processes running on the workstation, I see wscript.exe using about 10-15% of the cpu usage all the time. As soon as I kill that process on the workstation, the CPU usage on the server goes back down to normal.
So, I disabled the user's logon script and I still have the same issue. I went through msconfig/regedit on the workstation to see if there are any .vbs scripts running at startup. There were none.
If I log into the workstation locally instead of to the domain, the problem does not happen.
It almost seems that whatever is invoking that wscript.exe to run at logon is having issues finishing execution. Not sure if its waiting for a timeout or if there is an error causing it not to finish execution.
Any ideas on where to look would be helpful.
I recently had to install a new HDD in one of their workstations and then reload XP. Now I'm seeing issues on the domain controller that the CPU usage is almost 100% all the time when this machine is plugged into the network and turned on.
The lsass.exe and dfssvc.exe processes are using up all the cpu cycles on the domain controller. I went through a bunch of troubleshooting on the M$ site and narrowed it down to the fact that something is wrong w/ the workstation. When I examine the processes running on the workstation, I see wscript.exe using about 10-15% of the cpu usage all the time. As soon as I kill that process on the workstation, the CPU usage on the server goes back down to normal.
So, I disabled the user's logon script and I still have the same issue. I went through msconfig/regedit on the workstation to see if there are any .vbs scripts running at startup. There were none.
If I log into the workstation locally instead of to the domain, the problem does not happen.
It almost seems that whatever is invoking that wscript.exe to run at logon is having issues finishing execution. Not sure if its waiting for a timeout or if there is an error causing it not to finish execution.
Any ideas on where to look would be helpful.
