Another "Applying computer settings" issue - please advise (slightly long read).

[DukeN]

Hello,

Running into an issue with PCs taking a long time to boot when
connected to an external network, stuck at the "Applying Computer
Settings" screen. For typically 10-15 minutes, if not more.

Basically this happens for notebook users, that are connected to an
external network (not our corporate one, that has a domain controller,
etc on it) such as a home network. The notebook will take forever to
boot (stuck at that same screen), unless it is not connected to any
network.

This did not happen previously but started happening a while back.
Not related to the APC software issue (no one as far as I know has it
installed, and its happening to all users).

The two things of interest I did find in Event Viewer was a
certificate autologon denial, and a DHCP error issue. The certificate
autologon denial fix as suggested by MS does not do anything.

The DHCP error logs are:

The IP address lease 10.10.0.86 for the Network Card with network
address <hex address> has been denied by the DHCP server 10.0.0.254
(The DHCP Server sent a DHCPNACK message).

The IP address lease 192.168.1.101 for the Network Card with network
address <hex address> has been denied by the DHCP server 10.0.0.254
(The DHCP Server sent a DHCPNACK message).

Basically, the 10.xx.xx.xx is our company network subnet. The
192.168.xx.xx would be a customer, or user's home subnet.

Why is it on a fresh boot their machines are looking for a certain
range for IP addresses? DNS settings are configured perfectly as far
as I can tell, and all machines rely on DHCP.

Any and all input is appreciated, thanks.

 

[smlunatick]

Hello,

Running into an issue with PCs taking a long time to boot when
connected to an external network, stuck at the "Applying Computer
Settings" screen. For typically 10-15 minutes, if not more.

Basically this happens for notebook users, that are connected to an
external network (not our corporate one, that has a domain controller,
etc on it) such as a home network. The notebook will take forever to
boot (stuck at that same screen), unless it is not connected to any
network.

This did not happen previously but started happening a while back.
Not related to the APC software issue (no one as far as I know has it
installed, and its happening to all users).

The two things of interest I did find in Event Viewer was a
certificate autologon denial, and a DHCP error issue. The certificate
autologon denial fix as suggested by MS does not do anything.

The DHCP error logs are:

The IP address lease 10.10.0.86 for the Network Card with network
address <hex address> has been denied by the DHCP server 10.0.0.254
(The DHCP Server sent a DHCPNACK message).

The IP address lease 192.168.1.101 for the Network Card with network
address <hex address> has been denied by the DHCP server 10.0.0.254
(The DHCP Server sent a DHCPNACK message).

Basically, the 10.xx.xx.xx is our company network subnet. The
192.168.xx.xx would be a customer, or user's home subnet.

Why is it on a fresh boot their machines are looking for a certain
range for IP addresses? DNS settings are configured perfectly as far
as I can tell, and all machines rely on DHCP.

Any and all input is appreciated, thanks.

Sounds like the "customer's" notebook user account is a "limited" type
account which is not allowed to have the IP address changed. It seems
that only "Administrator" or 'Power User" type accounts can get the IP
address "changed."

Also, there could ba a possible "conflict" at the "external" network.
When the user decides to "log on" the external network is trying to
locate the domain controller but "failes" to find it.

 

[Phillip Windell]

Running into an issue with PCs taking a long time to boot when
connected to an external network, stuck at the "Applying Computer
Settings" screen. For typically 10-15 minutes, if not more.

Basically this happens for notebook users, that are connected to an
external network (not our corporate one, that has a domain controller,
etc on it) such as a home network. The notebook will take forever to
boot (stuck at that same screen), unless it is not connected to any
network.

You kind of answered your own question. Leave the Nic unplugged until it
boots up when you are dealing with some "other" LAN. This is particulary a
problem if the LAN uses the same IP range as the "real" LAN and a machine
exists on this "other" LAN which may have the same IP# as the DC on your
"real" LAN. The laptop may think it is looking at the DC and is waiting for
a response from it that is never going to happen. The machine will get an
address from DHCP perfectly fine if you plug the cable in after it boots up.

You also should set the nic that you most commonly use on the "real" LAN to
be the top in the binding order. This is found in the Properties of Net'
Places, then choose Advanced from the top menu then choose Advanced Setting
from the drop down menu. The rest should be obvious from there.

I have also see this problem occur is one or more LoopBack Adapters have
been added in the OS and are set to get an address by DHCP yet there is
obvously no DHCP to give them an address. The very laptop I am typing this
from has done that. So I deleted the Loopback Adapter,..then re-added
it,..and then left Client for MS Networks, F & P Sharing, and TCP/IP unbound
from the Loopback Adapter. I left only Virtual Machine Network Service
bound to it so that I can use it as a "network" to associate virtual
machines with when using Virtual PC.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------

 

[DukeN]

Thanks for the detailed response guys - just a couple of things:

Just to clarify smlunatick first reply, the priveleges are not an
issue as most of these users are local admins. Most of these external
networks are home networks with no domain controllers or anything like
that, and most routers have a different IP range than what's used at
work.

What baffles me is that this did not happen previously - but now it
happens much more often. Not sure what exactly would cause that given
the fact that our network has not changed much, if at all in that
timeframe.

Philip, you mentioned loopback adapters. Could you please provide
more detail as to what you are referring to for I'm unable to find
duplications under Network Connections. I did change the bindings but
this has not seemed to resolve this.

Seems to be the PC seems to be aching to reach a domain controller
every single time. The only time it logs in normally is if it has
access to one - all other times it hangs (unless it does not have an
IP). Any ideas as to why its looking for a domain controller or the
DHCP server on this domain every single time?

Thanks.

 

[Phillip Windell]

Philip, you mentioned loopback adapters. Could you please provide
more detail as to what you are referring to for I'm unable to find
duplications under Network Connections. I did change the bindings but
this has not seemed to resolve this.

If you didn't add any on purpose, there won't be any. I just used it as an
example of how having multiple adapters can adversly effect things. If you
wanted for some reason to add one you would do it by choosing "Add New
Hardware" and choosing to do the whole process "manually" and choose the
driver for Microsoft--->MS Loopback Adapter. They are sort of like "fake"
adapters without much purpose, but they are handy when working with Virtual
PC.

Seems to be the PC seems to be aching to reach a domain controller
every single time. The only time it logs in normally is if it has
access to one - all other times it hangs (unless it does not have an
IP). Any ideas as to why its looking for a domain controller or the
DHCP server on this domain every single time?

Domain Members *always* look for the domain controller. I'm just not sure
why yours is taking so long to "give up". It should immediately know there
is no DC and shouldn't even be showing the "Apply Computer Settings", at
least mine is that way. I'm not sure what to tell you there,..but I know
that leaving the Nic unplugged speeds things up.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------