If the system boots to the desktop, open a terminal and type this command:
Check if an IP address is assigned to the interface eth0 or wlan0 (something like 192.168.x.y)
Code: Select all
pi@rpi:~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:44:88:84
inet addr:192.168.1.58 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1f11:f7ea:e8d9:2eaf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31624 errors:0 dropped:422 overruns:0 frame:0
TX packets:24634 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43503172 (41.4 MiB) TX bytes:1946833 (1.8 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:15068 (14.7 KiB) TX bytes:15068 (14.7 KiB)
pi@rpi:~ $
The router could change the IP address assigned to your RPi occasionally. Check if the current IP assigned to your RPi is the same of the putty session.
Open a terminal on your PC and type a ping command to your RPi:
If you get a correct response, the remote login to your RPi should work properly.