Major boot time increase on XP Pro after applying static IP addres

[Guest]

I had to assign a a static IP to an end users machine, upon doing this the
boot time has increased by nearly 3 minutes. It seems to hang on the
"Applying Personal Settings" boot window. If I take out the static IP and
bring it back to DHCP it boots beautifully. This happens on all users
including admin upon logging into my network. If I boot straight to the
machine it boots fine.

What is going on? This amount of time to boot is unacceptable.
2.8 GHZ P4
512 MB RAM
XP Pro latest and greatest updates (No SP2 as of yet)
Win 2003 SBS network

BTW my 2000pro machine that I work with is also on a static IP and I have NO
problems with boot times.

 

[Guest]

FIXED, But don't understand why this worked. I COMPLETELY removed all the
settings in the network config and left the domain. I rebooted, re-setup all
of the settings and now it boots flawlessly. Don't know why this would solve
the problem but I am not complaining.

 

[Ron Lowe]

I had to assign a a static IP to an end users machine, upon doing this the
boot time has increased by nearly 3 minutes. It seems to hang on the
"Applying Personal Settings" boot window. If I take out the static IP and
bring it back to DHCP it boots beautifully. This happens on all users
including admin upon logging into my network. If I boot straight to the
machine it boots fine.

What is going on? This amount of time to boot is unacceptable.
2.8 GHZ P4
512 MB RAM
XP Pro latest and greatest updates (No SP2 as of yet)
Win 2003 SBS network

BTW my 2000pro machine that I work with is also on a static IP and I have
NO
problems with boot times.

Sounds like DNS failure.

Did you also specify DNS servers manually?
You will need to, since DHCP isn't doing this any more.

Go back to DHCP, and then do an ipconfig /all
Note down what values for DNS, WINS and Gefault Gateway have been issued.

Enter these in the statically assigned machine.

( Windows 2000 is more tollerant of misconfigured DNS than XP is. )

 

[Doug Sherman [MVP]]

Also, depending on how DHCP was configured, this problem may have resulted
because the statically configured XP machine was unable to update its DNS
record. Usually you can solve this by maually deleting DNS host and PTR
records. See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;816592#31

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP