Re: mac anmeldung am SMB server 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Tobias Redelberger (T.Redelberger_at_starnet-services.net)
Date: 03/18/05


Date: Fri, 18 Mar 2005 19:59:05 +0100

Hi Torsten,

Q: What can I do if my network administrator wants to have a private local
domain called "local"?

A: The ideal solution is not to use the name "local" for private unicast DNS
domains. However, for compatibility on networks where the administrator
insists on using the name "local", Mac OS X 10.3 can be configured to look
up "dot-local" names first using multicast, and then if that fails, using
unicast, by installing a piece of software called
DotLocalLookupConfigurator.

-> http://www.multicastdns.org/DLLC/

Source: http://developer.apple.com/macosx/rendezvous/faq.html

Ansonsten noch hier:

Directory Access 1.5 Help - Configuring Access to an Active Directory Domain
http://docs.info.apple.com/article.html?artnum=151444

und aus einen früheren Posting von mir:

"using the Directory Access application under Finder + Applications +
Utilities + Directory Access icon"

lies mal, wenn Problem damit auftritt, weiter hier:

Problem:

While trying to add a MAC (10.3.2) to a windows 2003 domain environment, the
following error occurs.

#####################################################################

Invalid domain

An invalid Domain and Forest combination was specified. You should enter a
fully qualified DNS name for the domain and forest (e.g.,
ads.company.com)

#####################################################################

You will receive this message while using the Directory Access application
under Finder + Applications + Utilities + Directory Access icon. Click the
"click the lock to make changes". Enter the MAC's admin account and password
to unlock the application. Enable the Active Directory 1.0.1 by clicking the
checkbox. Click the "Configure" button at the bottom on the window. Fill in
the form as follows

Active Directory Forest: Your forest
Active Directory Domain: FQDN
Computer ID: Enter the name of the MAC, this name will be added to the
Computers folder in AD.

After entering this information click the "Bind" button and then enter the
administrative user name for the Windows 2000\3 domain and password. After
this is done, you will receive the error message list
above; follow the steps below to solve the problem.

Solution:

To fix the problem go to the first Windows 2003 server that was promoted
into a DC (Domain Controller). Open the "Default Domain Controller Security
Settings" MMC under [Start] + Programs + Administrative Tools.

Expand the Local Polices by clicking on the + sign to the left of the icon.
Next, Select the Security Options icon. Now look at the right hand window
and change the following Policies.

1. Domain member: Digitally encrypt or sign secure channel data
(Always) DISABLE
2. Microsoft network server: Digitally sign communications (always)
DISABLE
3. Microsoft network server: Digitally sign communications (if client
agrees) DISABLE
4. Network security: LDAP client signing requirements NONE

Close off the Default Domain Controller Security Settings MMC and that
should fix the problem. You will have to wait until the domain policy is
refreshed or you can reboot the Windows 2003 Server. Also make sure that
your MAC has the same time as the domain controller or it will not work.

Source:
http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&th=1b0258857104895d&rnum=3

Und hier grundsätzliches zu Windows (SBS2003) + Mac:

How-To - "Connecting to Windows computers and servers from your Mac"
--> http://docs.info.apple.com/article.html?artnum=151670

Services for Macintosh/AppleTalk
Once you've installed Services for Macintosh, there are a few configuration
steps you need to complete before the Macs will be able to connect. Follow
these steps to complete those configurations:

1. Right-click on My Computer and select Manage.
2. Under System Tools, expand Shared Folders.
3. Right-click on Shared Folders, and select Configure File Server for
Macintosh. 4. In the Security field, select "Apple Clear Text or Microsoft"
from the
Enable authentication menu. This is a specific option. There are also
options for "Apple Clear Text" and "Microsoft Only." The one you want is
"Apple Clear Text or Microsoft."
5. Click Apply, then OK.
6. Click on Shares to see the list of existing shares on the server. You
need to have at least one Macintosh share created or the Mac will have
nothing to connect to when it authenticates. There should be a share called
"Microsoft UAM Volume" but that's not going to be very useful for your
users.
7. Right-click on Shares and select New Share.
8. Click Next.
9. Enter the path to a folder that you want to make available to your Mac
users. You can browse to it or just type it in. Then click Next. 10. Enable
the "Apple Macintosh users" checkbox. If you already have a
share created for this directory for Windows users, uncheck the "Microsoft
Windows users" checkbox.
11. Enter a name for the share in the "Share name" field and click Next. 12.
Click Finish. 13. Click Close.

On your server, make sure that the File Services for Macintosh are indeed
installed and running and that the Appletalk protocol is set to use the
network interface that will communicate with your Macs.

>From your Macs, you can select Connect... From the Go menu (or type Command
+ k) and enter "afp://servername" or "afp://serverIPaddress".

-- 
Tobias Redelberger
StarNET Services (HomeOffice)
Schoenbornstr. 57
D-97440 Werneck
    Tel:   +49-(0)9722-4835
Mobil:   +49-(0)179-25 98 341
 Email:   T.Redelberger@starnet-services.net


Relevant Pages

  • Re: Questions before I buy a PowerBook
    ... Is there a way that I could remote desktop to my desktop windows ... That would depend entirely on how the network you are connecting from ... connect to restricted Windows servers at work from home via a VPN, ... also had to get special VPN software for Mac OS X to do it. ...
    (comp.sys.mac.portables)
  • Re: Transferring files from windows xp to mac os x with an ethernet cable
    ... to network connections on the windows machine it always says that the "1394 Connection" is connected, even when there's no ethernet cable plugged in.. ... i have to use the usb connection to connect my modem to the windows machine; when i connect the same modem to my mac i just use the ethernet jack and it works right away.. ...
    (comp.sys.mac.system)
  • Re: Transferring files from windows xp to mac os x with an ethernet cable
    ... for example, when i go to network connections on the windows machine it always says that the "1394 Connection" is connected, even when there's no ethernet cable plugged in.. ... i have to use the usb connection to connect my modem to the windows machine; when i connect the same modem to my mac i just use the ethernet jack and it works right away.. ...
    (comp.sys.mac.system)
  • Re: DVD transfer fun (not)
    ... "Network" or something similarly obvious). ... Windows 95 doesn't support the "self assigned ... Set up the Mac to use the other IP address, ... After rebooting the Windows computer, with the network cable connected, ...
    (comp.sys.mac.apps)
  • Re: SBS2003 + Macintosh
    ... "using the Directory Access application under Finder + Applications + ... While trying to add a MAC to a windows 2003 domain environment, ... To fix the problem go to the first Windows 2003 server that was promoted ... Microsoft network server: ...
    (microsoft.public.de.german.backoffice.smallbiz)