What is causing PuTTy to not connect to Raspberry Pi?
I have a Raspberry Pi, and I have an SD card with Rasbian on it that is currently in the Pi.
I have a laptop with Windows 8.1 on it, and I have connected it to the Pi using an Ethernet cable. I want to SSH in to the Pi, so I have installed PuTTy.
I went to the windows command line and typed in ipconfig
and looked under Ethernet adapter Ethernet > Autoconfiguration Ipv4 Address to find the ip address of the Pi.
I took that IP and entered it under "Hostname(or IP address)" in PuTTy. I gave the name a session, pressed save and open. Now, I am getting the following error:
Fatal Error: Network Error: Connection Refused
I looked online, but I couldn't find a solution for windows (but there are a lot for Linux). I tried making sure I had the right IP address by trying to ping the Pi (and I can). I read other posts saying the error is caused by the server blocking the connection, but I am not sure how I would go about fixing that. The only thing I can see that looks strange in the command line to me is that there is no default gateway set up for Ethernet. However, I thought that I would need access to the Pi in order to change that.
Can someone tell me if there is a step I am missing in my setup that could be causing this error?
I'm new to this, so any help is appreciated.
Thanks!
windows ssh raspberry-pi putty
migrated from stackoverflow.com Jun 7 '15 at 10:26
This question came from our site for professional and enthusiast programmers.
add a comment |
I have a Raspberry Pi, and I have an SD card with Rasbian on it that is currently in the Pi.
I have a laptop with Windows 8.1 on it, and I have connected it to the Pi using an Ethernet cable. I want to SSH in to the Pi, so I have installed PuTTy.
I went to the windows command line and typed in ipconfig
and looked under Ethernet adapter Ethernet > Autoconfiguration Ipv4 Address to find the ip address of the Pi.
I took that IP and entered it under "Hostname(or IP address)" in PuTTy. I gave the name a session, pressed save and open. Now, I am getting the following error:
Fatal Error: Network Error: Connection Refused
I looked online, but I couldn't find a solution for windows (but there are a lot for Linux). I tried making sure I had the right IP address by trying to ping the Pi (and I can). I read other posts saying the error is caused by the server blocking the connection, but I am not sure how I would go about fixing that. The only thing I can see that looks strange in the command line to me is that there is no default gateway set up for Ethernet. However, I thought that I would need access to the Pi in order to change that.
Can someone tell me if there is a step I am missing in my setup that could be causing this error?
I'm new to this, so any help is appreciated.
Thanks!
windows ssh raspberry-pi putty
migrated from stackoverflow.com Jun 7 '15 at 10:26
This question came from our site for professional and enthusiast programmers.
Please move your question to Super User. It's off-topic here.
– Martin Prikryl
Jun 5 '15 at 5:33
@MartinPrikryl I flagged it so that way it could be migrated to Super User. Thanks!
– JustBlossom
Jun 5 '15 at 14:48
add a comment |
I have a Raspberry Pi, and I have an SD card with Rasbian on it that is currently in the Pi.
I have a laptop with Windows 8.1 on it, and I have connected it to the Pi using an Ethernet cable. I want to SSH in to the Pi, so I have installed PuTTy.
I went to the windows command line and typed in ipconfig
and looked under Ethernet adapter Ethernet > Autoconfiguration Ipv4 Address to find the ip address of the Pi.
I took that IP and entered it under "Hostname(or IP address)" in PuTTy. I gave the name a session, pressed save and open. Now, I am getting the following error:
Fatal Error: Network Error: Connection Refused
I looked online, but I couldn't find a solution for windows (but there are a lot for Linux). I tried making sure I had the right IP address by trying to ping the Pi (and I can). I read other posts saying the error is caused by the server blocking the connection, but I am not sure how I would go about fixing that. The only thing I can see that looks strange in the command line to me is that there is no default gateway set up for Ethernet. However, I thought that I would need access to the Pi in order to change that.
Can someone tell me if there is a step I am missing in my setup that could be causing this error?
I'm new to this, so any help is appreciated.
Thanks!
windows ssh raspberry-pi putty
I have a Raspberry Pi, and I have an SD card with Rasbian on it that is currently in the Pi.
I have a laptop with Windows 8.1 on it, and I have connected it to the Pi using an Ethernet cable. I want to SSH in to the Pi, so I have installed PuTTy.
I went to the windows command line and typed in ipconfig
and looked under Ethernet adapter Ethernet > Autoconfiguration Ipv4 Address to find the ip address of the Pi.
I took that IP and entered it under "Hostname(or IP address)" in PuTTy. I gave the name a session, pressed save and open. Now, I am getting the following error:
Fatal Error: Network Error: Connection Refused
I looked online, but I couldn't find a solution for windows (but there are a lot for Linux). I tried making sure I had the right IP address by trying to ping the Pi (and I can). I read other posts saying the error is caused by the server blocking the connection, but I am not sure how I would go about fixing that. The only thing I can see that looks strange in the command line to me is that there is no default gateway set up for Ethernet. However, I thought that I would need access to the Pi in order to change that.
Can someone tell me if there is a step I am missing in my setup that could be causing this error?
I'm new to this, so any help is appreciated.
Thanks!
windows ssh raspberry-pi putty
windows ssh raspberry-pi putty
asked Jun 4 '15 at 18:00
JustBlossomJustBlossom
111116
111116
migrated from stackoverflow.com Jun 7 '15 at 10:26
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Jun 7 '15 at 10:26
This question came from our site for professional and enthusiast programmers.
Please move your question to Super User. It's off-topic here.
– Martin Prikryl
Jun 5 '15 at 5:33
@MartinPrikryl I flagged it so that way it could be migrated to Super User. Thanks!
– JustBlossom
Jun 5 '15 at 14:48
add a comment |
Please move your question to Super User. It's off-topic here.
– Martin Prikryl
Jun 5 '15 at 5:33
@MartinPrikryl I flagged it so that way it could be migrated to Super User. Thanks!
– JustBlossom
Jun 5 '15 at 14:48
Please move your question to Super User. It's off-topic here.
– Martin Prikryl
Jun 5 '15 at 5:33
Please move your question to Super User. It's off-topic here.
– Martin Prikryl
Jun 5 '15 at 5:33
@MartinPrikryl I flagged it so that way it could be migrated to Super User. Thanks!
– JustBlossom
Jun 5 '15 at 14:48
@MartinPrikryl I flagged it so that way it could be migrated to Super User. Thanks!
– JustBlossom
Jun 5 '15 at 14:48
add a comment |
5 Answers
5
active
oldest
votes
"Connection refused" generally means the sshd daemon isn't running, and/or isn't listening on port 22.
I think you might have the wrong IP: "ipconfig" on Windows gives you the Windows IP address: you want the Raspberry Pi address.
Try this:
raspi-config > 8 Advanced Options > A4 SSH > make sure SSH access is "enabled"
Run
ifconfig
on the Raspberry Pi. Try Putty with that address.
Look here for more info:
http://www.instructables.com/id/Use-ssh-to-talk-with-your-Raspberry-Pi/
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
2
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
1
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
|
show 4 more comments
Mine was a case of an install of VirtualBox having the same IP addy as the rpi, on the windows host.
After looking at IPCONFIG on the windows host a dozen times, I finally noticed that it was the same for VB as the router had for my rpi.
Changed IP addy in VirtualBox > Preferences and was able to ssh on my second attempt (as is the custom with Putty on my box).
So if all the other troubleshooting steps don't work, looking for conflicts on the host is worth a shot. Don't ask how long it took me to figure this out -_-
TL;DR: When I typed XXX.XXX.X.10 for my IP in Putty, it was pointing to VirtualBox. IPCONFIG confirmed this. Changing VB IP address to XXX.XXX.X.100, solved problem.
add a comment |
I came across this question while faced with the same error/problem. I've found something that works for me, so I'll update the answers.
The short answer is that you need to add a file to the boot folder of your SD card, and call it "ssh" (the filename is extension-less, mind you).
The instructions for this can be found here: Headless Raspberry Pi Setup
add a comment |
The Nov 2017 version of Rasbian already includes SSH server and client. However by default SSH is disabled. In order to enable it use
$ sudo raspi-config
Then choose "5. Interfacing options"
Then select "Enable/Disable remote command line access to your Pi using SSH"
Tab to Back
Tab to Finish
Now you should be able to SSH from your machine to your Rasbian Pi :)
add a comment |
Using 2018-11-13-raspbian-stretch-lite
image doesn't works to setup "headless" raspbian, Using first 2018 raspbian-stretch-lite
image works as it should.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f924859%2fwhat-is-causing-putty-to-not-connect-to-raspberry-pi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
"Connection refused" generally means the sshd daemon isn't running, and/or isn't listening on port 22.
I think you might have the wrong IP: "ipconfig" on Windows gives you the Windows IP address: you want the Raspberry Pi address.
Try this:
raspi-config > 8 Advanced Options > A4 SSH > make sure SSH access is "enabled"
Run
ifconfig
on the Raspberry Pi. Try Putty with that address.
Look here for more info:
http://www.instructables.com/id/Use-ssh-to-talk-with-your-Raspberry-Pi/
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
2
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
1
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
|
show 4 more comments
"Connection refused" generally means the sshd daemon isn't running, and/or isn't listening on port 22.
I think you might have the wrong IP: "ipconfig" on Windows gives you the Windows IP address: you want the Raspberry Pi address.
Try this:
raspi-config > 8 Advanced Options > A4 SSH > make sure SSH access is "enabled"
Run
ifconfig
on the Raspberry Pi. Try Putty with that address.
Look here for more info:
http://www.instructables.com/id/Use-ssh-to-talk-with-your-Raspberry-Pi/
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
2
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
1
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
|
show 4 more comments
"Connection refused" generally means the sshd daemon isn't running, and/or isn't listening on port 22.
I think you might have the wrong IP: "ipconfig" on Windows gives you the Windows IP address: you want the Raspberry Pi address.
Try this:
raspi-config > 8 Advanced Options > A4 SSH > make sure SSH access is "enabled"
Run
ifconfig
on the Raspberry Pi. Try Putty with that address.
Look here for more info:
http://www.instructables.com/id/Use-ssh-to-talk-with-your-Raspberry-Pi/
"Connection refused" generally means the sshd daemon isn't running, and/or isn't listening on port 22.
I think you might have the wrong IP: "ipconfig" on Windows gives you the Windows IP address: you want the Raspberry Pi address.
Try this:
raspi-config > 8 Advanced Options > A4 SSH > make sure SSH access is "enabled"
Run
ifconfig
on the Raspberry Pi. Try Putty with that address.
Look here for more info:
http://www.instructables.com/id/Use-ssh-to-talk-with-your-Raspberry-Pi/
answered Jun 4 '15 at 18:14
paulsm4paulsm4
1,375911
1,375911
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
2
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
1
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
|
show 4 more comments
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
2
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
1
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
Where would I find that if I haven't gotten into the Pi yet? I read through the documentation, but I don't have access to an external screen and keyboard to get into the log in screen for the Pi.
– JustBlossom
Jun 4 '15 at 18:18
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
OK: exactly how far do you get with this tutorial: raspberrypi.org/help/quick-start-guide
– paulsm4
Jun 4 '15 at 18:42
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
I made it through step one, but I didn't make it any further because the rest requires a keyboard and screen. I followed the noobs guide in step 7 of the guide you sent: raspberrypi.org/help/noobs-setup I got to step two of "First Boot" but I never saw anything boot. I even tried restarting my computer to see if it would do something like a dual boot that I would do with Ubuntu. So, that is when I broke away from those instructions and started trying to SSH into it since I don't have an external keyboard or screen.
– JustBlossom
Jun 4 '15 at 19:12
2
2
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
To summarize: 1) the reason you're getting "connection refused" is because you're pointing to the wrong IP. You need to "Putty" in to your Raspberry Pi: you can get the IP from "ifconfig" (at an RP command prompt), or from the boot screen. You might also need to run "raspi-config" (from an RP command prompt) to get sshd working. 2) Even though you can run RP "headless" after you've configured it ... you're probably going to need to connect a monitor and keyboard in order to configure it.
– paulsm4
Jun 4 '15 at 22:33
1
1
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
Just in case anyone reading this thread is wondering...I ended up just getting a screen and keyboard to finish the configuration.
– JustBlossom
Nov 9 '15 at 3:41
|
show 4 more comments
Mine was a case of an install of VirtualBox having the same IP addy as the rpi, on the windows host.
After looking at IPCONFIG on the windows host a dozen times, I finally noticed that it was the same for VB as the router had for my rpi.
Changed IP addy in VirtualBox > Preferences and was able to ssh on my second attempt (as is the custom with Putty on my box).
So if all the other troubleshooting steps don't work, looking for conflicts on the host is worth a shot. Don't ask how long it took me to figure this out -_-
TL;DR: When I typed XXX.XXX.X.10 for my IP in Putty, it was pointing to VirtualBox. IPCONFIG confirmed this. Changing VB IP address to XXX.XXX.X.100, solved problem.
add a comment |
Mine was a case of an install of VirtualBox having the same IP addy as the rpi, on the windows host.
After looking at IPCONFIG on the windows host a dozen times, I finally noticed that it was the same for VB as the router had for my rpi.
Changed IP addy in VirtualBox > Preferences and was able to ssh on my second attempt (as is the custom with Putty on my box).
So if all the other troubleshooting steps don't work, looking for conflicts on the host is worth a shot. Don't ask how long it took me to figure this out -_-
TL;DR: When I typed XXX.XXX.X.10 for my IP in Putty, it was pointing to VirtualBox. IPCONFIG confirmed this. Changing VB IP address to XXX.XXX.X.100, solved problem.
add a comment |
Mine was a case of an install of VirtualBox having the same IP addy as the rpi, on the windows host.
After looking at IPCONFIG on the windows host a dozen times, I finally noticed that it was the same for VB as the router had for my rpi.
Changed IP addy in VirtualBox > Preferences and was able to ssh on my second attempt (as is the custom with Putty on my box).
So if all the other troubleshooting steps don't work, looking for conflicts on the host is worth a shot. Don't ask how long it took me to figure this out -_-
TL;DR: When I typed XXX.XXX.X.10 for my IP in Putty, it was pointing to VirtualBox. IPCONFIG confirmed this. Changing VB IP address to XXX.XXX.X.100, solved problem.
Mine was a case of an install of VirtualBox having the same IP addy as the rpi, on the windows host.
After looking at IPCONFIG on the windows host a dozen times, I finally noticed that it was the same for VB as the router had for my rpi.
Changed IP addy in VirtualBox > Preferences and was able to ssh on my second attempt (as is the custom with Putty on my box).
So if all the other troubleshooting steps don't work, looking for conflicts on the host is worth a shot. Don't ask how long it took me to figure this out -_-
TL;DR: When I typed XXX.XXX.X.10 for my IP in Putty, it was pointing to VirtualBox. IPCONFIG confirmed this. Changing VB IP address to XXX.XXX.X.100, solved problem.
edited May 25 '17 at 6:13
answered May 25 '17 at 6:05
VonRansakVonRansak
12
12
add a comment |
add a comment |
I came across this question while faced with the same error/problem. I've found something that works for me, so I'll update the answers.
The short answer is that you need to add a file to the boot folder of your SD card, and call it "ssh" (the filename is extension-less, mind you).
The instructions for this can be found here: Headless Raspberry Pi Setup
add a comment |
I came across this question while faced with the same error/problem. I've found something that works for me, so I'll update the answers.
The short answer is that you need to add a file to the boot folder of your SD card, and call it "ssh" (the filename is extension-less, mind you).
The instructions for this can be found here: Headless Raspberry Pi Setup
add a comment |
I came across this question while faced with the same error/problem. I've found something that works for me, so I'll update the answers.
The short answer is that you need to add a file to the boot folder of your SD card, and call it "ssh" (the filename is extension-less, mind you).
The instructions for this can be found here: Headless Raspberry Pi Setup
I came across this question while faced with the same error/problem. I've found something that works for me, so I'll update the answers.
The short answer is that you need to add a file to the boot folder of your SD card, and call it "ssh" (the filename is extension-less, mind you).
The instructions for this can be found here: Headless Raspberry Pi Setup
answered Nov 28 '17 at 1:34
AndrewAndrew
1
1
add a comment |
add a comment |
The Nov 2017 version of Rasbian already includes SSH server and client. However by default SSH is disabled. In order to enable it use
$ sudo raspi-config
Then choose "5. Interfacing options"
Then select "Enable/Disable remote command line access to your Pi using SSH"
Tab to Back
Tab to Finish
Now you should be able to SSH from your machine to your Rasbian Pi :)
add a comment |
The Nov 2017 version of Rasbian already includes SSH server and client. However by default SSH is disabled. In order to enable it use
$ sudo raspi-config
Then choose "5. Interfacing options"
Then select "Enable/Disable remote command line access to your Pi using SSH"
Tab to Back
Tab to Finish
Now you should be able to SSH from your machine to your Rasbian Pi :)
add a comment |
The Nov 2017 version of Rasbian already includes SSH server and client. However by default SSH is disabled. In order to enable it use
$ sudo raspi-config
Then choose "5. Interfacing options"
Then select "Enable/Disable remote command line access to your Pi using SSH"
Tab to Back
Tab to Finish
Now you should be able to SSH from your machine to your Rasbian Pi :)
The Nov 2017 version of Rasbian already includes SSH server and client. However by default SSH is disabled. In order to enable it use
$ sudo raspi-config
Then choose "5. Interfacing options"
Then select "Enable/Disable remote command line access to your Pi using SSH"
Tab to Back
Tab to Finish
Now you should be able to SSH from your machine to your Rasbian Pi :)
answered Feb 20 '18 at 19:56
BenBen
11
11
add a comment |
add a comment |
Using 2018-11-13-raspbian-stretch-lite
image doesn't works to setup "headless" raspbian, Using first 2018 raspbian-stretch-lite
image works as it should.
add a comment |
Using 2018-11-13-raspbian-stretch-lite
image doesn't works to setup "headless" raspbian, Using first 2018 raspbian-stretch-lite
image works as it should.
add a comment |
Using 2018-11-13-raspbian-stretch-lite
image doesn't works to setup "headless" raspbian, Using first 2018 raspbian-stretch-lite
image works as it should.
Using 2018-11-13-raspbian-stretch-lite
image doesn't works to setup "headless" raspbian, Using first 2018 raspbian-stretch-lite
image works as it should.
edited Feb 1 at 17:29
Ahmed Ashour
1,3271716
1,3271716
answered Feb 1 at 8:52
FlorexFlorex
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f924859%2fwhat-is-causing-putty-to-not-connect-to-raspberry-pi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please move your question to Super User. It's off-topic here.
– Martin Prikryl
Jun 5 '15 at 5:33
@MartinPrikryl I flagged it so that way it could be migrated to Super User. Thanks!
– JustBlossom
Jun 5 '15 at 14:48