Macbook Ethernet Connected But No Internet

[Jeff]

Itried plugging in my ethernet cable to my school's internet (I cannot reset, touch or even see the router I'm actually plugging into). Usually the port works for other laptops, my friends tried the same port with the same cable and it works fine for him. But on my Mac it says that I'm connected to ethernet and the ISP but cannot connect to internet. In network utilities, the IP address starts with 169.

Go to System Preferences -> Network. Click on 'Advanced' and select 'TCP/IP. Click on the 'Renew lease' button. If this doesn't work then, in System Preferences -> Network, create a new location (you might as well call it "School"), select the new location and then remove all connections except Ethernet from the list on the left and try re-newing the lease again.

unfortunately none of that seemed to change anything. in network utilities it says I'm sending 500 packets (using the new location) and receiving 41. If I didn't use the new location it sends 300 something packets. Also renewing the license doesn't seem to change anything. My ip address is still 169.xx.... and subnet mask is 255.xx..... but I'm not getting anything for router or DNS server of search domains in network preferences.

An address starting with 169 means your Mac is assigning an IP address because it can't connect to a DHCP server. Have you tried a re-boot? Always worth doing with problems of this nature, cures a panoply of ills! If after a re-boot it's still not working, then in the 'School' location, remove Ethernet and add it back in, effectively re-creating the network connection. Might even be worth re-booting between removing and adding it back in! Come back to us if still not working.

i'm having the same problem. When i go to assist me then diagnostics, network settings is yellow, and internet and server are both red. my IP starts with 169 and when i try to make a new location it says i cannot connect to ethernet network automatically. Please help the wifi at my school is terrible.

Earlier we had to reboot the modem and router. Now, my husband's computer will work with Ethernet, but mine will not. I can only get connectivity with my Mac via wireless (192.168.X.XXX). I've checked network settings and it says Ethernet is connected but cannot connect to the Internet.

What I found is when I went into "network" in settings and where they list the Ethernet, Wi-Fi, FireWire and Bluetooth where it said I was connected I deleted the ethernet using the - sign, then added it again using the + sign and choosing ethernet in the drop down menu in interface.

I started with my ethernet not connecting during Catalina. Here's how I solved this problem. It was time to update, so I let my iMac Retina upgrade itself to Big Sur and the issue still remained. Having successfully tested the router gateway, I knew it had to be the iMac hardware or the OS.I did a clean install of Big Sur. I backed up my important files, used the recovery utilities to wipe my SSD, made a bootable USB drive with Big Sur onboard and did the deed. Now there are no further ethernet issues. Hope this helps you.

On my previous Macbook Pro 16in Intel (Monterrey) and before, have always had my computer connected to OWC thunderbolt dock, and thunderbolt usb-c 10g ethernet attached to the dock getting me about 1.7gbps.

On the new M1 MacBook Pro 14 (Monterrey - Stable version shipped with), it still works but now in Preferences > Network > Thunderbolt Bridge shows as not connected (even though it is). The problem here, is even though I have that set to override wifi, wifi appears first in the list and thus uses the wifi because it thinks the ethernet isn't connected. If I disable wifi, then thunderbolt bridge is on top, still says not connected, but able to get full ethernet speeds. But then when I unplug and want to use wifi i have to manually re-enable wifi.

So after trying the crossover cable with no joy I came across another forum discussing a similar but different issue. The suggestions was made to turn off wifi on the macbook as that may be overriding the ethernet connection.

In my search I also found a post on Lasergods about making the Ruida wireless; -your-ethernet-capable-dsp-wireless/

I wish I had found this first as I would have spent the $50 on another wireless router instead off the USB Ethernet adapter I needed for the direct ethernet connection. Oh well. Live and learn.

Solution;

Before proceeding consider making the Ruida wireless as per this post; -your-ethernet-capable-dsp-wireless/

For the cost of a USB to Ethernet adapter you may be able to purchase a wireless router and have a wireless option.

