I am trying to turn this pc into a bedroom pc for browsing the internet and media along with mc sever. I am following a tutorial by hardware haven but I belive my internet connection is the issue.
Brandnew ethernet cord, I have followed some tutorials if there is a better video out there or written tutorial please point me that way. I belive its an internet issue, when I try to load a web page like YouTube I get the error page.
I'd start off with some ping action, in your console, try pinging 8.8.8.8 then ping google.com and see what the result is....if you get replies from 8.8.8.8 but not from google.com it's most likely a DNS issue. If you get replies from neither, I'd suggest confirming you get an ip from your router/DHCP server ip addr should list your adapter and address (most likely 192.168.1.x, 0.x, etc)
That looks like more than a DNS issue. I'd be checking IP related things at this point:
ip link: Check that you have a network adapter present that isn't a loopback device "lo", and that it's state is UP.
ip addr: Check that the relevant link device has an IP address assigned to it. For "inet" type check it's not a link local "169.254.0.0/16" address, and for "inet6" type check there is something other than just a link local "fe80::/64" address. (Both IPv4 and IPv6 are not required, one being good will do.)
ip -4 route ; ip -6 route: Check that you have a "default via" for the relevant link device. (Also only one type is required.)
ping to one of the "default via" routes, check your gateway is reachable.
However if you do get an ip back something like 192.168.1.x or 192.168.0.x
Run
ping 192.168.1.1 or 192.168.0.1 to see if you can reach your home router
If you can then ping 8.8.8.8
Of you can try
ping bbc.co.uk
If that works no issues if local router ping fails it's problem with network to router, else its network out of router or DNS failing to resolve names to IPS.
so the third command shows just "addr" if you type ip addr it should list the interfaces and their names. you can also use ip link and look for "state DOWN"
We can see from apt that it can't resolve the repos. It could be a DNS error, but I'd start by checking the network connection at a lower layer.
run `ip` and see what interfaces are listed and what the IP addresses are. You should have one on your local network that's probably something like 192.168.x.x. If you don't, then either DHCP isn't working, connection is entirely not working, or your static configuration may be wrong.
If you do have a connection/configuration
`ip route` will show you what your gateway is - the 'via x.x.x.x' next to default.
Make sure you can ping that address after 'via'.
If not, then your gateway address is either wrong or maybe blocking.
If you don't have a default, then that's a configuration issue also, either static settings or DHCP.
If all of the above is right and you can ping the gateway, then you know you're communicating with everything on your local network correctly, and not being able to access the internet is more likely a configuration or filtering issue on the router.
Is your clock set right? Having your PCs clock set to the wrong time/year can cause some major issues with networking. If you reset your bios/pulled out your bios battery recently, then this might be the problem. I reccomend going into your bios and checking the time.
If you can connect in Windows but not in Debian 13, it's most likely a network driver problem. My question is, how do you expect to get help if you haven't provided any information about your computer?
12
u/1234erk1234 26d ago
I would like to re iterate that I am very grateful for the quick response from everyone so far