Connecting Mac OS X to SBS


Do you use Mac’s in the workplace? More and more SBS customers are asking how to connect their computers running Mac OS X to an SBS 2003 network. In response to those in need,  we’ve written a paper that describes the necessary steps to take. 


Connecting Mac OS X 10.3 and Higher Clients to a Windows Small Business Server 2003 Network has been through a technical review and some preliminary testing, however we’d like to get some customer feedback before it is officially published. If you have a Macintosh computer running Mac OS X 10.3, try connecting it to your SBS network, and then post your feedback about what you liked or didn’t like about this doc! J


UPDATE 01/20/05: A couple of folks have commented that the linked paper is still marked as “Preliminary Documentation.” At this time, we do not have a firm timeline for incorporating your feedback into the doc, so your comments will continue to appear in the feedback below until the paper is updated. Thanks for asking!  -Steve


This posting is provided “AS IS” with no warranties, and confers no rights.

Comments (16)

  1. Well, I have downloaded it, but what application opens it?

    David

  2. Steve Holland says:

    .mht (Microsoft Web archive) files can be opened directly in Internet Explorer 5.0 or later, or in Word 2002 or later. .mht files allow you to package a Web page and its supporting files into a single file.

    -Steve

  3. David Hulse says:

    Word 2004 opened it on my Mac.

  4. Tried Word X. Won’t even open it when I use the Open command from the file menu and select it explicitly. Dragging it on to Word gets it treated as a text file. IE does nothing.

    Maybe a more Mac-friendly file format would help….

    (I have downloaded it twice.)

    David

  5. Susan says:

    Connecting a Macintosh to SBS 2003 Server via SMB:

    http://msmvps.com/bradley/archive/2004/06/14/8181.aspx

    Have you had Erik review these docs?

  6. Eriq Neale says:

    * In "Step 2: Configure DNS" under "To enable unicast .local resolution on a client computer" item 11 should note that there may be more than one line that starts with <i>nameserver</i>. If there is, and the IP addresses are <i>different</i>, the line that contains the IP of the SBS server <i>must</i> be the first one listed.

    * In "Step 3: Share Folders" under "Share Files Using File Services for Macintosh" under "To access shared folders on the server" line 2 notes that <i>ServerName</i> is the NetBIOS name of the server. This is correct with a default install when the NetBIOS name of the server is used to configure the "Server Name for AppleTalk Workstations" in File Server for Macintosh Properties. However, if this name is changed in the File Server for Macintosh Properties, then using afp://<i>NetBIOSserverName</i> will no longer work. I don’t know if it would be more confusing to note that here or not, but it is technically misleading just to say to use the NetBIOS server name here, because Appletalk does not do any sort of IP or NetBIOS lookups when finding a server.

    * In "Step 4: Access E-mail" under To set up and Exchange Server account on a client computer by using Setup Assistant, line 12 should read "In LDAP Server, type the fully qualified domain name of the server (for example, sbsserver.smallbusiness.local)" NOT "In LDAP Server, type the fully qualified domain name of the server (for example, https://sbsserver.smallbusiness.local)."

    * Figure 5 under "Step 4: Access E-mail" has incorrect information. The Domain field should contain the internal domain name of the SBS server (either FQDN or NetBIOS). The Exchange Server field should contain "https://sbsserver.smallbusiness.local/exchange" instead of "smallbusiness.local/exchange". (Compare the information in Figure 5 with Figure 6, which is correct. The information should match, and it does not.)

    * The information in "Access E-mail Using Safari" under "To import the certificate to the Macintosh certificate store" needs to be included in "Access E-mail Using Entourage 2004" as well. Entourage will generate multiple warnings when connecting to Exchange if the SSL cert is the standard self-signed cert. Importing the cert to the store as described in the later section will eliminate the warnings in Entourage.

    * Figure 7 at the end of the document has incorrect information. The data in the "Prefer this domain server" field should read "sbsserver.smallbusiness.local" and NOT "sbsserver.smallbusiness.local/exchange".

  7. I stand corrected. My experience with MAC’s is almost non-existent and I was unaware that mht files do not open in the Mac version of IE. Thanks to the folks who pointed it out. I will be replacing the mht file with a .doc formatted version shortly.

    -Steve

  8. Michael says:

    My office just purchased four new G5 boxes and I went through your steps for adding them to the domain with no problems. I’m a Windows network admin with very little Mac experience so that says a lot for your documentation – very clear.

    -Michael

  9. Thank you Eriq! Your feedback has been added to the "bug" that we’re using to track this content. It will be incorporated into the final version.

  10. Eriq Neale says:

    There may be some additional discussion about the actual items that need to be disabled in group policy. One of the SBS TL’s has said that we should exclude the "if client agrees" policy and leave it as "undefined." My early development of this doc found that both of those policies needed to be Disabled, but I have not yet had a chance to verify. Hopefully this week…

    -Eriq

  11. Eriq Neale says:

    * In the "To enable unicast .local resolution on a client computer" section line 6 need to specify that the lines must be entered AS SHOWN. I’ve already run across a couple of cases where people are looking at the "echo domain.local" line and interpreting that as "echo [internaldomainname].local".

    * Same section, line 9, the line should read "/usr/sbin/EnableUnicastDotLocal" and not "/usr/sbin/EnableUNicastDotLocal". UNIX is very picky about capitalization. 🙂

    * Same section, line 11, we need to make clear that the first line should come back as "domain.local" and not their internal domain name. Basically, everything that’s NOT in italics in the output of that file should exactly match what we have.

    Thanks.

    -Eriq

  12. Dave Eckman says:

    Thanks for this! Been looking for something like this, it’s GREAT!!!

    Went through the article step by step and it worked great for SBS 2000 too. Just had to do an alternative method for disabling SMB signing in Windows 2000 Server.