Hi all,
pasted below is the output from running the ssh -vvv username@192.x.x.x command on the problem box

debug2: service_accept: ssh-userauth

debug1: SSH2_MSG_SERVICE_ACCEPT received

debug2: key: /root/.ssh/identity ((nil))

debug2: key: /root/.ssh/id_rsa ((nil))

debug2: key: /root/.ssh/id_dsa ((nil))

Can someone please help me understand what the above entries mean???

Any help will be greatly appreciated.

Thanks in advance...

Aloesi

Hello,

Have a look at this thread here at LQ. That user had quite a similar problem.

Kind regards,

Eric

Hi Eric,
Thanks for replying. Correct me if am wrong but i take it from reading previous posts that the need to generate a key as suggested by the thread you directed me to is if you want to connect via ssh but without a password.

My problem is from any machine within the LAN, i cannot connect via ssh to this freebsd box which is on our DMZ. Other boxes on the same zone cannot ssh to it either. Also telnet via port 25 is not possible but telnet via port 22 is. From inside the machine (accessing it via its webip), one can basically reach any other machine with ssh and telnet.

M trying to pinpoint what could be the cause of this problem.

Any ideas???

Thanks in advance.

Aloesi

Hi,

If none of your computers can SSH into that machine, which you say is in your DMZ, then I'd first look at your firewall and routing and next to the sshd_config on the FreeBSD box and see if it accepts connections from the IP range of your LAN (since it will be different than from your DMZ). Also if you are connecting as root, do you have the PermitRootLogin set to yes on the sshd configuration?

The errors you get are an indication that authentication is failing, and ssh is trying other authentication sequences as far as I know.

Kind regards,

Eric

have you generate the key ?
at least one of rsa or dsa key have to generated for make the server authenticate to the clients.
try explore the rsa-keygen command.

Wish U luck bro..

Hi all,
Issue was resolved. Later found that telnet through port 25 was also taking it's time.

Updated a script on the server that disabled RDNS that seemed to be causing the server to be really slow and timeout eventually hence the inability to SSH and telnet on port 25.

Server is fine now.... can SSH, telnet etc just like before.


Thanks everyone for the help and suggestions and cant wait to be able to post again with a question or to help someone else.

Thanks again.
Aloesi

Hello,

Glad you figured it out. Have a nice day.

Kind regards,

Eric