Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Inernet access glitch.

Martyimac

Martyimac

macrumors 68020
Original poster
Aug 19, 2009
2,492
1,730
S. AZ.
So far, since Beta 1 and still there on most current beta. Internet access not available after overnight sleep. I have to go into settings and de-activate ethernet, wait a few seconds then re-activate ethernet. Then it works.
And no, haven't tried it with wifi, personal preference.
I have reported this through Feedback assistant every time a new beta comes out. No change.
 
Mac model? VPN? if you use privat relay - try turning it off. Which DNS? what does the system log in the console report?
 
Slartibart said:
Mac model? VPN? if you use privat relay - try turning it off. Which DNS? what does the system log in the console report?
Click to expand...
M4 iMac, no VPN use, Private relay not in use and never has been. Couldn't find anything in the console report. The most interesting thing is that it has now fixed itself. Has not occurred since Tuesday 15 July. PFM it would seem.
 
I’ve been installing the beta on multiple Macs as it’s been stable enough. Installed it on my M4 Mac mini and not getting any internet access. No vpn installed either. Multiple resets/forget network.. nothing has solved it for me yet.
 
Okay, a few things:

  • check wether /Library/Preferences/com.apple.captive.plist exists. If yes, delete. restart. check.
  • In the TCP/IP settings for the ethernet connection provide a DHCP Client ID, renew the DHCP lease. Create a network location. <- these two things fix a lot of network related problems in general.
  • Depending on your router/switch setup it might also be insightful to check wether providing a manual IP has an effect, as well as forcing IP4 use. (btw. get the ethernet connection an IP after wake-up when you can not connect with the outside world? If yes, what kind? If not, see next 😀).
  • You might be able to fix the problem when it occurs by simply renewing the DHCP release - worth checking IMHO (one cn then script that comfortably).
 
Slartibart said:
Okay, a few things:

  • check wether /Library/Preferences/com.apple.captive.plist exists. If yes, delete. restart. check.
  • In the TCP/IP settings for the ethernet connection provide a DHCP Client ID, renew the DHCP lease. Create a network location. <- these two things fix a lot of network related problems in general.
  • Depending on your router/switch setup it might also be insightful to check wether providing a manual IP has an effect, as well as forcing IP4 use. (btw. get the ethernet connection an IP after wake-up when you can not connect with the outside world? If yes, what kind? If not, see next 😀).
  • You might be able to fix the problem when it occurs by simply renewing the DHCP release - worth checking IMHO (one cn then script that comfortably).
Click to expand...
The plist referenced did not exist.
The way I get access back is to deactivate my ethernet. Wait a few seconds then reactivate. Once this is done enthernet access is fine until I restart the next day after overnight sleep.
 
Martyimac said:
The plist referenced did not exist.
The way I get access back is to deactivate my ethernet. Wait a few seconds then reactivate. Once this is done enthernet access is fine until I restart the next day after overnight sleep.
Click to expand...
I understood that. But that might be a thing which is located on the router side…
 
Slartibart said:
I understood that. But that might be a thing which is located on the router side…
Click to expand...

gigapocket1 said:
Wonder if the latest beta will also solve your problem
Click to expand...
This morning all went well. So hard to say if it was the the options @Slartibart recommended or the newest beta. Time will tell because last week the issue didn't show up, for one morning restart then it started again.
 
Slartibart said:
Okay, a few things:

  • check wether /Library/Preferences/com.apple.captive.plist exists. If yes, delete. restart. check.
  • In the TCP/IP settings for the ethernet connection provide a DHCP Client ID, renew the DHCP lease. Create a network location. <- these two things fix a lot of network related problems in general.
  • Depending on your router/switch setup it might also be insightful to check wether providing a manual IP has an effect, as well as forcing IP4 use. (btw. get the ethernet connection an IP after wake-up when you can not connect with the outside world? If yes, what kind? If not, see next 😀).
  • You might be able to fix the problem when it occurs by simply renewing the DHCP release - worth checking IMHO (one cn then script that comfortably).
Click to expand...
Figured I would update this thread.

I gave up. This morning was the worst. Neither wifi or ethernet connections would connect to the internet. I fiddled around for about a half hour when all of a sudden, I had internet. It's to weird for me. Now probably the fact that I am senior in my 70's has something to do with my inability to fix the issue. But in the last three major updates to MacOS, I never had these kinds of issues.

But thank you for your tips, they were appreciated and worked fine for two days, until the next beta come in and messed everything up.
 
Wifi and ethernet affected… try changing the MTU to 1460 for the Wifi as well as ethernet connection (Default is 1500).

Other than that, you connect the ethernet cable through the power supply, I assume? Did you try a different cable? I mean, yes, betas are tricky, but there seems to be something particular with your setup…
 
Last edited:
Slartibart said:
Wifi and ethernet affected… try changing the MTU to 1460 for the Wifi as well as ethernet connection (Default is 1500).

Other than that, you connect the ethernet cable through the power supply, I assume? Did you try a different cable? I mean, yes, betas are tricky, but there seems to be something particular with your setup…
Click to expand...
I have taken the M4 iMac, which was the beta machine, back to Sequoia. And yes, I connect the ethernet through the power supply. And guess what, absolutely NO problems. Between my Eero router and the new cables, which were installed before the first developer release, nothing worked well in beta Tahoe. Under Sequoia everything works as it should.
 is doing a lot of things in Tahoe they haven't talked about. Tahoe will be the first MacOS operating system release that I will not upgrade to on release day. Neither of my macs will get Tahoe until the first .1 release.
But because I am curious, I may start testing the public releases, well, maybe as it gets close. 🙂
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back