"Applying Personal Settings" Logon to Domain Delay

It could be a DNS issue on the local machines if their DNS settings are not pointing to an internal DNS server. If the DNS settings on the machine are pointing to an external DNS server, login times can be lengthy.

Do the users use roaming profiles? There are several issues related to roaming profiles that may cause that problem.

It could be the user's local profiles. Try renaming the user's current profile and allow the user to log in and recreate the profile. If the user logs in in an acceptable amount of time, move the users documents, favorites, desktop icons, etc. to the new profile.

The preferred method of configuring DNS is to point your internal clients to your internal DNS server and then to have external queries forwarded to the external DNS servers.

GL

No roaming profiles are being used.

Have you checked the local DNS settings on the troubled computers?

If everyone on the domain at this office was configured the same way and their PC's imaged using the same standard, why would it be a dns issue? Just curious.






Casey

Well, I was confusing your question with another question.

I would look at the local profile issue. Rename the users current profile and have user log in again. A new local profile will be created that is void of all the junk and clutter that can be associated with user profiles. If the user now logs on quickly, then he/she had a corrupt profile. Necessary files can be copied from the old profile to the new profile. I would limit copying files to desktop icons, my documents, and favorites. You don't want to copy that which may have corrupted the profile in the first place.

You may want to consider any login scripts that may run when the user logs in, such as a mapped drive to discontinued shared folder.

GL

Any news yet?

My boss doesn't believe it's a profile issue, he thinks it has to do with the network. I found a fix that might work in group policy that has the user waiting for the network at logon as opposed to using the cached credentials. This may work, but what about the people with laptops who travel and try to logon with their profile? If it's waiting for the network and there is no network, will they be able to logon to their laptops? I appreciate all the suggestions so far btw.



Thanks
Casey

Well, I misread you original post. I thought you are able to log in ok with the domain admin account. Read the explanation for the group policy before making changes. Unless I use roaming profiles, I always leave that default.

Well, we tried a regkey fix that has appeard to work...but not on everyone's PC. My bos and I continue to look into the issue as one of our other remote locations is starting to report similar problems.





Casey

With some help from Microsoft we were able to correct the problem. The main fix was lowering the MTU size, too many packets were being dropped and/or fragmented. Once we lowered the MTU at each remote location...logon times went from 5-10 minutes to less than 30 seconds.
        Since nobody came up with the answer, or comment that led to the answer I'll be requesting a mod close this topic. Thanks to everyone for the feedback, it's appreciated.





Thanks
Casey