I’ve had this problem right from the beginning and have no ideas left on how to approach it.
For context: I’m usually the person that fixes your Windows problem, and I’ve already gone through numerous tips found on other forums (which unfortunately has been a while, so I can’t reiterate), but my experience with Linux is limited and I was mostly copying commands hoping I’d find a fix.
After booting, there’s a little popup at the top right telling me the Pi has an IP. It’s the IP I assigned to it via DHCP, and the Pi appears as connected in my Router, but the Pi has no access to the internet and I can’t ping any of my devices in the same network, and vice versa. The only “solution” I have is to reboot the Pi until it works (i.e. starts to inform about updates, too), which is silly and annoying.
It seems like there might be some services not starting properly. Also, whenever the Pi is not connecting, although it does appear in the Router’s menu, it’s not the same chain of icons as when it’s actually connected to the internet. (I’m aware that this isn’t very useful without screenshots, but I’ll deliver as soon as I can).
The Pi is not hindered by a firewall and I think it’s always using its physical MAC address. There is also no other device with the same IP around. It doesn’t matter whether I’m using WiFi or LAN, and it doesn’t matter whether I’m using DHCP or assign a fixed IP.
I’m hoping someone might’ve encountered this before and could give me an idea on how to further troubleshoot the issue ?
I have been a Linux user practically since the beginning of this operating system.
Except for very specific cases where I am forced to use Windows, I use Linux for the vast majority of applications.
I think I can help you solve the problem.
We will probably have to exchange a lot of information. In order not to saturate the forum, if you think it is appropriate, send me a private message with your email and in this way we will have a more direct and fluid communication.
Currently I can ping the Pi (IP and name), but the Pi can not ping my Windows PC or access the internet. SSH/VNC doesn’t work.
Now I rebooted, the Pi is online, pinging goes both ways, ssh works. My router says… the same as before … I’m positive I had seen an extra icon when the Pi was online before, but I guess not today. So much for that.
Anyway. I’ve taken screenshots of the connection information window now. Maybe there’s a clue next time it doesn’t work.
@Manuel_Angel Will send a message. Thanks for the offer!
Are you trying to run the Pi headless?, meaning, you do not have a separate keyboard, mouse and display hooked up to the Pi, and you are utilzing like it like its own computer, but instead it appears as remote access device, where the Pi’s screen is in a window on your computer’s screen?
I’ve done headless operation on both Pi 3+ and now a Pi 5. If you objective is to run headless, and you are running a Pi 5, it should be easy enough to set up. Raspberry Pi some good resources on this, but here is the gist of it.
Use the latest version of the Pi OS (bookworm)
Using the Pi imager software to write the image onto your SD card
(I don’t have an SD card at the moment, so I can’t post screen images of the following steps)
In the Pi image, there are options to have it automatically connect to your newtwork.
Assuming wireless connection, you will need to put in the SSID and password. There are some other security and connection settings, one that allows for booting into CLI (command line interface) or Desktop. For CLI, there are a number of opensource remote terminal software programs for windows, for graphical, ripi suggests tigervnc.
In the Pi Imager, you should set the devices username and password (write it down).
You can also set the device name, default is something like: raspberrypi.local, if the pi successfully joins the network, this should appear in you router connected device, you can also figure out which address it’s at when DHCP assigns it.
Using the terminal or tigervnc, you will attempt to connect via that address.
You may get some error messages, and have to re-image the SD if the Pi can’t connect to the wifi.
I will trying to get more detail when I am able to use and SD card to run through the imager setup.
Thanks for the reply and sorry for not closing this thread.
I exchanged a few mails with @Manuel_Angel and finally could resolve the problem by using a static IP.
Thing is, I had already setup the Pi with a static IP earlier and it didn’t change anything about the connection issues, so I didn’t make another attempt. It’s possible that I accidentally picked one from inside the DHCP server range at the time, but even then we couldn’t really find a reason why the RPi wouldn’t work with DHCP in the first place, when every other device in the household is running without issues.
Anyway. The connection is reliable now! Thanks again.
Edit regarding headless: I wanted to and went with RealVNC, which works, but things kind of struggle when the camera preview window is running during scan. I had to work around the network issues so much, I just used ssh or worked on the Python scripts with local editors (when it worked). Now I have a seperate screen and only use a mouse with the Pi to start the program. I barely have the need to type anything anymore (since the scanner is running rather nicely right now), but when I do I punish myself with a software keyboard
No problem. Your response, as well as mine, may help someone else. If you don’t close this, I will try to add some more detail (screen shots), so as to make my response more helpful.
Yes, static IP can both help and confuse, as you discovered. I’ve tried both in the past on other projects. Since I know how to log into my router, I can see the devices in the routing table, and figure out which one is the Pi.
?
… I’m positive I had seen an extra icon when the Pi was online before, but I guess not today. So much for that.
and finally could resolve the problem by using a static IP.
