Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Operating System
can't connect to 169 network
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="jvf" data-source="post: 1208722" data-attributes="member: 196366"><p>Hi MikeM,</p><p></p><p>Good call. As you can probably tell, I’m not a Maxpert yet. I checked on my wife’s Mac. Indeed, Safari brings up the proxies tab found in network preferences and is not a part of Safari itself.</p><p></p><p>Unfortunately, I’m not at the 169 network now. But, from memory, the Mac had a valid assigned 169 address of 169.254.93.9 (.3 for my wife’s Mac) with the usual subnet mask of 255.255.255.0 and the router entry correctly showed our DHCP router’s address of 169.254.93.69. DNS server tab was blank on my wife’s Mac. I clicked “advanced” and added it to the DNS field on the “upset” Mac but it didn’t help so I deleted it (it’s now gray, it didn’t really disappear.) I seem to recall that, after a short period of time on either machine, the DNS entry field would appear under the router field in the first network preference window and be filled in with the router’s address. </p><p></p><p>From this I conclude that the DHCP router has done its job and, in spite of the incorrect warning about having a “self assigned address”, the Mac’s TCP/IP stack has been correctly figured and it’s good to go.</p><p></p><p>Based on the realization that the proxy info displayed by Safari is really a system setting I am even more confused because the settings look identical on both machines with no proxies checked. I edited the “bypass proxy” window to erase the 169.254/16 entry on the “upset” Mac but that didn’t do anything. At that point I was guessing because I don’t understand the implications of “bypassing” the proxy except to think that bypassing any 169 proxy might actually be a good thing.</p><p></p><p>Firefox is configured to “use system proxy settings” and can connect but Safari cannot connect on either machine. So, why not? What proxy configuration does Safari need that Firefox doesn’t need? That is the question. However, to complete the test, I need to install Firefox on the recalcitrant Mac to see if it can connect. I am awaiting approval to do so and should know sometime during the weekend. </p><p></p><p>jvf</p></blockquote><p></p>
[QUOTE="jvf, post: 1208722, member: 196366"] Hi MikeM, Good call. As you can probably tell, I’m not a Maxpert yet. I checked on my wife’s Mac. Indeed, Safari brings up the proxies tab found in network preferences and is not a part of Safari itself. Unfortunately, I’m not at the 169 network now. But, from memory, the Mac had a valid assigned 169 address of 169.254.93.9 (.3 for my wife’s Mac) with the usual subnet mask of 255.255.255.0 and the router entry correctly showed our DHCP router’s address of 169.254.93.69. DNS server tab was blank on my wife’s Mac. I clicked “advanced” and added it to the DNS field on the “upset” Mac but it didn’t help so I deleted it (it’s now gray, it didn’t really disappear.) I seem to recall that, after a short period of time on either machine, the DNS entry field would appear under the router field in the first network preference window and be filled in with the router’s address. From this I conclude that the DHCP router has done its job and, in spite of the incorrect warning about having a “self assigned address”, the Mac’s TCP/IP stack has been correctly figured and it’s good to go. Based on the realization that the proxy info displayed by Safari is really a system setting I am even more confused because the settings look identical on both machines with no proxies checked. I edited the “bypass proxy” window to erase the 169.254/16 entry on the “upset” Mac but that didn’t do anything. At that point I was guessing because I don’t understand the implications of “bypassing” the proxy except to think that bypassing any 169 proxy might actually be a good thing. Firefox is configured to “use system proxy settings” and can connect but Safari cannot connect on either machine. So, why not? What proxy configuration does Safari need that Firefox doesn’t need? That is the question. However, to complete the test, I need to install Firefox on the recalcitrant Mac to see if it can connect. I am awaiting approval to do so and should know sometime during the weekend. jvf [/QUOTE]
Verification
Name this item. 🍎
Post reply
Forums
Apple Computing Products:
macOS - Operating System
can't connect to 169 network
Top
