Pull down the “Locations” menu and choose “Edit Locations”, then click the plus button, give the new network location a name like “Yosemite WiFi” then click Done.Open the Apple menu and go to System Preferences, then choose “Network”.Finally, we’re going to set a custom MTU size that is slightly smaller than the default, which will get rejected less often by a router, it’s an old netadmin trick that has long been used to fix network troubles. Then, we’ll set DNS on the computer rather than waiting for OS X to get DNS details from the wi-fi router, which alone can resolve many issues with DNS lookups, since Yosemite seems to be finicky with some routers. First, we’ll use a completely new network setup. What we’re doing here is creating a new network location which is going to have a configuration different from the defaults. 2: Create a New Wi-Fi Network Location with Custom DNS This alone may resolve your problems, but if you’re continuing to have trouble we recommend following through with the second step which means using some custom network settings. This forces OS X to recreate all network configuration files. Turn ON WI-Fi from the wireless network menu again.
Os x yosemite server mac#
Move all of these files into a folder on your Desktop called ‘wifi backups’ or something similar – we’re backing these up just in case you break something but if you regularly backup your Mac you can just delete the files instead since you could restore from Time Machine if need be.Within this folder locate and select the following files:.Library/Preferences/SystemConfiguration/ From the OS X Finder, hit Command+Shift+G and enter the following path:.Turn Off Wi-Fi from the Wireless menu item.This is particularly effective for Macs who updated to Yosemite that may have a corrupt or dysfunctional preference file mucking things up: This is one of those tricks that consistently resolves even the most stubborn wireless problems on Macs of nearly any OS X version. Manually trashing the network plist files should be your first line of troubleshooting. 1: Remove Network Configuration & Preference Files
This involves editing some system level configuration files, and you should probably start a Time Machine backup before proceeding just to be on the safe side of things. With that said, we’ve been able to resolve the problem for many Macs by using the steps outlined below. Accordingly, it’s challenging to offer a single solution to the Yosemite Wi-Fi problems that users are experiencing. Lesson learned: Don't rely on wizards and other user-friendly stuff.It should be noted that it’s difficult to point to a single cause for sudden and unexpected wireless troubles with any OS X version, and there may be different causes for different users. I guess I should have seen it, but I didn't.Īfter I changed the subnet mask in the DHCP scopes everything went back to normal. When you create a scope Apple will assign a default subnet mask (255.255.0.0). After an hour of troubleshooting (more and more DHCP clients were failing in the network), I found the problem Getting connectivity with a device took a very long time, and when the device got an IP address, it was from a different network (?)> So it couldn't communicate across the network.Īt first I began to wonder if I had mixed up the VLAN names and tags, but those were correct. Upon testing I ran into the weirdest behaviour on my network. I just had to fill-in the blanks (very user friendly), and OS X did the rest. The IP addresses for these scopes are all in the 192.168-range (class C subnets), so when I created the scopes I had to go through a simple wizard in the Server App. So I also use several DHCP Scopes for those segments. My server uses 802.1q (VLAN-tagging) to connect several different VLAN's which I feed into several Virtual Machines.
Os x yosemite server install#
So after a couple of hours of pondering if I had forgotten to backup something, I started with a clean install of OS X Yosemite (10.10).Įverything went smooth, until I started using the DHCP service that comes with the Server App add-on. It still ran Snow Leopard, and it was time to start with a clean slate. This week I re-installed my Mac Mini server at home.