Slow login in to network

Topic

New Reply

We are running a Windows 2000 server (without Exchange). When each of our PC’s log in to it EACH computer hangs for a full 10 minutes at the “loading personal settings”. I thought it was only my PC at first, but all of them are doing this. This morning I rebooted the server thinking that that might clear up something, but that didn’t help (it only added frustration in the office while everyone waiting to get to work).

What might cause this to hang like this?

–KZ

Reply | Quote

Replies

Once lgged in, can a user access the server OK?

Have you checked the event logs for anything untoward?

Are the workstation profiles local or on the server?

Reply | Quote

What desktop OS are you using? Have you recently removed or disabled any shared devices?

Joe

--Joe

Reply | Quote

Each PC’s OS is XP Pro.

Once logged in everything operates normally.
“Workstation profiles”? I’m not sure where they are stored. I would think that they would be stored locally.

There are a number of event logs. I have no idea what they mean though. I may need to get our network guy to come look at these….but it will cost us a fortune.

–KZ

Reply | Quote

[indent]

---

I may need to get our network guy to come look at these….but it will cost us a fortune.

---

[/indent]

And now you know why

What has changed on your network? Have you installed any AV software that might be scanning your network shares each time you log on? Do you have a logon script that is attempting to connect to shares that no longer exist. Just throwing some random thoughts out.

Definetely the first thing to do is to check what DNS server your machines are point to ( Run,, Command.. ipconfig /all), and then go to that server and make sure that it really is running it’s DNS service properly.

Reply | Quote

There are no real EventID’s worth trouble. All that is there is 11 which refers to the w32time. The other is 1039 about the DHCP cleaning up the database.

I can’t tell at all what is happening in the background as it loads Windows all the way, just hangs at “applying the personal settings”. This is on each PC in the network too, so it’s not just my PC.

Not sure what else to check. All computers run fine once they get past that 10-15 minute hang. The DHCP and DNS appear to be set up correctly.

–KZ

Reply | Quote

1.) What has changed on your network? 2.) Any hardware added or removed? 3.) Any software added or removed? 4.) Are scripts run when each PC logons on?

Joe

--Joe

Reply | Quote

Nothing changed that I can think of. We did have some QOS updates. Would that make a difference?

There is one script that runs upon log in.
net use f: /delete
net use f: (name of our server)(name) /yes

–KZ

Reply | Quote

Since “Quality of Service” is all aobut making sure some applications get bandwidth at the expense of others, I would ceratinly check into it.

Have you tried commenting out each line in the login script, or even removing it entirely to see if that affects the problem? That’s what I would do.

Reply | Quote

I tried deleting the script from one person’s login and rebooted and it didn’t effect the speed at all. It actually didn’t even effect the way it logged into the server at all that I could tell.

–KZ

Reply | Quote

One question, what client are you using to log in? (I would assume the Microsoft one but I have learned what “assume” does.)

Under the event logs if you click the “View” menu select “Filter” and clear the “Information” and “Successful Audit” check boxes you will get to see the more important messages. The logs most likely to be of interest are “Security” and “System” but don’t ignore the others (see “assume” above).

Try this MS search and enter “Event id” together with the number from the log for more info.

I have “lost” an alternative link but will post that is and when I find it again.

HTH

Reply | Quote

According to the instructor of the Server 2003 course I am on at this very moment, the most likely cause of slow logons is a problem with DNS. There could be a problem between DHCP and DNS. Setting the IP address of the client would ensure that it is able to find its DNS server, but how practical that would be depends on the number of clients you have to deal with. Setting the IP address of one client manually and seeing if that gives an improvement would be a useful test in any case.

You could try checking DNS for redundant entries.

There might be a problem with replication of DNS if there is more than one DNS server on the network.

Reply | Quote

Yes, Granville, each of the PC’s are logging in using the MS client.

The warning each day is “The NTP server didn’t respond”. There are some other “information” items though.

Each of the computers are using DHCP with everything being supplies automatically to each PC. I really don’t want to change that.
Also, there is only one DNS server on the network.

–KZ

Reply | Quote

Ok the client was a long shot anyway but you never know.

Here are some sites that may help you in searching out the problem.

MS KB Alerts

or if you can find the relevant message in the event logs

EventId

MS KB on the subject “The NTP server didn’t respond” is here. As this deals with the registry, the usual dire warnings apply.

take care now

Reply | Quote