SSH not working

Floob

Well that build isnt supported, but what does it give the IP as when you type "ifconfig" ?

Beretta9

At the top in red where it says ip address is 192.168.2.110.
After I typed the command if config, where it says wlan0, the inet addr is 192.168.2.110 Bcast 192.168.2.255.

Beretta9

@Floob I've tried to login using:
Host 192.168.2.110
Username pi
Password raspberry
Port 22
This didn't work.

Meneer Jansen

@Beretta9 said in SSH not working:

At the top in red where it says ip address is 192.168.2.110.
After I typed the command if config, where it says wlan0, the inet addr is 192.168.2.110 Bcast 192.168.2.255.

Wlan0? That means WiFi. WiFi connection on the Pi is quite quirky. I'd try to connect via cabled network and if that succeeds that I'd try wireless. I never succeeded to get a stable wireless connection to my Pi. Wired ethernet however: no problem.

Success. :-)

Beretta9

@Meneer-Jansen I had ssh working through wifi before this happened. Since then I have tried wired and wireless, neither one of these work anymore.

Shakz

Hummmm how bout you try reinstalling the ssh package.

sudo apt-get --reinstall install openssh-server
I think
sudo apt-get --reinstall install ssh
will also work.

Beretta9

@Shakz I will try that when I get home. Thanks!

PetroRie

When you switch the pie on and connect it to the internet, do you see it on your network? In Windows go to your Network and check if it's listed there. If it is then you're using the wrong IP. I don't use the network IP to connect via SSH I use the hostname which is: retropie

So try:

Host retropie
Username pi
Password raspberry
Port 22

Beretta9

@PetroRie i will try this. Thanks for the advise.

Beretta9

Still no luck. I tried to uninstall and reinstall the ssh server. Also tried to change my host name in cyberduck to retropie. Any more suggestions?

pipari

@Beretta9
Can you "ping" the host?

also try telnet <ip address> 22 (<ip address> change to IP of the raspberry)

Guess you are running mac os x (because of the cyberduck app). Try running ssh from the terminal instead
ssh pi@<ip adress>

best regards

Beretta9

@pipari I'm on A Windows system. I ran ipconfig then ran ping 192.168.2.110.
The ip is visible but comes back as 4 packets sent 4 packets lost.

pipari

@Beretta9 said in SSH not working:

92.168.2.110

192.168.2.110 is the IP of raspberry? Because ipconfig should not work on the raspberry. On the raspberry it is ifconfig command to view network configuration.

As default you should be able to ping the raspberry. Thats the main problem that your computer cannot find the raspberry...

OR it could be that the windows firewall is blocking you. Try disable the firewall (temporary) to verify that thats not the problem.

mrbwa1

Have you tried rebooting your router by chance? One device not working is often resolved with a router reboot. It tends to be pretty rare, but does happen (well except for the Ethernet to wifi bridge my Pi2 is plugged into... that sucker needs to be rebooted every week sometimes....)

glennlake

@Beretta9 There is a windows program called "advanced ip scanner" that will tell you everything on your lan network. Do a google search, download and you can run it without installing. I hope this will help.

Beretta9

@pipari I ran ipconfig and ping from my laptop.
I will check my firewall though. Thanks for your help.

Beretta9

@mrbwa1 I haven't restarted my router, should've done that a long time ago.. I will try this thanks!

pipari

To verify that the ssh server is working on the raspberry:
[On the raspberry]

Login to the raspberry
type "ssh pi@localhost" without "
Then you should get a login prompt (first a question to accept the ssh key)

PS. You most get the IP from the raspberry, not the laptop... the IP of the laptop is irrelevant.

Beretta9

@pipari that command is what I needed.
I ran "ssh pi@localhost" I then got a message saying "Warning: remote host identification has changed". I then ran ssh-keygen -f "home/pi/.ssh/known_hosts" -R localhost.
Ran "ssh pi@localhost" gave a password and problem solved. Thank you everyone for all the help.

glennlake

@Beretta9 Great. I was glad you solved it. I like to follow these forums. I learn something new with each solved issue!