Didn't seem to make a difference.
We believe it may be a hardware issue.
Booting laptop from another system over firewire yields the same results.
Booting the system over firewire on another laptop allows access to the network.
Problem stays with the hardware.
Checked all system updates, changed MTU, and reset the PRAM multiple times. Still no luck.
Main Topics
Browse All Topics





by: pheidiusPosted on 2007-11-30 at 17:12:27ID: 20386508
if they are right about it self assigning tehn might be worth it to go into terminal and do a release/renew. I think it is sudo ipconfig set en0 BOOTP or you could try sudo ifconfig eno down ; sudo ifconfig esudo ipconfig en0 BOOTP n1 up
"The ipconfig set en BOOTP causes OS X to release the address; then ipconfig set en DHCP causes OS X to attempt to get a new address. On some networks, the behavior will basically be the same, but depending on the topology and what\'s going on, you could get very different results doing a RELEASE/NEW LEASE versus a true RENEW.
On the GUI version, OS X has a bug in its behavior where its RENEW is actually a REBIND. Again, this is probably going to get you the same results on many networks, but it\'s not a real RENEW. The difference between a RENEW and a REBIND is that a RENEW is a directed unicast to the original server that gave you the address asking for an extension on the list; a REBIND is a broadcast that you do after you don\'t get an answer on your RENEW (T1 has expired, and T2 has expired). "
I any case I think it could not hurt to do a complete release below the gui level and then reset its new adress
o, by the way looking again at your post, it might be en1 instead of en0 asen0 would be your ethernet port while en1 would likely be your wireless port .perhaps before you reboot the modem you could run ipconfig getifaddr en0 0r en1 as the case may be and see if it is selfassigning a nonworking ip