XP Pro IP Config Problem

I have two computers here that use one cable connection. This computer (called laptop from hence forth) is connected wirelessly to a router, which is (duh) connected to the cable modem. The other computer (called desktop from hence forth) is wired to the same router. Obviously, this computer works. The other won't access the internet. And it's because it won't renew it's IP address.

I tried ipconfig /renew and the windows XP "Repair" function. Both gave me errors. The IP config for the desktop is as follows:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 169.254.20.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

The error that the desktop gets when using ipconfig /renew is as follows:
An error occured while renewing interface Local Area Connection: Unable to contact your DHCP Server. Request has timed out.

And finally, the ipconfig for the laptop is as follows (I guess for comparison):
Connection-specific DNS Suffix . : cablerocket.net
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Any idea what's wrong? Thanks for any light you can shed on this problem.

[Prometheus]

Configure your router make sure it is broadcasting.

You'll have to forgive me. I'm kinda new to all this home networking stuff. What do I need to do to ensure it is? Obviously it's broadcasting to my laptop but what about the desktop?

Nevermind, it managed to fix itself somehow. I took the desktop and hardwired it to the modem, which worked, and put it back to the router, and it fixed itself. I tried resetting everything last night and double-checked all the connections (and everything checked out), but for some reason doin it a few minutes ago cured all. Thanks for the help though prometheus. Much appreciated.

[Jason425]

I love it how things just fix themselves when you do something stupid.. happens all the time with printers for me..

[vee_ess]

Well, there's always a reason, we just don't always understand it. I'd like to guess, though, that the router is not configured as a DHCP server for the wired ports, but it is for the wireless ports. This would mean that when the modem assigned an IP address to the desktop of some 192.168.0.XXX IP. Then when the desktop was connected back to the router, there was no more need for the router, (which wouldn't be assigning IP's to wired connections,) to assign an IP, because the computer had already been changed to a 192.168.0.XXX IP.

[Prometheus]

if only we could see the windows xp source

[vee_ess]

You don't need to see the XP source, you just need to go into the router configuration and see if it is functioning as a DHCP server and if the IP of the desktop is now on the IP range that the router is config'd for. :P

[Prometheus]

still

I would face the law suits to release the XP source if i had the chance besides all the opensource junkies would like pour money into legal defense to who ever did release it

Linus would faint lol