This is a device-specific problem to my daughter's MacBook Air M2. Four other MacBooks in the family (mine, my wife's, two other daughters) work without this issue.
My daughter uses her Air M2 at home and at school with zero issues. The problem comes any time she tries to connect to a public wifi that has a window pop up for a passcode, agreement, etc. The window always pops up, it stays blank, then an error pops up that says "a problem occurred the webpage couldn't be loaded." We were out of town over the weekend and this issue happened on the hotel network, a coffee house network, the airport network, and the guest network of a college. Many troubleshooting pages I see are about not being able to even connect...her's connects (the window pops up immediately) but it fails to load.
I found a workaround for her which is to go to a browser and type 1.1.1.1. When she does that, the approval/agreement page opens up right away and she's off and running with no issues. But how can I fix needing to do this workaround?
AirM2 is currently running Sequoia, but was having this problem on Sonoma too. As mentioned at the start, all other MacBooks in the family work fine at these same locations.
Thanks for any advice!
My daughter uses her Air M2 at home and at school with zero issues. The problem comes any time she tries to connect to a public wifi that has a window pop up for a passcode, agreement, etc. The window always pops up, it stays blank, then an error pops up that says "a problem occurred the webpage couldn't be loaded." We were out of town over the weekend and this issue happened on the hotel network, a coffee house network, the airport network, and the guest network of a college. Many troubleshooting pages I see are about not being able to even connect...her's connects (the window pops up immediately) but it fails to load.
I found a workaround for her which is to go to a browser and type 1.1.1.1. When she does that, the approval/agreement page opens up right away and she's off and running with no issues. But how can I fix needing to do this workaround?
AirM2 is currently running Sequoia, but was having this problem on Sonoma too. As mentioned at the start, all other MacBooks in the family work fine at these same locations.
Thanks for any advice!