Slow login to W2K from WinXP

dadlugie · April 13th, 2002, 02:36 PM

I purchased some new Acer laptops with XP Pro on them. I have two different networks I logon to. One, a W2K Small Business Server, it takes about 4 minutes to get logged on. It takes a long time to apply the settings. My other network (seperate) is a W2k Adv server which works fine (normal boot). If I boot without network connectivity it also works fine. I have been over the small business server several times and can't figure it out.

DVNT1 · April 13th, 2002, 03:18 PM

Is either one setup as a domain server?

This might help...

Quote:

There was a bug in windows 2000 that would cause the scheduled tasks folder to be searched when ever the user would browse network drives. Microsoft developed a fix for this bug. The fix fixed the problem and it also had nice side affect of speeding up browsing of Microsoft networks. Below are instructions how to apply the fix.

1. Open up regedit.
2. Navigate to HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Explorer/RemoteComputer/NameSpace.
3. Find a key named {D6277990-4C6A-11CF-8D87-00AA0060F5BF}.
4. Right click on it and delete it.
5. Restart

dadlugie · April 14th, 2002, 02:01 AM

Both servers are domain controllers for different domains

DVNT1 · April 14th, 2002, 08:04 AM

Do they clients use the same DNS server? Is it AD enabled? Does the DNS server serve both domains?

dadlugie · April 14th, 2002, 08:33 AM

Both are AD, the servers are in seperate cities and use their own dns on the server they log into.

Cyclone2 · April 14th, 2002, 08:37 AM

Tweak #10 - Speeding Up Share Viewing

This is a great tweak. Before I found it, I was always smashing my head against the table waiting to view shares on other computers. Basically, when you connect to another computer with Windows XP, it checks for any Scheduled tasks on that computer - a fairly useless task, but one that can add up to 30 seconds of waiting on the other end - not good! Fortunately, it’s fairly easy to disable this process. First, navigate to HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version/Explorer/RemoteComputer/NameSpace in the Registry. Below that, there should be a key called {D6277990-4C6A-11CF-8D87-00AA0060F5BF}. Just delete this, and after a restart, Windows will no longer check for scheduled tasks - mucho performance improvement!

http://www.tweaktown.com/document.ph...Id=120&dPage=5

Might help?

Doh! Shoulda read DVnT's ressponses better- beat me to it

darksign · April 23rd, 2004, 06:46 PM

I have exactly the same problem - 8 users on XP Pro logging into a Win 2k SBS. It's running AD and Exchange.

When a user logs in, their screen sits and waits while it is applying settings - usually takes 3-4 minutes.

Once they are in, it's fine, and everything moves along at a nice rate. The server is compeltely over the top on specs, so I know that's not it.

Someone told me to check the DNS, but I can't find anything wrong with how it's set up. Can anyone recommed specifically what to check in the DNS, or give any other solution?

dadlugie · April 24th, 2004, 07:54 AM

It does have to do with the dns. I was pulling the DHCP from a router instead of the server which pointed to my ISP for DNS. I assume you are running DNS on the server. Make are that it is on the top when the computer gets an address from DHCP. The way I found it was to use a static address on the laptop and then only had the server as dns and it worked, so then I figured out what was wrong.