Question : DHCP client not pulling address correctly after boot

system: Windows XP Pro SP2 w/ all current updates, Pentium M 2GHz, 768MB RAM
lan: Realtek RTL8139/810x Family Fast Ethernet NIC
wlan: Intel(R) PRO/Wireless 2915ABC Network Connection
router: Linksys WRT54GS

The problem is the laptop can only pull an address from the DHCP server at Windows start-up. If an ethernet cable is plugged in to the laptop when it boots, it has an IP address by the time it can be verified with ipconfig. However, if I release and then try to renew the address it times out with the usual "limited or no connectivity" error. The wireless adapter can never get an address because it doesn't start pulling an IP address until well after Windows start-up. The ONLY time I get a dynamic IP address is on the wired interface at Windows boot after a complete restart (logging off and then back on does not give me an address). This has been tested with many other known working routers.

If I set up a static IP address on either the wired or wireless adapter in the same subnet everything works fine, so I don't think this is an adapter hardware issue. I fully believe it is a software problem.

I have tried resetting the TCP/IP components using netsh, also using WinSockFix. I have uninstalled both adapters on the laptop and reinstalled them. Other devices can pull IP addresses off of the same router with no problem.

This has me stumped. The laptop that this is afflicting is the system for on-site tech services, so you can imagine this is a pain. Thanks in advance for any assistance!

Answer : DHCP client not pulling address correctly after boot

The only other suggestion i can think of is to un-install Service Pack 2 (which will uninstall everything Windows Firewall-related).  I swear this has something to do with the firewall.  If it had anything to do with the IP Stack, it wouldn't pull an IP when plugged in.  Do you have Norton Internet Security or anything like that running?  Those have built-in software firewalls that have been known to conflict with wireless Internet as well.  Is there any possibility that its a signal-degradation issue?  Or is the router immediately close to your computer...