A few months ago I lost the ability to access Regulus, the Cobalt Qube, with telnet and with FTP. I tried all sorts of things, and never did figure out what was wrong.

It's made me feel a bit insecure.

A couple of days ago it occurred to me that the ftp/telnet failure coincided with the time when I changed my LAN from using 192.168/16 to 169.254/16.

So this evening, just for the hell of it, I tried changing the LAN IP of Regulus back to 192.168, and also Alcyone. And you know what? Now I can telnet and ftp again.

I wonder why? Probably it's because of an obscure firewall rule I set up years ago after Regulus got hacked one time. But there are over 500 rules, and scrolling through them in pages of 25 is massively painful because the code takes about 45 seconds per page to refresh.

So anyway, now I've changed Arcturus (the torrent computer) and Deneb (the Windows Home Server) to 192.168. I next need to change Saten (the Slate 500).

Then I need to find the documentation for Railgun, the Wifi hub, and figure out how to reset  it. I cannot figure out what administrative password I set up for it, and it needs to be switched, too.

I think that the reset is a button inside a deep hole. The documentation will tell me.

(Please note that this post is not a request for advice.)

UPDATE: In fact, FTP works better than it did. Used to be that making the initial FTP connection took 30 seconds. It was some sort of timeout; Windows was trying one thing, that didn't work, and then it switched to something else that did. I never understood what was going on, and never did figure out how to fix it.

Whatever it was, it ain't any more. FTP starts up instantly now.

Probably Microsoft fixed it in one of the patches in the last few months.

UPDATE: Saten is fixed. So only Railgun yet needs to be updated. But it isn't urgent; it's routing WiFi and ethernet traffic fine.

Posted by: Steven Den Beste in Site Stuff at 07:38 PM | Comments (10) | Add Comment
Post contains 354 words, total size 2 kb.