[butchfoote]

We have a wonderful G3 Wallstreet that is used by one of the kids. Primary usage is Firefox, iTunes, iPhoto and Appleworks. It uses a wireless card / Airport to talk to a Linksys WRT54g router. That has worked fine as has its ethernet port when needed.

It's at OX X 10.2.8 and has been running fine for many months. I replaced the PRAM battery last fall, upgraded the HD to 32Gb and did fresh installs of everything.

Suddenly it won't communicate over its Ethernet port or wireless card.

I rebooted once last week and the problem went away. Last night it came back and persists beyond restarts.

During restart the network initialization seems to take a very long period of time. When the machine finally completes the restart, and I check the Network system preferences, I notice that the IP address is one of those self-assigned defaults (169.......).

I can't figure out what to go tweak to make it work again.

Are there any preference files I could throw away and hope for improvement. Other suggestions???

Thanks in advance

[Gossamer]

1. Applications > Utilities > Disk Utility ... Repair Disk Permissions
2. Remove and reinsert the card
3. Check Apple's site for the latest Airport drivers and reinstall them
4. Try booting without the card installed and see what happens, then restart again and put it back in

I don't know if any of those will work but they should give you a starting point.

[butchfoote]

I ran the Disk Utility to repair permissions. I think that helped and now the Network Initialization seems to move right along when rebooting.

However, Mac OSX is still failing to get a DHCP address from the local router.

I can ping other Macs on the subnet, but the IP address that Mac OSX is now using is the 169.x.x.x default, self-assigned address.

THIS JUST STARTED HAPPENING ...

So again, what can I throw away that is probably corrupted? internetconfig.plist or something?

Thanks in Advance

[tinkered]

Sounds like the DHCP lease is not being released and renewed properly. This might be better for the networking forum.

I noticed this happens sometimes with my pismo after it wakes from sleep after a few days. Have you tried power cycling your router that is issuing the DHCP leases? Routers run on software too, and need a power cycle sometimes too. Although, in my case I found that if I logged into my router from another computer, that would resolve my DHCP lease issue--strange, inexplicable, but functional.