how do i connect my rpi using ethernet cable

Question

hi,

I've recently bought rpi model b+ and am facing problems in connecting it to my laptop as an error occurs every time i run putty software. I'm following the instructions given in the following video.

http://www.youtube.com/watch?v=xarq3PI5zTw

please suggest other by whch i can connect rpi to my laptop. i do not have an external screen.

Robert Peter Oakes · Answer

what are the errors your getting this will help to advise you Thanks Peter

rew · Answer

You are digging up an old thread. Why are you doing that? To get the "helpful" tags on your post? 1) There ARE packets: He's seeing "connection refused": His computer sent a "I want to talk to the program on port 22", and got back the: "sorry but, there is no program on port 22". 2) Well, he's seeing "connection refused", so the packets described above are getting through. 3) Well, the packets are getting trhough what other pins need checking???? The pi is powered correctly otherwise it wouldn't be sending packets back, right? 4) Pray tell, what are the measurements you expect to see using a multimeter on the ethernet port? When is it broken? When is it "no fault"? I'm guessing I'd know that better than you. But what I do know is that there are so many things that could be wrong that cannot be measured with a multimeter that the excercise is unlikely to be useful. So what use is the "then it is a software problem"? 5) Totally bogus remark. Make sure you had a nice breakfast in the morning. And now for something completely different.... What I did not yet know in 2014.... https://www.raspberrypi.org/documentation/remote-access/ssh/ under point 3, you can enable ssh on a headless pi. I use "echo yes > boot/ssh" (which would provoke the possible error to change that to "no" if you decide to disable it later. But the contents of the file doesn't matter. If the file exists (no matter the contents), ssh is enabled).

rew · Answer

Hi Anjani, The "connection refused" means that there is no ssh deamon waiting for you to connect. In the beginning, it was deemed "unsafe" to start the ssh deamon on "out-of-the-box" raspberry pi's. You had to edit a file in the boot partition, or run raspi-config on the console to enable it. That situation would cause the effects you're seeing. Nowadays, last few pi's I've installed, the ssh deamon is turned on by default. This eases things for you and me who are going to use the 'pi without a screen. Either I don't even have a screen-and-keyboard or it's a hassle setting it up for just a few minutes until ssh works. So are you using the official raspian image? How old?

Robert Peter Oakes · Answer

I just created this, it should help, http://www.element14.com/community/community/raspberry-pi/blog/2014/10/03/first-time-login-top-pi-b-b-using-ssh Regards Peter

trado · Answer

Hey, try following these instructions:- (1) Use Wireshark to see if there are any packets. (2) Check the ethernet cables to be sure it's not cut or broken. (3) Try using your multimeter to probe your rpi for any faults like broken pins on your rpi. (4) Probe your systems' Ethernet port too, if there is no fault and it still does not work, then it is a software problem. (5) Finally be sure your rpi is working effectively.

Robert Peter Oakes · Answer

If you connect the PI to an HDMI screen along with keyboard and a network connection Run this command pi@raspberrypi ~ $ ifconfig it should return stuff like this eth0 Link encap:Ethernet HWaddr b8:27:eb:5f:e0:68 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1104 (1.0 KiB) TX bytes:1104 (1.0 KiB) wlan0 Link encap:Ethernet HWaddr 00:13:ef:d0:23:98 inet addr:192.168.1.229 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:435567 errors:0 dropped:7234 overruns:0 frame:0 TX packets:3242 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:330166230 (314.8 MiB) TX bytes:647233 (632.0 KiB) In my case im connected via WIFI and you can see under wlan0 my IP address You may well have a different ip Whatever you have, try to ping it from your computer, this atlest will tell you if you have connectivity The other possibility is you did not enable SSH during install so from the console you will need to follow these instructions to enable it http://www.raspberrypi.org/documentation/remote-access/ssh/ This still means you will need to connect a keyboard and HDMI screen to your PI to complete the task, once that’s done you wont need the keyboard or screen Regards Peter

rew · Answer

If you're using the right IP address and you're getting "connection refused" then that trumps my "I thought the SSH daemon was enabled by default nowadays". The fun with Linux is that you can examine the source of everything that happens to be able to say more about how things work or you you can manually cause things to happen. As in this case. If you use raspi-config it calls "update-rc.d ssh enable" to enable ssh. What this does is it creates a link from /etc/rc2.d/S02ssh to /etc/init.d/ssh . (for completeness, it does this too in the rc3.d, rc4.d and rc5.d directories, but at this point in time those don't matter. So once you can access your raspberry pi, I recommend you dis/enable it once more with raspiconfig to prevent future surprises. ) So if you can mount the sd card on another Linux machine you can create that link, and it should work.

mikepowell · Answer

I think most things have been covered here: 1. Make sure the Ethernet socket of your laptop is MDI-X compatible (that means you can connect Ethernet devices directly together - in the past this was not possible except via a Ethernet switch or a hub). 2. Find out the IP address of your Raspberry Pi. For example 192.168.1.23. 3. Set your Windows computer to static IP, rather than via DHCP. 4. Set your Windows computer IP address to a static address in the range 192.168.1.1 to 192.168.1.254. I normally choose 192.168.1.1. 5. Set gateway address to be your Raspberry Pi address, 192.168.1.23. 6. Leave DNS settings blank. 7. Make sure the SSH service is started on Raspberry Pi. I believe the command should be service sshd start. You need a screen for this bit. You might need to research how to ensure SSH starts when Pi boots up. This should be easy to find. 8. If you still have problems after this, switch Windows Firewall off. 9. You should be able to login using the default username and password. I hope this works out. Regards, Mike.