CTRL + ALT + DEL appears but have to wait for successful logon

kennysarmy · November 10, 2009

This issue seems to have started since coming back in September.

Need to investigate how wide spread and if it's affecting only certain PC builds or areas but in essence the following is happening:

PC is switched on and boots up normally.

CTRL+ALT+DEL screen appears.

If you try and login immediately you get "domain is not available".

If you try and login after say 10 seconds you are logged in but the desktop does not appear and the error message "network path was not found" appears...if you clear the error message and refresh the background then the desktop does appear and all seems OK. However I believe the logon script has nt run.

If you wait for about a minute and attempt to logon then everything is fine. No errors at all.

In the summer we had some new core switches installed, AT hardware was replace by 3 COM kit. Namely a 3Com 5500G & 2 x 3Com 2900-48 switches.

Co-incidence?

Does this sound like a server or switch issue?

Thanks.

cookie_monster · November 10, 2009

First thing to check before digging too deep.

Do you have always wait for network at startup and logon set in group policy?

Also check that your switch ports with Windows clients on are set to fast forward. I don't know much about 3 COM switches but we had no end of problems like this with our Planet switches.

Edited November 10, 2009 by cookie_monster

Potato-Peeler · November 10, 2009

We had a similar problem with a batch of dodgy network cards if that helps? Replaced them with itnel pro gt 1000s and they worked fine.

kennysarmy · November 10, 2009

found this: Fast Logon Optimization: Group Policy

hopefully cookie_monster is right...

will report back...

kennysarmy · November 10, 2009

If you want to guarantee the application of Folder Redirection, Software Installation, or roaming user profile settings in just one logon, enable this setting to ensure that Windows waits for the network to be available before applying policy.

OK so I've enabled that....

PC sits longer now at the "Preparing network connections"....

However, if I try to logon when the CTRL + ALT + DEL appears...I get....logged in BUT NO logon script runs.....

IF, I wait 5-10 seconds after the CTRL + ALT + DEL appears..then...LOGS IN FINE.....

cookie_monster · November 10, 2009

It sounds to me like the switch ports aren't switching to forwarding mode quickly enough I'd take a look in the 3COM manual of have a word with your supplier, or you could post in the network forum I think a few people on here use 3COM switches.

Is this happening everywhere or just in certain areas?

Edited November 10, 2009 by cookie_monster

kennysarmy · November 10, 2009

have set this:

Administrative Templates -> System -> Scripts-> Run Logon

scripts synchronously - enabled

If you enable this setting, Windows Explorer does not start until the logon scripts have finished running. This setting ensures that logon script processing is complete before the user starts working, but it can delay the appearance of the desktop.

cookie_monster · November 10, 2009

Ah yes I have that set as well as I find that certain functions in logon scripts don't always work unles you set that. It also makes the scripts run one after the other as well as just waiting for them to finish.

That still doesn't really explain this though as the network should be ready before logon now.

However, if I try to logon when the CTRL + ALT + DEL appears...I get....logged in BUT NO logon script runs.....

IF, I wait 5-10 seconds after the CTRL + ALT + DEL appears..then...LOGS IN FINE.....

What does your logon script do is it just mapping drives and printers or does it contain other functions?

Edited November 10, 2009 by cookie_monster

mattx · November 10, 2009

Anything in the server / client event logs ?

I'd also check possible duplex mismatch / driver settings & driver versions / also firmware on the switches.....

Edited November 10, 2009 by mattx

kennysarmy · November 10, 2009

so the changes I have made are:

System/Logonhide

Policy Setting

Always wait for the network at computer startup and logon Enabled

System/Scriptshide

Policy Setting

Run logon scripts synchronously Enabled

The situation seems to have been improved in that I can always log on now - no more "domain is not available" messages, however it's hit and miss as to whether the login script works depending on how long you leave it before attempting logon.

Will email the guys who put the switch in in the summer see if they know of any setting that might help with the "forwarding mode".

thanks.

kennysarmy · November 10, 2009

Ah yes I have that set as well as I find that certain functions in logon scripts don't always work unles you set that. It also makes the scripts run one after the other as well as just waiting for them to finish.

That still doesn't really explain this though as the network should be ready before logon now.

What does your logon script do is it just mapping drives and printers or does it contain other functions?

Basically just mapped drives...then calls another script to do things such as set reg. values and copy the odd file to the local pc...

kennysarmy · November 10, 2009

Anything in the server / client event logs ?

on the client...

"windows cannot obtain the domain controller name for your computer network (The specified domain either does not exist or could not be contacted)"

mattx · November 10, 2009

Give me a D, give me an N, give me an S

Anything on the server's DNS event viewer ?

Maybe worth running DCDIAG to see what you get.

Edited November 10, 2009 by mattx

kennysarmy · November 10, 2009

DNS logs fine on both DC's.

Only errors reported back from DCDIAG are:

Starting test: systemlog