Delay logon until IP address is assigned

  • Thread starter Thread starter Andrew
  • Start date Start date
A

Andrew

Hello Group,

Is it possible to delay the logon screen until an ip address gets assigned
from DHCP? We have some wireless devices that take around 1 min after the
machine has booted to get an ip address, so when a users logs on, they get
roaming profile issues.

Thanks, Andrew
 
Andrew said:
Hello Group,

Is it possible to delay the logon screen until an ip address gets assigned
from DHCP? We have some wireless devices that take around 1 min after the
machine has booted to get an ip address, so when a users logs on, they get
roaming profile issues.
Click to expand...

Assuming it works (first attempts) then I am pretty
sure this is the way it already works.

Client coputers initialize IP (getting an IP address),
start some more services, Authenticate THEMSELVES,
download their own (Computer) GPOs, authenticate
the user only after all that.

If however, the machines have given up on the (initial
IP address attempt) then it will continue on with cached
information and not computer authentication.

You probably should start by resolving the initial
DHCP problem.
 
Thanks Herb,

Looks like the application itself needs to wait until the user logs on.

Ta, Andrew
 
Herb, can this be done? i mean waiting until the adress is assigned before
the ctrl alt del screen appears?

thanks, andrew
 
Andrew said:
Herb, can this be done? i mean waiting until the adress is assigned before
the ctrl alt del screen appears?
Click to expand...

I still don't think you will see the Ctrl-Alt-Del
screen prompt UNTIL you have an IP.

Not only will you have the IP (if it CAN be acquired),
your computer(s) will also be authenticated on the
Domain if they can authenticate.

What precisely is the problem and what do you wish
to do?
 
Thanks again,

No worries Herb, the wireles card seems to startup after the logon screen
appears (10-20 secs afterwards) so the users will be adivsed to wait a sec
before logging on.

Thanks for your help, Andrew
 
Andrew said:
Thanks again,

No worries Herb, the wireles card seems to startup after the logon screen
appears (10-20 secs afterwards) so the users will be adivsed to wait a sec
before logging on.
Click to expand...

It's not supposed to do that. Maybe you should
(reset) the WinLogon or Network timeouts....
 
Andrew said:
Tanks again Herb,

Please could you let me know how to do this?
Click to expand...

The following does not fully answer the issue, but
I ran out of time for searching and wanted to give
you some leads you can pursue.

PLEASE update us all (here) if you solve the problem
or find something of use....

Increase Domain Logon Timeout over Network
http://support.microsoft.com/kb/q163204/

This KBs offer hotfix or explanations for similar problems:
Group Policy processing does not work...
http://support.microsoft.com/?kbid=842804

60-second to 120-second delay occurs in user authentication when you log on
to Windows XP in a wireless network
http://support.microsoft.com/?kbid=822725
http://support.microsoft.com/?kbid=826145


You can DISPLAY the (old NT) error message
if the user gets logged on with cached
credentials (Win2k+ disabled it) so at least
they and you can see the situation:
http://www.jsiinc.com/SUBA/tip0400/rh0416.htm

Hive: HKEY_CURRENT_USER
Key: Software\Microsoft\WindowsNT\CurrentVersion\Winlogon
Name: ReportDC
Type: REG_DWORD
Value: 0 default: suppress domain controller message
Value: 1 dont suppress domain controller message


Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Name: ReportControllerMissing
Type: REG_SZ
Value: FALSE default: suppress domain controller message (default)
Value: TRUE dont suppress domain controller message (must be all caps TRUE)
 
Back
Top