Tag Info

New answers tagged

0

Short answer: make sure the new DNS server has (or can quickly resolve) both forward (name -> IP) and reverse (IP -> name) entries for the Mac server. Long answer: OS X Server tends to like to look itself up via DNS, even for things you wouldn't expect DNS to be involved in at all. (I think it's a side effect of checking its own hostname via a reverse ...


0

Killing the Window server will take all it's child processes with it. If you can log in as the user via SSH then you can use: $ alias maclogout="osascript -e 'tell application \"System Events\" to log out' " $ (sleep 1; maclogout) & Expect to wait almost two minutes before the login window appears. In my testing the logout dialog wouldn't appear ...


1

The following command with nmap with root privilegies (or using sudo): sudo nmap -sP 172.31.201.0/24 | awk '/Nmap scan report for/{printf $5;}/MAC Address:/{print " => "$3;}' | sort results in: 172.31.201.80 => 00:50:56:AF:56:FB 172.31.201.97 => 00:26:73:78:51:42 server1.company.internal.local => 3C:D9:2B:70:BC:99 ...


3

Mac OSX has Active Directory support. Here's a best practices document from Apple. You should be able to use Active Directory to provide both logins and file shares.



Top 50 recent answers are included