In a library with an iPad and a MacBook Pro (MBP) on unsecured WiFi. Websites in Safari on the iPad are showing no problems.
On the MBP, Safari says “server unexpectedly dropped connection” for every website tried.
On Firefox, it’s connection timed out.
Tor is able to connect to directory server but unable to establish connections to any of the entry nodes it offers. The log shows the connection failures are of three different types. All are on port 443, and my browsing is always https when possible. But https is working on the iPad.
Ping takes 40-100 milliseconds to echo the same domains that the web browser cannot reach.
Hard to imagine library staff having any reason for device detection, if even the ability to implement it.
Devices forty centimeters apart, so probably on the same router.
What would cause this inconsistency?
UPDATE: Both devices have behaved as expected everywhere else as long as I’ve owned them. I risked reprimand :-) by transferring the Cat-5 cable from their Windows box to the MBP. en0 became active, but would not connect even to their router. Prefs said that I had a self-assigned IP address, but the menu said using DHCP, and renewing the lease got a 169.x.x.x address which I would never manually assign, and is weird because their WiFi router is 172.16.110.1 according to trace route.
DNS was resolving host names on both devices. Safari has no extensions installed, yet when I change https to http, it gets changed back. Firefox has “https everywhere” but turning it off does not fix the problem. Tried to check port 80 in shell but there is no telnet executable!
sftp times out on the command line. No ftp executable either (grr). Finder connected to the ftp port and displayed contents, but then announced connection interrupted—and about 1.5 seconds later entire screen went gray; had to reboot. Second try, Finder gets the spinning pizza, and won’t do anything else, not even shut down on the menu bar. Relaunch from the dock killed the Finder and it did not come back. That sounds like something wrong with the MBP but still, the WiFi access worked fine many other places.
In case the above is too confusing or doesn't say everything:
- No problems noted on the iPad.
- MBP could do ping, traceroute, DNS, and whois
- MBP could not do http, https, smtp, imap, exchange, or sftp
- tor could contact its directory servers via port 9001 but could not use the addresses found on port 443.
- although the shell could not invoke ftp, Finder could, and displayed the known contents of the remote directory. However, something about doing so caused Finder to crash the O.S. and to not work properly until the fourth reboot.