Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP workstation w/ 2000 SB Server == SLOW!!!

Status
Not open for further replies.

locke787

Programmer
Joined
Jan 20, 2004
Messages
1
Location
PR
Folks,

I recently added a number of brand new XP Pro machines to my network. Users authenticate via a domain set up on a Win 2000 SB server. First off, It takes about 3-5 minutes to log into the XP workstations. The lag is specifically on the "Loading your personal settings", " Applying computer settings..." login process. #2: Any time you request "properties" of a file or directory it takes a *long* time to bring up the window #3: When you "apply" changes to properties or settings that affect files on the network it also lags a bunch. We have *NONE* of these problems w/ our 95,98,ME workstations which authenticate w/ the same 2000 server. Any ideas on how I can minimize this sluggishness with XP and 2000 ?


Any help much appreciated,
Alfredo

 
95, 98 etc use lmhosts, wins, broadcast, DNS, hosts, resolution order. 2000 and above use Hosts, DNS, ...

The order is reversed. Check DNS.

 
I agree with xmsre, it sounds like your new systems (XP) are having problems locating the dcomain server to be authenticated initially, then are haveing problems finding the files/shares you want to open. Is this a mixed mode or native mode Domain?

I have been seeing a lot of browsing issues on other boards concerning XP, and it appears to be a serious problem, especially if the folder being accessed has a large number of files in it.

Something to check, make sure that the XP systems are not forcing the domain to do a master browser challenge every time they come up. Check the log files on the DC, then try to log on to one of the XP systems, then check the DC log again to see if a MASTER browser election is being forced. If so, you need to set the XP registry to stop the Master Browser assertion.

Also, make sure the XP systems have been correctly added to the Domain, and are showing up in the AD correctly as Domain members, AND are showing up in the DNS correctly.

HTH,

David Holbrook
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top