Rickresource Rickenbacker Forum

I can't connect to http://www.rickenbacker.com/

Apparently. I've gotten in a couple of times today, but mostly it times out. It was having problems yesterday morning (before they opened) as well.

Just worked for me.

As of 5:40 PM CST USA corporate was working. They must've been busy shipping out geetars.

JimK

The down time was most likely due to maintenance and / or updates on their server.

Maybe they're updating it to announce the 4001SV68.

Its been up and down sporadically since Sunday. Mostly up, though. Maintenance, I'm certain.

Must be some serious maintenance, seems to be down again this morning...

The T1 used for the website has been intermittent, no doubt due to the rain we had over Thanksgiving. The copper infrastructure in this end of town is over 100 years old they tell me. There's fiber in the streets but the owner of it went bankrupt some time back and it's been dark for years now.

We have other T1 circuits but they're rather busy for some other things, our outside IP addresses are pretty much used, and I thought they'd get this line dried out faster than the DNS propagation time anyway.

You can also always try www.rickenbacker.net which, as I recall, uses a different circuit.

I tried this morning and it is asking for my user name and password. I tried the forum password and no luck.

dlandau wrote:I tried this morning and it is asking for my user name and password. I tried the forum password and no luck.

Just got the same from both .com and .net

rikk wrote:

dlandau wrote:I tried this morning and it is asking for my user name and password. I tried the forum password and no luck.

Just got the same from both .com and .net

Good to know I'm not the only one. At first I took it kind of personal.

I've seen that before (yeah, I got the login/password thing too), seems to me the answer was that they were doing some sort of maintenance (really) when the password thing happens.

The domain controller self-destructed yesterday, so internal DNS and authetication doesn't work. I just grabbed a new server out of the rack in my home, have it in the car, and will install it later this morning. I guess it's time to have a secondary domain controller . . .

Combined with the T1 problem, which is still open ticket, it's been a fun week.

I guess it's time to have a secondary domain controller . . .

A Big +1 to that, and giving it a secondary DNS role wouldn't be a bad idea either.