Tom helped me move the server - ash.datamantic.com - to the data center. I took the old server out, put in the new one, fired it up and everything seemed to be okay. I had put in the new network configuration back at headquarters. But then I tried to SSH into tulip (the current server located in a different data center,) and it wouldn't recognize my password. Weird. ifconfig seemed to indicate that ethernet was up and connected. And getting a response from tulip (even a rejection) further made me believe that things were working. But I couldn't account for the inability to log in.
But luckily (I am learning) I didn't waste tons of time trying to figure out what was wrong. I say luckily because, as I suspected, everything really was fine. I'm back home now I can ssh into ash with no problem. So everything seems to be working. I'll have to try to figure out the weirdness about not being able to get a secure shell going out though, but it's not a big deal at the moment.
So I'm a little behind schedule, but at least it has finally happened.
Tom took some pictures.
Okay, just for the record, I'm pretty sure the ssh problem I was seeing is a DNS issue. Since the host I was ssh'ing from doesn't have a proper DNS entry yet the remote server is rejecting the authentification step. So as soon as I get DNS setup it should then work.
Um, no. Turns out it wasn't a DNS issue. The other server is just very old and only supports version 1 of the SSH protocol. So from my new server I have to ssh -1 user@server.example.com where the -1 forces it to use version 1.
Learn something every day.
|
But luckily (I am learning) I didn't waste tons of time trying to figure out what was wrong. I say luckily because, as I suspected, everything really was fine. I'm back home now I can ssh into ash with no problem. So everything seems to be working. I'll have to try to figure out the weirdness about not being able to get a secure shell going out though, but it's not a big deal at the moment.
So I'm a little behind schedule, but at least it has finally happened.
- jim 11-23-2005 12:08 am
Tom took some pictures.
- jim 11-23-2005 5:22 pm
Okay, just for the record, I'm pretty sure the ssh problem I was seeing is a DNS issue. Since the host I was ssh'ing from doesn't have a proper DNS entry yet the remote server is rejecting the authentification step. So as soon as I get DNS setup it should then work.
- jim 11-25-2005 6:37 pm
Um, no. Turns out it wasn't a DNS issue. The other server is just very old and only supports version 1 of the SSH protocol. So from my new server I have to
where the -1 forces it to use version 1.Learn something every day.
- jim 2-14-2006 11:24 pm