Timeline for Couldnt enable SSH headless
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 27, 2017 at 17:53 | answer | added | Stowoda | timeline score: 1 | |
Jan 27, 2017 at 14:42 | answer | added | Aloha | timeline score: 3 | |
Jan 27, 2017 at 14:13 | comment | added | Adam Plocher | I agree, seems you're connecting to your router's SSH server. Try connecting to the router (web UI if it has one) and find a list of known machines (or DHCP log) and see what IP's are actively used right now. You can probably pinpoint the Pi pretty quick (default hostname is raspberrypi I think). If you don't have access to the router, install nmap and run nmap 192.168.2.0/24 to scan the entire class-c. It should run multiple checks (ping, basic port scan, and I think attempt OS identification). It should tell you pretty quick which IP your Pi is sitting on. | |
Jan 27, 2017 at 14:00 | comment | added | goobering | That you're getting as far as that response screen means that you're connecting to something at that IP address. I notice that 192.168.2.1 seems to be the default address assigned to Belkin routers - is it possible you're trying to connect to your router rather than the Pi? | |
Jan 27, 2017 at 13:42 | comment | added | techraf |
If it's really the Pi then the SSH daemon is working, so the ssh file-configuration worked. You need to provide the correct password or ...connect to the correct machine. It would be pretty unusual (although not impossible) for a router with default configuration to give .1 address to the client machine.
|
|
Jan 27, 2017 at 13:40 | history | edited | Anton Bystrov | CC BY-SA 3.0 |
corrected spelling
|
Jan 27, 2017 at 13:35 | review | First posts | |||
Jan 27, 2017 at 13:40 | |||||
Jan 27, 2017 at 13:31 | history | asked | Anton Bystrov | CC BY-SA 3.0 |