General discussion

Locked

loadg/applyg persnl settingtakeslongtime

By fajarpri ·
Hi all,
I have a w2k domain with w95, w98, and w2kp clients.

The problem is :
Why do w2kp clients take a long time (15 mins to 30 mins) for loading and applying personal settings?

I don't use roaming profiles, all profiles are local. I don'teven apply any group policy on the users (well, only default domain group policy that comes with w2k server).

Is it a cable problem? But, w95 and w98 clients can logon very fast (below 30 secs).

All w2kp clients hardware specs are: PIII-500, 128MB, 5.1GB. For server : PIII-600, 256MB, 10GB. We're using cisco switch.

Please help me. I'm desperate and I'm offering 750 clean points for this. Thanks a lot.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

loadg/applyg persnl settingtakeslongtime

by QB In reply to loadg/applyg persnl setti ...

Normally I would say try adding more memory but I never heard of it taking 15-30 min (is that a typo?) We have around 75 w2kpro machines all with 512mgs except for mine that only has 396mgs and my computer starts up considerably slower that the others (at least 45 seconds longer). The total startup time for my machines is around 3-5 mins so maybe it is just a memory problem. I would try loading a machine up with as much ram as you can find (even shut a couple of machines down and borrow from them just to see what kind of difference it makes. That way you will know if it is a hardware problem or not. Another thing you might want to try is checking startup programs and extensive desktop settings. You may what to try logging into a computer with a username that has never logged into that computer before (creating a new profile) try that a couple of times will let you know if it is extensive desktop setting since the new profile won't have any special settings.

Collapse -

loadg/applyg persnl settingtakeslongtime

by fajarpri In reply to loadg/applyg persnl setti ...

Thanks QB, I brought my own PC from home just to test it. It's PIII-450 with 256 MB memory. But, still it takes 20-30 minutes to logon (loading and applying personal settings. I also created a few new user accounts with nothing in it, but, still soooooo slow. This w2kp logon process is really getting into me.

From your experience, has any of those 75 w2kp clients shown similar symptoms like mine?

Thanks.

Collapse -

loadg/applyg persnl settingtakeslongtime

by pginnega In reply to loadg/applyg persnl setti ...

If there is not a hard were problem, I would check to see if DNS is set up for optimization. Windows 2000 and Active directory need DNS to resolve domain computer names on the network. Also check WINS. Both these servercices,if properly configured can speed up network access. Is the DNS or WINS server on a local subnet? Also try just using the Win2k Workstations with TCP/IP only. If need be try editing the local Host and LMHOST files on the Win2K boxes to point to the DNS and WINS servers. Hopethis helps

Collapse -

loadg/applyg persnl settingtakeslongtime

by fajarpri In reply to loadg/applyg persnl setti ...

WINS? If I'm not mistaken, w2k doesn't need it anymore, right?

I use one DNS server only, and of course it's on the same subnet :)

The w2kp clients have these as networking components :
Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and Internet Protocol (TCP/IP). That's all.

Have you encountered any troubles similar to mine?

Thanks.

Collapse -

loadg/applyg persnl settingtakeslongtime

by umbral-echo In reply to loadg/applyg persnl setti ...

You might be able to detect the problem with a special user log discussed in the TechNet article Q221833. Go to:

http://search.support.microsoft.com

Search the Windows 2000 articles for the number of the article. This will allow you write a log file that helps tremendously in troubleshooting the user logon process when the profile and Group Policy loads. Something tells me that you are going to see some strange things happening in your logon process once you do this. At any rate, hopefully this will let you detect the specific problem.

One trick we used was to share the folder the log file is created in so that it can be accessed by another computer. When the user logs on and it just sits and sits and sits, go to the other machine and access the share. Open the log file and you will see the stage that the computer is waiting at and you don't need to wait for the user to get a desktop (the log file will be complete at this point and might not reveal your problem).

Once youhave identified the source of the difficulties you can narrow down your troubleshooting.

Collapse -

loadg/applyg persnl settingtakeslongtime

by fajarpri In reply to loadg/applyg persnl setti ...

i'm really out of answers here

Collapse -

loadg/applyg persnl settingtakeslongtime

by fajarpri In reply to loadg/applyg persnl setti ...

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums