Slow "Applying Computer Settings" on a small number of clients (long post)

Hi All

I've recently installed an SBS network at my company, and everything has
gone pretty smoothly. One issue I've had lately involved about 5 clients
taking a long time (roughly 2 minutes) to get past "Appplying Computer
Settings" - the disk would thrash away as normal, then stop, and just
wait for another 90 seconds or so before popping up the login box. All
of the affected clients are HP DX2000 machines, with my other 5 DX2000's
working fine, as well as the various "local whitebox builder" machines
I've inherited.

There have been some NIC issues, including:

An occasional "network cable unplugged" icon on the taskbar which
doesn't respond when clicked

The name appearing as "Local Area Connection 2"

The following two errors in the local System event log:

******************************************************************
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11191
Date: 14/07/2005
Time: 17:21:11
User: N/A
Computer: ALPHA-042
Description:
The system failed to update and remove pointer (PTR) resource records
(RRs) for network adapter
with settings:

Adapter Name : {9707A2D2-EFBC-4FDF-93E1-3A932F016541}
Host Name : ALPHA-042
Adapter-specific Domain Suffix : Alpha.local
DNS server list :
192.168.102.2
Sent update to server : <?>
IP Address : 192.1.1.1

The system could not remove these PTR RRs because because of a system
problem. For specific error code, see the record data displayed below.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 27 00 00 Q'..
******************************************************************

******************************************************************
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11197
Date: 14/07/2005
Time: 17:21:10
User: N/A
Computer: ALPHA-042
Description:
The system failed to update and remove host (A) resource records (RRs)
for network adapter
with settings:

Adapter Name : {9707A2D2-EFBC-4FDF-93E1-3A932F016541}
Host Name : ALPHA-042
Primary Domain Suffix : Alpha.local
DNS server list :
192.168.102.2
Sent update to server : 192.1.1.1
IP Address(es) :
192.168.102.37

The reason the update request failed was because of a system problem.
For specific error code, see the record data displayed below.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 27 00 00 Q'..
******************************************************************

192.168.102.2 is my SBS, 192.1.1.1 doesn't exist and isn't in the ISA
LAT.

Now, I seem to have resolved this by running NETSH WINSOCK RESET
and NETDIAG /FIX on each machine, but I don't have a clue what the
issue was, how I resolved it, and how to stop it reoccuring.

Any info anyone can offer would be appreciated.


--
Daniel Walker
IT Manager, Alpha Construction Ltd

THIS POST REPRESENTS MY OWN OPINIONS, NOT MY EMPLOYER'S.

Maybe some answers here...
http://www.eventid.net/display.asp?e...DnsApi&phase=1

--
Merv Porter [SBS MVP]
===================================
"Daniel Walker walker alphaconstruction CO.UK>"
<daniel<insert_a_d0t_hereatinsert_a_d0t_here> wrote in message
news:Xns96948867164CBdw109alphacon@207.46.248.16...
> Hi All
>
> I've recently installed an SBS network at my company, and everything has
> gone pretty smoothly. One issue I've had lately involved about 5 clients
> taking a long time (roughly 2 minutes) to get past "Appplying Computer
> Settings" - the disk would thrash away as normal, then stop, and just
> wait for another 90 seconds or so before popping up the login box. All
> of the affected clients are HP DX2000 machines, with my other 5 DX2000's
> working fine, as well as the various "local whitebox builder" machines
> I've inherited.
>
> There have been some NIC issues, including:
>
> An occasional "network cable unplugged" icon on the taskbar which
> doesn't respond when clicked
>
> The name appearing as "Local Area Connection 2"
>
> The following two errors in the local System event log:
>
> ******************************************************************
> Event Type: Warning
> Event Source: DnsApi
> Event Category: None
> Event ID: 11191
> Date: 14/07/2005
> Time: 17:21:11
> User: N/A
> Computer: ALPHA-042
> Description:
> The system failed to update and remove pointer (PTR) resource records
> (RRs) for network adapter
> with settings:
>
> Adapter Name : {9707A2D2-EFBC-4FDF-93E1-3A932F016541}
> Host Name : ALPHA-042
> Adapter-specific Domain Suffix : Alpha.local
> DNS server list :
> 192.168.102.2
> Sent update to server : <?>
> IP Address : 192.1.1.1
>
> The system could not remove these PTR RRs because because of a system
> problem. For specific error code, see the record data displayed below.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 51 27 00 00 Q'..
> ******************************************************************
>
> ******************************************************************
> Event Type: Warning
> Event Source: DnsApi
> Event Category: None
> Event ID: 11197
> Date: 14/07/2005
> Time: 17:21:10
> User: N/A
> Computer: ALPHA-042
> Description:
> The system failed to update and remove host (A) resource records (RRs)
> for network adapter
> with settings:
>
> Adapter Name : {9707A2D2-EFBC-4FDF-93E1-3A932F016541}
> Host Name : ALPHA-042
> Primary Domain Suffix : Alpha.local
> DNS server list :
> 192.168.102.2
> Sent update to server : 192.1.1.1
> IP Address(es) :
> 192.168.102.37
>
> The reason the update request failed was because of a system problem.
> For specific error code, see the record data displayed below.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 51 27 00 00 Q'..
> ******************************************************************
>
> 192.168.102.2 is my SBS, 192.1.1.1 doesn't exist and isn't in the ISA
> LAT.
>
> Now, I seem to have resolved this by running NETSH WINSOCK RESET
> and NETDIAG /FIX on each machine, but I don't have a clue what the
> issue was, how I resolved it, and how to stop it reoccuring.
>
> Any info anyone can offer would be appreciated.
>
>
> --
> Daniel Walker
> IT Manager, Alpha Construction Ltd
>
> THIS POST REPRESENTS MY OWN OPINIONS, NOT MY EMPLOYER'S.

"Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in
news:uO3jfSUiFHA.3544@TK2MSFTNGP15.phx.gbl:

> http://www.eventid.net/display.asp?e...1746&source=Dn
> sApi&phase=1

That looks good - I think I'll try the DHCP lease thing if it reoccurs.

Thanks Merv

--
Daniel Walker
IT Manager, Alpha Construction Ltd

THIS POST REPRESENTS MY OWN OPINIONS, NOT MY EMPLOYER'S.