Problem with auto-assigned DHCP address

[Max]

Hi,

I've been having this problem for ~2 weeks now and it's really bugging
me. I don't see what could have changed in my PC configuration except
for the latest Windows Updates (824105 and 824146). I de-installed them
without better success and even re-installed a bunch of other products
that I thought could be the source to my problem.

My problem is that it takes about 1 minute for my PC to come up with its
auto-assigned DHCP address when I start it up. Since this "feature"
doesn't run in parallel with other services, all subsequent services are
also delayed until my network card has an IP address.

Is there a way to limit the time it takes for Windows to realize there's
no DHCP server at the end of my network cable and assign this
auto-assigned IP address much more rapidly ? I searched around and could
not find any settings that seem to control this.

My setup is as follows:
- ThinkPad A31
- Windows XP Pro + SP1 + all updates
- 1 integrated Intel PRO/100 VE network card with latest driver
- Network settings only have TCP/IP and VMware Bridge protocols enabled
- All NetBios, Sharing, Computer Browser, ... are disabled

I completely removed and re-installed:
- RAS PPPoE
- VMware
- Local Area Connection
- Anti-Virus

Problem is still there.

Here's my Event log entries. Notice the time difference between the
Warning on the fourth line and the Information on the following line:

Type Date Time Source Category Event
Information 28.09.2003 14:31:01 RemoteAccess None 20158
Warning 28.09.2003 14:30:58 Dhcp None 1007
Warning 28.09.2003 14:30:51 Dhcp None 1007
Warning 28.09.2003 14:30:51 Dhcp None 1007
Information 28.09.2003 14:29:52 Tcpip None 4201
Information 28.09.2003 14:29:52 Tcpip None 4201
Information 28.09.2003 14:29:50 VMnetx None 34
Information 28.09.2003 14:29:50 VMnetx None 34
Information 28.09.2003 14:29:50 VMnetx None 34
Information 28.09.2003 14:29:50 VMnetx None 34
Information 28.09.2003 14:29:50 VMnet None 20
Information 28.09.2003 14:29:50 VMnet None 34
Information 28.09.2003 14:29:50 VMnet None 34
Information 28.09.2003 14:29:50 VMnet None 34
Information 28.09.2003 14:29:50 VMnet None 34
Information 28.09.2003 14:29:50 VMnet None 34
Information 28.09.2003 14:29:45 E100B None 8
Information 28.09.2003 14:29:44 E100B None 5
Information 28.09.2003 14:29:41 VMnetx None 34
Information 28.09.2003 14:29:41 VMnetx None 34
Information 28.09.2003 14:29:41 VMnetx None 34
Information 28.09.2003 14:29:48 eventlog None 6005
Information 28.09.2003 14:29:48 eventlog None 6009
Information 28.09.2003 14:29:41 VMnetx None 34
Information 26.09.2003 22:14:38 eventlog None 6006
Information 26.09.2003 22:14:37 Service Control Manager None 7036
Information 26.09.2003 22:14:37 Removable Storage Service None 98

Here's the content of the Warning I get for my network card:

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1007
Date: 28.09.2003
Time: 14:30:51
User: N/A
Computer: HOMEPC
Description:
Your computer has automatically configured the IP address for the
Network Card with network address 00D059DAzzzz. The IP address being
used is 169.254.yyy.zzz.

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

 

[Jason Tsang]

Assign the computer a static ip so that it won't wait for the DHCP timeout
to occur.

For example, giv eyour computer an ip of 192.168.1.254, subnet mask
255.255.255.0

That will fix your issue.

 

[John Steele]

Assign the computer a static ip so that it won't wait for the DHCP timeout

to occur.

For example, giv eyour computer an ip of 192.168.1.254, subnet mask
255.255.255.0

That will fix your issue.

Try a DHCP server!

I have been using this very simple one for years on W98, WMe, Win NT and XP
http://ruttkamp.gmxhome.de/dhcpsrv/dhcpsrv.htm

John Steele

 

[Yves Leclerc]

Most broadband routers now come with a built-in DHCP server.

Y.