Up until yesterday shortly after lunch, my home network was managed (routed, firewalled) by a Linksys WRT54G wireless router. I never enabled the wireless portion of the device because I don't need it in my little crackerbox palace of an apartment, plus there's far too much metal in the wall studs and other support structures, including the door and window onto the terrace, so I just disabled it to keep things utterly shut tight and secure. Why'd I buy a wireless router in the first place? Suffice it to say, I didn't know the place was that metallic when we first moved into it. Be that as it may, about eight or so years and three firmware revisions later, the thing finally gave up the ghost, as they say, and is now sitting in a truck on the way to a landfill somewhere--I no longer have the device. This is key to understanding my problem and why it cannot be suggested to reconnect the device in order to solve it. Yiskar has been saide. I have buried my dead. OK, the 54G was replaced with a nice new (vintage 2008) DLink DIR655n router, all ports operating at a gigabit, as opposed to 100mb for the Linksys box. The Linksys router's home address was 192.168.1.1, while the DLink's is 192.168.0.1. Two devices on my network have static IP addresses--a printer and a NAS box. Everything else is DHCP and has reserved an address on the new 192.192.0.1 network. This means now that I cannot communicate at all with either the printer or the NAS box until I either change their address or change the rest of thenetwork devices' addresses back to the old address base (192.168.1.*) I thought I would simply change the address of the router itself from 192.168.0.1 to ..1.1. Every time I try to do this, the router does its thing, reboots, and returns with the ..0.1 address. Anyone with experience with the DIR655 router who knows how to get past this, greatly appreaciated to hear from you asap, publicly or privately. TIA