[Solved] SSH over Putty: connection refused

[MaverikCH]

I recently buyed a new B3 and upgraded it over usb stick and have done the web update to 2.4.2.
for some unkown reasons i can't access my b3 over ssh.

my created user has Shell access activated.
well, i'm planing to boot up over usb stick with rescue modus.
can you tell me which files i need to check?

[nobody]

i can't access my b3 over ssh.

this is WAY to vague for anyone to respond to. Be more accurate on what does work and what does not, and what the exact error message is.

[MaverikCH]

well, the thread given title is the error message gives me. i really can't provide more than given. i think some configuration files (actually uknown to me) on bubba have some deny access lines written. if you could tell me which files to check, i'll find out what is configured wrong - even i didn't actually changed any files since upgrade.

hope some spintscreens provide my lines:

Putty: servername and port given. more should not be needed resp. was not needed connecting a b2.

ScreenShot017.jpg (44.57 KiB) Viewed 40694 times

Connection refused error message

ScreenShot018.jpg (27.19 KiB) Viewed 40694 times

My User with Shell access configured. You also see that my custsom bubba servername works.

ScreenShot019.jpg (82.33 KiB) Viewed 40694 times

[Gordon]

Most likely the message refers to the corresponding winsock error 10061. So what this says is that the service is running *and* is responding, but is actively denying you access to it. I think someone mentioned an issue with the hosts.deny file a while back, but I'm not sure what the outcome was. One thing I can imagine is that the paranoid setting got enabled somehow, but that should not give you troubles if you allowed the B3 to hand you a DHCP address (and thus be a resolvable peer).

[nobody]

Thanks, this helps a lot really. I'd start with looking at /var/log/auth.log. The /etc/hosts.deny is not actively filled by the default installation of the b2/b3, and in that distro the paranoid line is commented out. But it's worth having a look there too. You can safely comment out every line in that file for testing purposes.

[MaverikCH]

only lines i get in auth.log are these:

Code: Select all

May 29 20:40:01 joseserver CRON[22536]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:40:01 joseserver CRON[22535]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:40:01 joseserver CRON[22534]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:40:01 joseserver CRON[22536]: pam_unix(cron:session): session closed for user root
May 29 20:40:01 joseserver CRON[22534]: pam_unix(cron:session): session closed for user root
May 29 20:40:02 joseserver CRON[22535]: pam_unix(cron:session): session closed for user root
May 29 20:45:01 joseserver CRON[22590]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:45:01 joseserver CRON[22589]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:45:01 joseserver CRON[22588]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:45:02 joseserver CRON[22590]: pam_unix(cron:session): session closed for user root
May 29 20:45:02 joseserver CRON[22588]: pam_unix(cron:session): session closed for user root
May 29 20:45:03 joseserver CRON[22589]: pam_unix(cron:session): session closed for user root
May 29 20:50:01 joseserver CRON[22638]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:50:01 joseserver CRON[22637]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:50:01 joseserver CRON[22636]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:50:01 joseserver CRON[22638]: pam_unix(cron:session): session closed for user root
May 29 20:50:01 joseserver CRON[22636]: pam_unix(cron:session): session closed for user root
May 29 20:50:02 joseserver CRON[22637]: pam_unix(cron:session): session closed for user root
May 29 20:55:01 joseserver CRON[22664]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:55:02 joseserver CRON[22662]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:55:02 joseserver CRON[22663]: pam_unix(cron:session): session opened for user root by (uid=0)
May 29 20:55:02 joseserver CRON[22664]: pam_unix(cron:session): session closed for user root
May 29 20:55:02 joseserver CRON[22662]: pam_unix(cron:session): session closed for user root
May 29 20:55:03 joseserver CRON[22663]: pam_unix(cron:session): session closed for user root

i checked it over web frontend

Auth.log

ScreenShot020.jpg (178.23 KiB) Viewed 40660 times

i will check the file /etc/hosts.deny when i managed to set up an working rescue system usb stick...

[MaverikCH]

did reinstall of bubba with last usb-stick version 2.4.1.1
and bubba.cfg settings as following:

Code: Select all

Format=0
Partition=0

accessed http://b3/ and recreated my joseklee user with ssh access

putty ssh connection works and i am able to login successfully:

Putty Security Warning

ScreenShot021.jpg (51.08 KiB) Viewed 40629 times

Putty ssh session

ScreenShot022.jpg (42.6 KiB) Viewed 40629 times

will now rename back my server and upgrade to 2.5

[MaverikCH]

* renamed my bubba back to joseserver
* set my workgroup
* upgraded successfully without any errors to 2.5
* disabled services i do not need
* customized admin password

and my putty access is still working:

putty working with customized servername

ScreenShot023.jpg (45.51 KiB) Viewed 40625 times

again a reinsstall solution wihtout knowing what was the cause