I have been using my Rpi for some time now using ssh with no problems until recently when i tried to login using the default password and it refused. After several attempts i packed it away, so it happens that i wanted to use it again earlier on today and when i tried accessing it using PuTTy it gave me a "unable to open connection to raspberrypi.local Host does not exist!" error. so i got a new memory card with Noobs on it reinstalled the OS only to get the same error, "unable to open connection to raspberrypi.local Host does not exist!". i have tried all i can i need help..
I had a very similar problem (connecting from a Windows 10 PC to a Pi Zero over USB using PuTTY), and I solved it by following this guide and by using a non-OTG USB cable/adapter: http://www.circuitbasics.com/raspberry-pi-zero-ethernet-gadget/. My issue seemed to be that the Pi was getting locked into a host-state while using the OTG micro-USB to USB adapter and thus couldn't receive any commands over the "ethernet" USB connection.
Did you check your devices in your network? And did you try it with "raspberrypi" instead of raspberrypi.local?
Good luck!
Related
I successfully flashed a new coral dev board and verified everything went well using the HDMI video feed. I installed MDT on Windows 10 and can see the device
$ mdt devices
jumbo-wasp (192.168.101.2)
But when I try to connect I get a socket error
$ mdt shell
Waiting for a device...
Connecting to jumbo-wasp at 192.168.101.2
Couldn't establish ssh connection to device: socket error: [WinError 6] The handle is invalid
I've also tried to connect using the serial cable (micro USB) following the directions here: https://coral.ai/docs/dev-board/serial-console/#connect-with-linux
but the device never showed up in my COM adapters.
Any help would be greatly appreciated.
UPDATE:
I am able to use the serial connection now with Putty to connect now (had a bad micro USB cable), but I'm not sure what to do next to get the USB-C connection working with MDT
Finally solved this. The issue was with the Git Bash app they suggested using. Instead I used a Python Terminal and was able to connect.
Note, when trying to adjust the network adapter settings, nmtui would not work, I instead had to use the command line interface nmcli.
I had a similar problem where the mdt devices command could not see my Coral Dev Mini. Git Bash just didn't work at all for me. Eventually I installed the free Ubuntu terminal for Windows 10 and it worked fine. I downloaded it directly from Microsoft
I am new to Raspberry Pi. I have a Pi 2 kit model B.I am using an angry IP address and I can find Raspberry Pi's address using it. When I configure it using sudo raspi-config, make necessary changes and then say OK to reboot, I get this error in putty:
Server unexpectedly closed network connection.
How do I correct this issue?
Further, I have connected Raspberry Pi 2 with an Ethernet cable to the laptop. I have completed necessary steps like changing adapter settings, edited properties of Wi-Fi to allow other network users to connect to computers Internet connection but still I have no Internet access shown for unidentified Internet connection.
How can I solve this? Please suggest the necessary steps to be implemented
For me too many process and session running for a particular user is the cause of your problem so alternatively I logged in as root and ran the following commands:
ps -fp $(pgrep -d, -u adminuser)
pkill -9 -u adminuser
After this I can login normally in putty like ever before.
I am trying to remotely gain access to the command line of a Raspberry Pi 3 from my windows laptop on the same network using ssh. I am using Putty as the tool.
Since both my laptop and Pi are connected using my home Internet wireless connection, they are on the same network. When I try to ping the Pi from my laptop, it says destination is not reachable. However, if I keep trying for 4-5 times, it finally works. I am able to use Putty and connect to my Pi and execute some commands. However, after few minutes, I lose the connection. When I try to ping the pi, I get the message destination is not reachable.
This issue is intermittent. I used the below link to set a static IP address.
http://www.modmypi.com/blog/how-to-give-your-raspberry-pi-a-static-ip-address-update
I am able to now always connect to my pi using a fixed IP address. However, the issue still exist. I am able to ping the pi after several attempts and then after few minutes the connection drops.
I am using the ADSL2+ internet connection at home and dont see any problem with that. In my Pi, I opened the file /etc/ssh/sshd_config file to confirm the port is 22. I use my Putty to connect to my Pi using port 22.
Thanks,
Murali
I have used PuTTy.exe for an SSH client. But putty.exe is not working for a 64 bit Windows OS. It works perfectly 32 bit Win OS.
Questions:
Am I making some mistakes. If so please can you help?
Is there any app which works on both 32 and 64 machine for win os?
Is there any cmd commands to connect ssh?
Info:
Putty.exe ver 0.63.10125.0.
Run as administrator used no use.
firewall disabled no use.
putty.exe runs on a separate drive no use.
Error:
Network error: Permission denied
Oh I found the solution for this problem.
Its due to anti virus (ex: norton).
Anti virus blocks all the network permissions.
So I have disabled all smart firewall and browser protection from anti virus.
it worked fine.
Please disable all third party firewalls too then it will work. It is not 32 and 64 bit issue I think so.
It's usually a firewall problem, especially with third party firewalls, in my case TinyWall for Windows. Simply allow the program access.
I have McAfee Endpoint Security and I had the same problem. Whenever I try to connect with putty I get "permission denied". In this case, I opened McAfee Endpoint Security, went to "Firewall". In "Firewall" I went to "RULES" and pressed "Add Rule", wrote the rule name and went to the bottom to "Executables". In "Executables" I pressed "Add", then "Browse", and added PUTTY executable. That solved this problem for me.
Just in case someone comes across the same problem:
At some point I started to receive the following errors when trying to run port forwarding
Event Log: Local port 2001 SOCKS dynamic forwarding failed: Network error: Permission denied
After struggling with that for a while, installed Bitwise SSH where the error would appear as:
Failed to enable SOCKS/HTTP proxy forwarding on 127.0.0.1:2001: Address is already in use; bind() in ListeningSocket::StartListening() failed: Windows error 10013: An attempt was made to access a socket in a way forbidden by its access permissions.
So it was clear that the port is in use - although that didn't show up in CurrPorts. So I resolved that by changing the port number
I don't know why? Whenever I install AOL desktop (9.5, 9.6, 10.0) on my computer and I'm connected to the internet using cable, every thing is ok. I can browse websites and sign in to AOL.
But whenever I connect to the internet using my wireless network at home, I can not sign in to AOL, but I can still browse the web.
My wireless network uses WPA2-Personal with AES encryption type.
I always get the AC-3000 error message whenever I want to sign into AOL. None of AOL solutions could be useful to solve this.
What do I have to do ?
You didn't mention what version of windows you are using but my suspicion would be that if you are on Windows Vista/7 then the cable connection is identified as "home" or private and that the wireless connection is identified as public and the AOL connection (which used to be on port 5190 IIRC) is getting blocked as a result.
If I am right, to change what apps have access on which network types, you can follow the instructions here:
http://www.addictivetips.com/windows-tips/how-to-stop-a-program-from-gaining-unsolicited-internet-access-in-windows-7/
Although it is about how to stop a program from accessing the internet, it works just as well the other way around ;)
You could use netstat to determine what the successful connection to AOL is on the cable set up in terms of destination and IP and then attempt a simple telnet connection to the same address/port on the wireless set up to verify if this is blocked at the network/port level or if it is blocking the application (usually referred to as ACS). If the telnet connection succeeds and does not timeout, then it is an application level restriction which you will need to fix .