(With the ethernet cable removed, this same mac also connects just fine to the web when wifi is turned on. A different LAN ip number is established obviously.... but again, I can't use wifi for my server application)

I log into the Rogers modem to administrate these necessary Port Forwarding/UDP settings. I select 'Add Port Forward', I select my macbook and enter the proper port number and UDP setting. The big green check mark comes up and says 'Finished'. However, when I look at the Port Forwarding page, it lists "No Associated Device" with an ip number that matches my macbook's wifi LAN ip number (?)

@WDP1 I'm not sure what can be done about this. When the Internet protocols were first designed 40+ years ago, the designers never thought about the possibility of having multiple network interfaces connected to the same logical network. Although this is now typical with Laptop computers, it's not typical of servers, and port forwarding on IPv4/NAT firewalls never handled situations terribly well where a device could join a network using different interfaces that would result in them also taking on different IP addresses.

In the case of your Mac, when it is both Ethernet and Wi-Fi connected, it will prioritize the use of those interfaces and will (typically) only use one when initiating connections, unless the network application binds to a specific interface.

I don't know of any solution to getting this working better unless you have your Mac connected by Ethernet, disable Wi-Fi, and get port forwarding set up on the Ignite gateway to the IP address corresponding to your Mac's Ethernet adapter.

Your very last paragraph is exactly what I've been attempting to do, but the router wouldn't recognize the active LAN ip of ethernet connected mac. (active ip according to the mac's System Preferences/Network)

I have had the same issue but disconnecting and reconnecting the adapter to the computer usually gets it going. I have seen some what better results with the ethernet/thunderbolt2 to thunderbolt2/USB-C combination of adapters. Those adapters are all Apple branded as well. Plus none of our 2017 MBP's are touchbar not sure if that could have anything to do with it.

We are a school district so we went with the Belkin adapter for teachers/staff and the double dongle setup for tech staff. With the idea that only tech staff would need the netboot/internet recovery functionality. So far wireless has not been an issue so the Belkin adapters don't get used much.

Have you guys found an Ethernet solution for MacBook Pro with USB-C ports only which works? (Well except that USB-C to Thunderbolt + Thunderbolt to Gigabit Ethernet Adapter by Apple? I just don't like this adaptors chaining which could maybe bring even more troubles).

My problem is definitely not in the network because over Wi-Fi everything works great. But actually you need Ethernet connection for Internet Recovery, because it seems like there's another bug with Apple where especially on MacBook Pro with Touch Bar the EMBEDDEDOS on your EFI partition doesn't get personalized over Wi-Fi Recovery, just over Ethernet only.

I wanted to share my finding... I am using the Tripp-Lite Multi Function device (Model U444-06N-VGU-C) connected to a 12 inch Macbook. I had the Ethernet plugged in and the power brick into the pass through port. Upon booting into the Internet Recovery mode, it did not seem to recognize the adapter. It required me to choose a wireless network. After the initial recovery image was downloaded and initialized, the GUI loaded. I opened up terminal and executed an ifconfig command. It showed both en0 and en1 as connected. This surprised me based upon what I read above. The en0 had an IP address from the wired subnet where as the en1 had an IP address from the subnet of the wireless network that I chose. I exited the terminal, turned the wireless adapter off, wiped the hard drive, and started the OS reinstall.

I pulled up my firewall logs and limited to the wired (en0) IP address and so far it has downloaded 5.47 GB worth of data. So, while it seemed to need the wireless for the initial IR GUI image download, once the recovery module loaded, it recognized the adapter and initialized the kext for the rest of the install.

When connected, the laptop can route to servers and hosts on our LAN as expected, but it cannot route to any external sites (Google, Bing, Apple, CNN etc). This includes ping, traceroute, etc (not just http). DHCP works.

I did some testing with using wireless, and if i remember correctly worked fine using a SPrint MyFy, didn't try using our campus wifi mainly because of needing to authenticate (didnt want that to be a solution for us). But i may re test to see if using campus wifi works as well.

This morning my Break/Fix manager just emailed me saying the Belkin USB-c to Ethernet adaptor is no longer available on Apple site for purchasing, but a new $350 docking station is. I guess thats Apples answer, an over prices docking station. Lets see if a Apple brnaded adaptor shows up in a few months.

Going to dig up this post in hopes it helps save others from some frustration. There is a way to enable third party Ethernet adapters as long as you can get into recovery, either an open WiFi network or local recovery on the hard disk.

Once there you can now plug in the Ethernet adapter of your choice. Go to utilities>network utility. Look for the adapter and the nickname associated with it from the drop-down i.e. USB 10/100/1000 LAN en4. Remember that nickname. Close out of network utility and open up terminal from Utilities in the menu bar. You are going to run 2 commands. The first will activate the adapter. The second will assign a DHCP lease to it.

3a8082e126