My D-Link went psycho and I replaced it with a LinkSys. It's not like they're expensive or something.

• Can you flash with an older (known working) firmware?

• After you reset the wireless router, do you need to reinsert settings? (If not, you need to "hard reset" your router: "depressing the reset switch for 30 seconds and then releasing it".)

• Are there any issues with the power supply? (Do you know someone with a similar model of router with whom you can swap supplies to test?)

Alex:

Can you flash with an older (known working) firmware?

I just took a hit to my tender web savvy regions, but I really don't know how to do this.

After you reset the wireless router, do you need to reinsert settings?

No, all previous settings reappear.

Are there any issues with the power supply?

No, it all checks out nicely. Thanks for your help... something tells me maybe wonky firmware? Last update was apparently last January ('05). I d/l'd the newest firmware, and it's in a /bin file. My computer keeps sending VLC player to open it, yet I don't know what app to associate it with...

Merci encore!

I would do a hard reset. A "soft reset" that leaves settings behind can be the source of problems. Try a hard reset, reinsert settings, and see if things improve.

I had a very similar problem with a D-Link I owned a few years ago. It would be fine for a few days and then just go crazy until I gave it a few hard power cycles. My solution was to just get a Linksys; D-Links aren't worth the plastic they're housed in.

I once had a similar problem with a D-Link (non-wireless) router. Upgrading the firmware turned it from an unreliable piece of shit into a paperweight, so don't try that.

It turned out that the problem was a particular machine on the network that was configured to act as a DHCP server (related to having been used to share a dial-up connection on that pc), so it was conflicting with the router DHCP server. I can't remember exactly how I fixed it and the whole DHCP/internet sharing connection thing is very poorly documented by MS, but that may be some clue as to where the problem lies.

Hey, thanks everybody! Upgrading the firmware and doing a long, cold, hard manual reset has seem to have done the trick. Gracias!