Server: Win2K3 R2 standard - SP1
Client: Win XP Pro SP3

On this one XP Pro client(10 users network), I get 12-15 minutes for
start-up & shut down.

Most of the time is spent in "applying computer settings" ~ 10 minutes and
the remainder in personal settings.

All other WinXP clients load in ~1-2 minutes.

What can I examine to fix this long start-up time (other than go & make the
coffee before getting a cup).

After logon, the system runs just fine and accesses server folders &
printers with no problem nor time degradation.

THX

--

*****************
John Lenz
JohnLenz@newsgroup

"John L" <JohnLenz@newsgroup> wrote in message news:AF4CA904-4897-419B-8CD5-21C356762DBC@newsgroup

> Server: Win2K3 R2 standard - SP1
> Client: Win XP Pro SP3
>
> On this one XP Pro client(10 users network), I get 12-15 minutes for
> start-up & shut down.
>
> Most of the time is spent in "applying computer settings" ~ 10 minutes and
> the remainder in personal settings.
>
> All other WinXP clients load in ~1-2 minutes.
>
> What can I examine to fix this long start-up time (other than go & make the
> coffee before getting a cup).
>
> After logon, the system runs just fine and accesses server folders &
> printers with no problem nor time degradation.

Without specific configuration information about your domain, and going by the symptoms posted, I agree with Meinolf, that this is normally caused by DNS misconfiguration. As Meinolf said, make sure no external DNS, ISP's DNS or the router is being used as a DNS address. This goes for ALL internal machines, not just the DC.

Also make sure that DHCP Option 006 only shows the internal DNS.

Other causes, in conjunction with misconfigured DNS, are: Single label name domain (domain rather than the required minimum of domain.net, etc), multihomed DCs or DCs with RRAS on them (causing multiple interfaces, NICs and/or IP addresses), disjointed namespace (Primary DNS Suffix does not match the AD DNS domain name it is a DC of), and others.

Your ipconfig /alls of the DC and a sample client will help us make an evaluation and recommendations.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
aceman@newsgroup
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

The WinXP PC has hard coded DNS addressses that were not a DNS host. I went
to automatic and all works well.

THX for your help.

--

*****************
John Lenz
JohnLenz@newsgroup

"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:uVLXGYJDKHA.2832@newsgroup
"John L" <JohnLenz@newsgroup> wrote in message
news:AF4CA904-4897-419B-8CD5-21C356762DBC@newsgroup

> Server: Win2K3 R2 standard - SP1
> Client: Win XP Pro SP3
>
> On this one XP Pro client(10 users network), I get 12-15 minutes for
> start-up & shut down.
>
> Most of the time is spent in "applying computer settings" ~ 10 minutes and
> the remainder in personal settings.
>
> All other WinXP clients load in ~1-2 minutes.
>
> What can I examine to fix this long start-up time (other than go & make
> the
> coffee before getting a cup).
>
> After logon, the system runs just fine and accesses server folders &
> printers with no problem nor time degradation.

Without specific configuration information about your domain, and going by
the symptoms posted, I agree with Meinolf, that this is normally caused by
DNS misconfiguration. As Meinolf said, make sure no external DNS, ISP's DNS
or the router is being used as a DNS address. This goes for ALL internal
machines, not just the DC.

Also make sure that DHCP Option 006 only shows the internal DNS.

Other causes, in conjunction with misconfigured DNS, are: Single label name
domain (domain rather than the required minimum of domain.net, etc),
multihomed DCs or DCs with RRAS on them (causing multiple interfaces, NICs
and/or IP addresses), disjointed namespace (Primary DNS Suffix does not
match the AD DNS domain name it is a DC of), and others.

Your ipconfig /alls of the DC and a sample client will help us make an
evaluation and recommendations.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
aceman@newsgroup
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"John L" <JohnLenz@newsgroup> wrote in message
news:7F8DCF40-1804-4EC7-9F6C-D6B41914B5EB@newsgroup

> The WinXP PC has hard coded DNS addressses that were not a DNS host. I
> went to automatic and all works well.
>
> THX for your help.
>

Good to hear things are working well, and for the feedback to let us know.

You are welcome!

Ace