DHCP warning in system log

I installed a router and am now getting a warning message in the system log.
The event ID is 1003
The description is:Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address xxxxxxxxxxxx. The following error occured:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

The router is an older (BEFSX41) Linksys wired router with the most current firm ware and is working fine. I am using the "opendns" server address'.
The "client lease times" setting in the router is set to renew every day.
The DHCP server setting in the router is disabled

The DHCP Client is set to automatic under services and is started.

Any ideas?

 

If you open cmd (start->run, type cmd and hit enter)
What happens if you type ipconfig /release, and then ipconfig /renew?
This should renew your ip. If this doesnt work, maybe a local firewall software is blocking DHCP.
NB! if renew doesnt work, you are without internet until you figure it out

 

release and renew works fine. I have internet connection. Thats whats strange the warning says it can't renew the address but it is. I have re-enabled the DHCP setting in the router because the other (win98) machine in the house cant renew its address with it disabled. BTW both computers on the network are getting different IP address' and both have no connection problems.

 

Is yuor network card aslo configured to recive DNS automatically?

Also take a look here:
MSW2KDB

From another site:
"In my case two clients with automatic DHCP were giving the same error but with no apparent problems with the network. With "flushdns" and "registerdns" using "ipconfig" the problem seems to be fixed. In addition, the DHCP server gave error id 30022 for IPBOOTP which ostensibly shows hardware reading problems on the nic which serves the dhcp. However the above solution solved this one as well. "

 

Its an onboard ethernet and no it is not configured to receive dns automaticly
Thanks for that link. It didn't help me but thank you just the same.