I have remotely accessed my computer for almost two years using dyndns and port forwarding with tomato. In the past I have updated my firmware over Windows Remote Desktop (uploading from the remote computer, locally connected to the router by Ethernet). Today I updated Tomato to 1.26 over remote desktop. After updating, I lost connection (as expected, as the router rebooted). But I could not get back in to the remote computer, nor could I access the router remotely over HTTPS. When I got home (luckily I wasn't in another country), the only thing that looks different is that the dyndns.org update failed with the following message: Friday, November 27, 2009 4:22:04 PM: Unknown error (-1). (1/3: Automatically retrying in 16 minutes) I can remote desktop in using the IP address---now that I'm actually at the router and know what it is! So is dyndns down, or does Tomato 1.26 have issues updating dyndns? Surely after all these months using dyndns, it wouldn't coincidentally go down at the moment I upgraded to 1.26, would it? There are no error messages in the logs. Thanks for any help.