Advertisements

Archive

Archive for the ‘OS X’ Category

Preventing Mac OS X from becoming a Master Browser on Windows networks

March 5, 2012 Leave a comment
  • System Notes: Mac OS X 10.5.x and 10.6.x, Various Windows Clients

The organization I work for has a network of Windows clients, with 3 Mac systems thrown in by the Marketing department for artistic and production needs.  The three Macs are configured for normal Windows network browsing, but are not a part of our Active Directory infrastructure.  They tend to take turns taking over as the master browser for the default WORKGROUP setup, and they have never been able to provide any type of browsing support for any other systems that use the WORKGROUP non-AD setup.

After searching in vain for a solution to this problem in the past, I just recently revisited the issue and finally found a solution, which I present here with other Windows administrators in mind (and this assumes you have at least a minor proficiency in navigating the OS X interface):

  1. Open the Terminal application from the Utilities group in OS X.
  2. Type in sudo nano /etc/smb.conf.
  3. Find and move to the [global] section of the file.
  4. Either change, or add, the following lines:

              os level = 0
              lm announce = False
              preferred master = False
              local master = No
              domain master = False

Restart the Mac once these changes are complete.  This should prevent it from attempting to do anything related to network browsing, at least from a list hosting or master browser perspective.  It will not prevent the Mac from browsing other already available network resources.

Advertisements

Mac OS X not able to connect to Windows Server 2003 R2 running Terminal Services

September 3, 2008 Leave a comment
  • System Notes: Mac Pro, OS X 10.5, Microsoft RDP Client for Mac 1.0.3 and 2.0

Error Message: You were disconnected from the windows-based computer because there were problems during the licensing protocol. Try reconnecting to the Windows-based computer or ask your administrator if the license is properly configured.

Recently, we retired our old, outdated Windows 2000 Terminal Server, and replaced it with a Windows Server 2003 R2 server running Terminal Services. Terminal services are used for remote access only, not for application virtualization or anything extensive like that. We have three Mac clients in the office which also use terminal services for access to a Windows-only database application. This is where the problem came in. With the new terminal server, we reset the licensing database on our existing Licensing Server, which was running on one of our domain controllers. All three of the Mac clients started getting the above listed error message, even though there were plenty of licenses on the licensing server (15 total, to be exact).

After searching around the web, and finding lots of references to this being a “temporary license” not being issued, I eventually stumbled across this link, which led me to checking the directory permissions on Users/Shared/Microsoft/RDC Crucial Server Information/RDC GLOBAL DATA for the logged in Mac user, who was an Administrator on the Mac. We did originally have version 1.0.3 of the RDP client on this Mac, and we had upgraded it to the release version 2.0. The security permissions on this folder were not set to full for the user, and once they were corrected, the problem with the login went away. I still do not understand why the Administrator privileges were not correctly applied on this folder in the first place.