When you are trying to connect to the SSH address are you getting the PuTTY Security Alert message? You need to agree with it in order to get in. Also are able to ping the board's address? You can also check if the IP address you are using is the right one by using the ifconfig wlan0 command.
I do not get any kind of Security Alert message. The following is the only error I get:
Do I need to have SSH keys on my machine?
Additionally, this is the output of ifconfig wlan0:
wlan0 Link encap:Ethernet HWaddr fc:c2:de:3e:23:b0
inet addr:192.168.1.233 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:8601 (8.3 KiB) TX bytes:5944 (5.8 KiB)
I have confirmed I am using the correct IP address, and that the machine responds to pinging over the network.
I had the same trouble after upgrading to the latest image. I think there's a defect in the latest configure_edison script - although I had a password set, the system did not recognize it had been done. E.g., pulling up the webpage for the device showed that a password had not been set.
I did these steps to fix this:
- Edit /lib/systemd/system/sshd.socket and comment out the USB0 bind statement. This will enable SSH to bind to all network interfaces. This step might also be done automatically by the next step; I did it manually as part of an earlier attempt. It's needed regardless.
- configure_edison --password - this seems to have executed whatever step had failed to complete during the initial device setup. It indicated that it was enabling SSH on wlan0.
- shutdown -r now - The above change is apparently not immediately effective.
Note that with the USB0 interface active, some folks have had issues with the addresses landing in the same subnet, and they needed to readdress the USB0 interface. I didn't run into that, but have found a thread here discussing it.