I recently had my MacBook sent in for repair. While I was waiting for it to get back, I booted my backup drive through my Mac Pro so I could continue working. Once I got the MacBook back and I restored from my backup, AirPort refused to turn on.
Eventually I found out that Leopard makes a few changes to network device mapping, and doesn't always clean up after itself. It seems that going from one Ethernet port and one AirPort to no AirPort and two Ethernet ports and back again confused it greatly. This thread on Apple Discussions goes over the same problem, in a lot more detail.
To work around it, I had to delete AirPort in the Network System Preferences pane and recreate it -- making sure to remove the AirPort icon from the menu bar before hitting apply (restoring /Library » Preferences » System Configuration from Time Machine should also work). It also seems I would have had this problem if I booted the MacBook into Target Disk Mode and then booted the Mac Pro off it.
Moral of the story: Be weary of booting different classes of machines off the same drive.
Mac OS X Hints
http://hints.macworld.com/article.php?story=20080227061320185