ok. surely you guys have seen this problem before. i've worked in multiple domains over the course of 6 years and all have had the same problem. many of which are only stocked with the latest computers, OSes, and fastest servers.
about 30-50% of the time you RIGHT-CLICK something on an NT/2K/XP desktop or in File Explorer (usually after you haven't done it in about 30 minutes), it takes 1-2 MINUTES for the context menu to pop-up. :disgust: there is NO increase in resource usage or any accompanying "grinding" of the drives, or freezing of other programs. it just sits there without any indication of progress, UNTIL IT MAGICALLY APPEARS without any fanfare.
my personal hairbrained theory is that when you RIGHT-CLICK, the client wants to check with the AD to see what options in the context menu group policy allows. but 1-2 minutes to complete this task tells me that I've got some setting wrong. but I have absolutely no clue what it could be.
surely some other pros have seen this problem before and know an easy fix.
its embarrassing when i go to set up a new computer and tell them how fast it is, then when they right-click on something, it behaves like the PII Win98 box I just chucked in the dumpser.
i'm gonna run a check down for you:
1. Client DNS Addresses *are* pointing to DCs w/ DNS Server Running
2. Group Policy is not enforced for 90% of LAN PCs
3. No software firewalls running across the entire network
4. 10/100 switched infrastructure
5. 1 W2K and 1 W2K3 DCs in unified Domain
6. Both are GCs
7. W2k3 retains all FSMO roles
8. File Replication & DNS logs report no unusual errors
9 Problem only occurs on NT based OSes
10. DHCP servers running on both DC1 & DC2 (80/20 configuration)
about 30-50% of the time you RIGHT-CLICK something on an NT/2K/XP desktop or in File Explorer (usually after you haven't done it in about 30 minutes), it takes 1-2 MINUTES for the context menu to pop-up. :disgust: there is NO increase in resource usage or any accompanying "grinding" of the drives, or freezing of other programs. it just sits there without any indication of progress, UNTIL IT MAGICALLY APPEARS without any fanfare.
my personal hairbrained theory is that when you RIGHT-CLICK, the client wants to check with the AD to see what options in the context menu group policy allows. but 1-2 minutes to complete this task tells me that I've got some setting wrong. but I have absolutely no clue what it could be.
surely some other pros have seen this problem before and know an easy fix.
its embarrassing when i go to set up a new computer and tell them how fast it is, then when they right-click on something, it behaves like the PII Win98 box I just chucked in the dumpser.
i'm gonna run a check down for you:
1. Client DNS Addresses *are* pointing to DCs w/ DNS Server Running
2. Group Policy is not enforced for 90% of LAN PCs
3. No software firewalls running across the entire network
4. 10/100 switched infrastructure
5. 1 W2K and 1 W2K3 DCs in unified Domain
6. Both are GCs
7. W2k3 retains all FSMO roles
8. File Replication & DNS logs report no unusual errors
9 Problem only occurs on NT based OSes
10. DHCP servers running on both DC1 & DC2 (80/20 configuration)
