Until recently, my Pi 3B was working perfectly fine on VNC using ethernet with my windows 10 laptop. The problem started after I took out my SD card one day I believe. The IP was still showing up on Advanced IP Scanner at that point but remote connection wasn't possible, even after putting in another SSH file in the SD card.
This doesn't appear to be an issue with power. This also doesn't work using raspberrypi.local or firstname.lastname@example.org. I figured the SD card may have been corrupted(Windows says something is wrong wih BOOT:/E but scanning yields no errors and restarts change nothing), so I formatted it and using Win32DiskImager and Raspberry Pi Imager wrote Raspbian OS back onto it (2020-02-13-raspbian-buster) as well as the SSH file, only this time the IP hasn't come up. I've written another OS to it as well to the same result (2020-08-20-raspios-buster-armhf).
I also decided to try wpa_supplicant.conf and have the Pi boot up online. This didn't work.
I know that the Pi must be registering the SD card since the SSH file was deleted (meaning it was enabled). I also made sure the file extension of the wpa_supplicant.conf file was correct. I'm not sure where else to go from here in order to solve my problem. Could I be mistaken in thinking an SSH file being deleted means that the SD card is being read? Are there any physical indicators that the Pi is connected to a network or the SD card is being read from(lights)? Could this be an issue with my computer?
Update from a comment:
It (the ip address) no longer appears (with Advanced IP Scanner) unfortunately...
Edit: Using wpa_supplicant.conf, I connected to my router and started remote access through WiFi. So that works. For some reason though, using the ethernet doesn't. WiFi is far laggier, so if possible I'd like to get ethernet to work. Now that I have access to my pi, how could I potentially troubleshoot?
Output for ip addr:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:58:38:7b brd ff:ff:ff:ff:ff:ff inet 169.254.123.193/16 brd 169.254.255.255 scope global noprefixroute eth0 valid_lft forever preferred_lft forever inet6 fe80::4de:8ab1:f694:e760/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b8:27:eb:0d:6d:2e brd ff:ff:ff:ff:ff:ff inet 192.168.1.243/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0 valid_lft 86315sec preferred_lft 75515sec inet6 fe80::91e6:143f:5269:b08d/64 scope link valid_lft forever preferred_lft forever
Output for ip route:
default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.247 metric 202 default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.243 metric 303 192.168.1.0/24 dev eth0 proto dhcp scope link src 192.168.1.247 metric 202 192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.243 metric 303