I had just installed epic4 onto my second computer and now when I try to ssh into it, i get this mesage

root@darkstar:~# ssh -v -v 192.167.0.3
OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7b 10 Apr 2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.167.0.3 [192.167.0.3] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
ssh_exchange_identification: Connection closed by remote host
debug1: Calling cleanup 0x8063320(0x0)


normally it just gives me a password prompt for the user I ran the ssh command with, but now it gives me this, does anyone know what my problem is?

This is a longshot but make sure sshd: ALL is in your hosts.allow file. If that doesn't help, comment out the entire hosts.deny file and try.

By the looks of it, it appears that you haven't created your keys as it complains (-1) on id_rsa and id_dsa. It also appears that you've disabled V1. Try ssh with version 1. Check your sshd_config.

SSh is also fussy about permissons on .ssh directory files. If they are global readwrie then it will moan.

Putting ssh: ALL in your hosts.allow is a bad idea. That opens you up to ssh logins from anywhere. You are better off using something like
ssh: your-hosts-name (or IP address)
You could also use:
ALL: *.yourdomain
to open up any running services to your local network.
or
ALL: 192.168.0.101, 192.168.0.102 (for specific localhosts)

When you use a service like this it first checks the hosts.allow file. If the machine, or ip address, etc. is listed in hosts.allow then you get access. If not, it then goes to hosts.deny to see if it is explicitly denied. That makes using
ALL: ALL
in your hosts.deny file a good idea. That locks out anyone you didn't explicitly list in *.allow.

i figured out my problem, after posting this my network stoped working all togeather, at first i thought it was the crossover cabel, but when i tried (in windows) the onboard LAN adapter for my better computer, things worked. so I ended up installing the NFORCE drivers onto slackware and now i can ssh into my other computer with no problem.

although as i said its an onboard LAN, and since im on a cluster theres alot of idle trafic, i have seen CPU tems dramatically increase since the switch, so im gona have to buy a new lan card soon.