MacBook Pro can't obtain IP address from Linksys WRT54G v2 router

Question

I believe I am having the issue described in the article below:
http://docs.info.apple.com/article.html?artnum=304817
In a nutshell, AirPort seems to be seeing the wireless router just fine, but internet connect is a no go.  The router is a Linksys WRT54G v2, which should - SHOULD - work w/ my brand new MBP C2D 17", based on the reports I have seen in other threads here.
In the Network Status tab of the network pref pane, the message is:  "Airport is connected to the network linksys.  Airport has a self-assigned IP address and may not be able to connect to the Internet."  This is in line with the Apple tech doc cited at the link above.
I am starting a new thread on this because, unlike many of the other folks who are having problems connecting wirelessly, my actual wireless connection seems to be rock solid (AirPort connects to the Linksys instantly, and shows up as full strength with no apparent dropouts).  The problem seems to be with the IP address, as the MBP can't/won't pickup anything other than its self assigned IP when connecting.
Here are the things I have tried so far (most of which are probably irrelevant as it turns out, b/c the actual wireless connection has been fine - just not the TCP/IP stuff):
1. Updated to latest firmware in router.
2. Tried switching to different wireless channel (ch. 11 in this case, based on reports in other threads).
3. In Linksys settings, changed beacon interval to 50 and lowered packet thresholds as described in another post (can't find the link right now).
4. Formatted and re-installed OSX onto the MBP.  Did NOT use Migration Assistant this time (since others were apparently having problems due to out of date prefs and PowerPC related items copied over from older machines).
5. Updated to latest version of OSX Tiger (10.4.8 with all patches installed) using a wired Ethernet connection to the internet.
6. Downloaded and installed the AirPort Update patch 2006-002 located at:
 http://www.apple.com/support/downloads/airportupdate2006002.html
7. Repeatedly trashed all AirPort-related keychain items and the SystemPreferences folder in Root/Library/Preferences.
8. Repeatedly trashed and re-created a new wireless location using Network Assistant.
9. Salaam thrice towards Cupertino, wave rubber chicken and bathe self in pigs' blood while humming a continuous medley of Mac startup chimes from the last two decades.
Just kidding about #9, mostly.
I am starting a new thread about this because I believe my issue is OS related.  The AirPort hardware seems to have a a full-strength and non-intermittent connection to the Linksys router.  The problem appears to be w/ the (in)ability of OSX to negotiate an IP lease with the Linksys box.
I am posting this to the Linksys forum as well, but do not believe this to be a Linksys issue.  I have two other PowerPC-based Mac laptops in my office, both of which connect flawlessly to the Linksys.  (I'm typing this from one of them.)  In fact, I have torture tested my new MBP with several other wireless routers with the same result - MBP will not connect, while both of the PowerBooks work like a charm with the other routers in question.  Therefore, it surely seems to me like the common denominator here is definitely the MBP and not the router.  I realize that in the support doc at the top of this post, Apple claims it is the responsibility of the router manufacturer, but I just cannot buy that line - based on the fact that EVERY OTHER LAPTOP that I own works great with the Linksys except for my shiny new MBP.
Beautiful machine otherwise and I really can't wait to get it working, but this is a SERIOUS pain in the you know what.
At any rate, if anyone has any ideas as to what to try next, I would love to hear about it.  I will be calling AppleCare again first thing tomorrow morning, but it always seems the users are better informed than the Apple guys.
Thanks in advance for any suggestions.

Answer 1

if other computers connect to the router just fine , doesn't seem to me a router problem then .. the only thing i can think is to try connecting to a different network and see whether it does any good to u...can't help much if it's an OS related issue...