?

Log in

No account? Create an account
Lord Yupa

February 2010

S M T W T F S
 123456
78910111213
14151617181920
21222324252627
28      
Powered by LiveJournal.com
Lord Yupa

Frustrating Windows Problems.

Okay, this is the most annoying things I've run into in ages.

I have not installed anything in the past week or two, and for no reason that I can figure out, I sat down to my WinNT box and attempted to Secure Shell (ssh) to my Linux box. The reason for this is that the monitor for my Linux box is currently dead, so this is my only easy way to access it.

Well, upon attempting to connect, I get the error:

Unable to open connection:
Protocol initialisation error


I don't have a clue what that is supposed to mean, nor why it's suddenly started up. You want to know what else is really odd? When I first got this, I tried a different version of the program. Same thing. So, I tried a different windows ssh program (MindTerm, it's a Java based ssh client) and I got the same thing.

At this point, I'm really getting annoyed. So, I've been thinking about reinstalling NT for a while now anyway, 'cause there's a lot of things screwed up on this box right now. I figure this is as good a time as any. So, I've just finished reinstalling, and guess what....putty still isn't working.

I'm starting to get pissed here, and it takes a lot for that to happen.

If anyone has any suggestions, knowing that I'm a computer user who is well 'above average' in knowledge (don't suggest rebooting. ;-), I'd love to hear it.

I'm running NT 4, Service Pack 6a, IE 5.5, Office and Visual Studio are not yet installed, I'll prolly get around to putting them back tomorrow.

UPDATE: I've been doing a ton of digging around on the web, searching mailing list archives, and sniffing in Deja News archives. I've discovered two things.

First of all, I can still use ssh to connect to some machines, just not all. I don't know why. Secondly, there's a possibility it might be a server related issue, because a friend of mine using the standard ssh client, on a NetBSD box, was also unable to connect. I'm gonna move my monitor over and check things manually tomorrow, I think.

Sometimes, I really hate computers.

Comments

A funny thing used to happen to me when I tried to ssh home from school - same error message.
So I would ssh to a machine where I had a shell, and then ssh home from there.
The weird thing is that the school net was the -only- place where I got that error.
Dunno if that's related at all.

Re: Protocol initialization error

Well, initialize the protocol already!

Seriously, it could be a conflict in what encryption type you want.

Or, if it was FreeEvil, install the RSA crap from ports. (don't remember if that was the error I was getting or not)

Anyways, is anything logged on the sshd end?