In Event Viewer/Systems I have suddenly started getting the following warning: Dhcp 1007 Or Error: Dhcp 1002 Your computer has automatically configured the IP address for the network card with network address 0007E98FAD-- (last ltr's omitted by me). The IP address being used is 169.254,---.--- (last groups omitted). When I checked in Control Panel/Network Connection/LAN the correct IP address 169.254 etc is shown. This seems to be slowing the boot. Anyone know what I can do to change this? Thanks.

Sorry, failed to say I am on a cable modem.

Might find some clues here... http://www.eventid.net/display.asp?eventid=1002&source=dhcp Good luck Krystyna

Krystyna-- Thanks for the response. I have had that site bookmarked for quite a while, and checked it earlier. As with most errors, it gives a lot of possibilities, none of which really seem to apply.

Hi JohnO Did you try the link to Comptech ? http://www.comptechdoc.org/os/windows/wintcp/wtcpdhcp.html Krystyna

Did you look here? http://support.microsoft.com/default.aspx?scid=kb;en-us;313896&Product=winxp That 169.x.x.x. address doesn't look like a router issued ip address but a windows default assigned address. Windows will automaticly assign a ip address if you don't get one from dhcp. Windows assigned ip address won't work for getting on the internet. You don't mention a router so I have to assume this is one pc with cable connect. Do you know your cable's gateway address? Can you ping it? Cause can be bad cable, nic, firewall or configuration. Talk to your cable isp techsupport

Wanderer, thanks. This is one computer on a cable modem, The error just started yesterday. Although I get the Dhcp error in Event Viewer, it doesn't affect anything. It goes online just like it should, running fine. I talked with Road Runner support, and of course, they told me it must be a Windows problem. I read the link that Krystyna posted above, so now I know how it works, but don't know how to fix whatever is broken. I just don't like seeing errors and warnings in event viewer. I've learned to live with the DCOM errors, but I'd like to get rid of this one.