Buy Microsoft Office Home & Student
Windows XP: Windows XP Clients Slow when launching applications
Windows XP Clients Slow when launching applications
by funhouse69 - 12/6/07 5:07 AMHi everyone I have an interesting one for you... I have several XP Pro machines on my network with 2 Windows 2003 Server Domain Controllers. I recently replaced one of my Domain Controllers cleanly by removing the old one using DCpromo, all roles were transferred over to one of the other DC's without a problem.
Since then I can log in to my XP Pro clients without an issue but when I try to launch any application on the system it will hang for upwards of 2 minutes before it launches the application.
I have checked all of the event viewers and for a while I was getting a 1054 error which is group policy not being applied but that has now been resolved. I check the domain controllers and don't see any out of the ordinary issues. I verified the networking is set up properly with the proper DNS Settings etc.
I have also tried to remove the system from the Domain and Rejoin it which I can do no problem but still have the same issue when I try to launch an application.
There has to be a simple fix for this but I haven't been able to find anything online as of yet.
Any suggestions would be greatly appreciated.
BTW - All of the latest service packs / patches have been updated and this is all on a LAN no Firewalls blocking any internal communications.
Stupid question?
by Y4 - 12/6/07 5:39 AM In reply to: Windows XP Clients Slow when launching applications by funhouse69Have you tried Chkdsk?
That's normal.
by R. Proffitt
- 12/6/07 6:23 AM
In reply to: Windows XP Clients Slow when launching applications by funhouse69
There are many causes of this but the network change is likely it. Old references to the old network will be done and you have to wait for a timeout. Some IT staffers think they can swap in a new server, keep the name the same and then puzzle why this happens. I will not tell why here.
-> Fixes include reimaging the workstations (many businesses have this procedure all good to go so it's a valid fix.) We can also use the Microsoft articles about XP and slow networking. Since you are the IT person you should know these without me posting them here.
Bob
Normal?
by funhouse69 - 12/6/07 2:16 PM In reply to: That's normal. by R. Proffitt
When I originally posted the message I thought that I was specific in saying that the old Domain Controller was retired but I think I said it was replaced. To be clear it was retired and not replaced by another server under the same name.
The process taken was this - A new server was built and brought up as a domain controller, Once this was completed I removed the old domain controller from the network by doing a DCpromo which completed successfully (no errors in either of the other domain controllers). I checked to make sure the roles were transferred to one of the new controllers as well.
While I can believe that this is "Normal Behavior" I can not believe that this can not be corrected in some way other than rebuilding system that is ridiculous. What if this happened in a corporation with hundreds of PC's? How could this have been avoided?
Let's use one instance where XP goes into slug mode.
by R. Proffitt - 12/6/07 3:02 PM
In reply to: Normal? by funhouse69
Let's say we were opening documents on our old server. The IT staff fields a new server and XP takes a dive. Why?
Hint: old entries in recent documents. I read your post of DCPROMO use so this is where we now have a replacement server. Your job is to find all the old entries that XP uses and clean them out.
As to the 100's of machines during a changeover, this is something that Microsoft helps keep the workerbees (IT staff) busy...
Bob
Hand this to your IT staffer.
by R. Proffitt - 12/6/07 3:57 PM
In reply to: Windows XP Clients Slow when launching applications by funhouse69
http://www.google.com/search?hl=en&q=site%3Asupport.microsoft.com+XP+SLOW+NETWORK
I won't duplicate these issues since... it's all there for you.
Bob
Resolved
by funhouse69 - 12/6/07 4:34 PM In reply to: Hand this to your IT staffer. by R. Proffitt
I'm very happy to say that I resolved the issue by going in to my DNS Server and changing the IP Address for the old Domain Controller to the one that replaced it. Rebooted the clients and everything is working perfectly. Thanks for all of your help with this.
~ Pete
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
