Logon Delay After Entering Password

[DeanHiggins]

Guys, I believe most of you already heard and familiar with this issue.

1. A user in my company is using a brand new PC and everytime she login with her username and password, the screen will just delay at the "Applying Computer Settings" box for almost 5-10 minutes. This only happens if she login straight away as soon as the PC reaches the login screen.

2. If she waits for at least 2-3 minutes at the login screen and then login, there will be no delay.

3. I know this is related to network and yes my company is using a login script. Tried unplugging the network cable during startup, and there will be no delay.

4. The thing is, this issue didn't happen on almost all PCs, not even the oldest PCs there are here. So I'm wondering if there is any configuration I missed.

If you have any suggestion on what else I could try to solve this, please do help.
I'd be greatly appreciated it. Thanks in advance.

 

[linney]

Can you do anything with this Group Policy setting?

Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon

See what the setting is on the faster machines.

 

[MiggyD]

Are you using MacAfee? or Symantec? Could be your AV blocking ALL ports until it checks system files, registry, and other 'automatic' services.

Also, check any AV settings regarding 'Scan System At Startup'. If possible change them to something like 20 mins after she is scheduled to start working.

Also, if the 'brand new PC' is a laptop, make sure the wireless card is off (or disabled.) You mentioned that It's wired--I had a tabletPC that I had both wired and wifi'd and it took 2-3 minutes to login cause it was acquiring 2 IP at the same time when I checked with the server.

Other than that, I don't know what else to consider as the cause...anyone else?

-MiggyD



My mind not only wanders, it sometimes leaves completely.

 

[DeanHiggins]

Can't do anything on the Group Policy Settings as it is managed centrally on the HQ and I've got no access for it.

It does have Symantec SEP installed, but all the settings are also managed centrally, so any changes are impossible.

The computer has been clean-installed, so I can say there are no bloatwares during startup.
All computers in the office are being setup the same and the softwares installed are also exactly the same.

What strange is, why this is only happening to one machine only, while everything setup and installed across the company are exactly the same.

 

[goombawaho]

Make sure that the DNS settings are the same on the problem and non-problem computers especially if you're connecting to a MS server. The DNS server should be the MS server ip address NOT an internal router or other DNS setting.

I've seen the "hanging at applying personal settings" issue in this instance on computers connected to Server 2003/SBS 2003.

 

[Lemon13]

does it also happen when the user in question logs in on a different pc?
and when another user logs in to her pc?


M. Knorr

MCSE, MCTS, MCSA, CCNA

 

[linney]

What follows on from the previous suggestions is removing both user and machine from the Domain and then adding them back.

 

[gbaughma]

Make sure that the DNS settings are the same on the problem and non-problem computers especially if you're connecting to a MS server. The DNS server should be the MS server ip address NOT an internal router or other DNS setting.

Exactly. If you are on AD, the primary DNS needs to be the AD controller, not an external DNS.

I have had your exact problem before on a domain, and every time this turns out to be the problem.

The delay is because it's trying to find the domain controller, and it can't even try until the DNS servers timeout.



Just my 2¢

"What the captain doesn't realize is that we've secretly replaced his Dilithium Crystals with new Folger's Crystals."

--Greg

http://parallel.tzo.com

 

[cdogg]

Have you checked Event Viewer for any errors or warnings that stand out from the crowd?

I also second the suggestion to remove the PC from the domain by dropping it into a workgroup, reboot, then readd it. Make sure you have a local admin account active before doing so.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.

 

[DeanHiggins]

Found 3 errors in event viewer. I'll remove and readd the machine from the domain to see if that helps.

[blue]Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 1/27/2010
Time: 7:39:32 AM
User: EXIM\main-marlene
Computer: MAIN-MARLENE
Description:
Windows cannot access the file gpt.ini for GPO cn={854BD336-9465-4C9F-A674-931526073E5B},cn=policies,cn=system,DC=exim. The file must be present at the location <\\exim\SysVol\expd\Policies\{854BD336-9465-4C9F-A674-931526073E5B}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

[/blue]


[green]Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 1/27/2010
Time: 7:39:32 AM
User: EXIM\main-marlene
Computer: MAIN-MARLENE
Description:
Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

[/green]


[purple]Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11165
Date: 1/27/2010
Time: 7:33:32 AM
User: N/A
Computer: MAIN-MARLENE
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:

Adapter Name : {32129203-7EE6-48F5-9602-545469E3B174}
Host Name : main-marlene
Primary Domain Suffix : exim
DNS server list :
192.1.83.16, 10.254.1.31, 10.254.1.119
Sent update to server : <?>
IP Address(es) :
192.1.83.103

The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.

To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Data:
0000: 2a 23 00 00 *#..
[/purple]

 

[goombawaho]

You didn't say if you checked the DNS. Hopefully you did that simple thing before removing from domain or other troubleshooting.