Mac OS X Lion Server :: Directory Editor Fails To Connect?
Mar 12, 2012
I have several messages "Module: SystemCache Misconfiguration detected in hash 'Kerberos'" in my System Logs. Having browsed the forums, I found this most likely to be caused by User Records in the local LDAP database created with Workgroup Maager instead of Server.app. [URL]I wanted to fix these entries with the directory editor pane but the tool fails to connect toDirectory service /LDAPv3/127.0.0.1/.If I supply wrong user credentials, the message indactes a wrong username or passworf, but if I give the right credentials for the administration user of the LDAP directory, it simply sais "failed to connect (5000)". how I can convince the directory editor to let me edit the database?
I'm trying to do something fairly simple — allow users from an external LDAP server to access services on my Lion server. Following Apple's instructions, I can't find the "Connect to Directory" choice in the Manage menu of Server.app. I always start by turning off OD by using Server Admin to configure as "Standalone Directory". This is what I see in Server.app after doing that.
Apple's instructions say if the Manage Network Accounts option appears, you need to first set up the server to host network accounts. So I click that option, which seems the be the same thing as creating an OD Master using Server Admin, as far as I can tell.Then I try to add a new user.For some reason, the "type" dropdown list exists, and lets me choose "Imported user from directory", even though I haven't setup any other directory server. Of course, when I search for a username, it finds nothing.Apple's instructions say to now choose "Connect to Directory" from the Manage menu, but that option doesn't show up. I only have what shows in the screenshot above, sans "Manage network accounts" now. How can I get this to appear?
I am running a 10.7.3 Lion Server bound to Active Directory. There are only several local admin users on the machine; everyone else authenticates against AD. AFP connections work fine, using both local and AD accounts. SMB connections work fine if you use a local account but any AD account is rejected as having the wrong password when connecting via SMB. I've tried using the adusername trick (our AD server is named "ad") even though you're not supposed to need that with 10.7.2 and above... it doesn't help.Â
I have tried both a Windows 7 client and a 10.6 client, specifying SMB as the protocol in the Connect To Server dialog. Both fail, and they also take several minutes before reporting the bad password (the slowness in responding is yet another problem I've read as being an issue). Checking the kdc.log file on the server I see:Â
2012-02-09T09:54:22 digest-request netr: failed user=AD\dlennie DC status code c000006d 2012-02-09T09:54:22 digest-request: netr failed with -1073741715 proto=ntlmv2 2012-02-09T09:54:22 digest-request: od failed with 2 proto=ntlmv2
[code]....
I am using the full DNS name for the server, and on my test clients there are no firewalls or other network issues that would prevent connection to the server. We're mostly Macs here but the Windows users become a rather vocal group when something doesn't go their way. The confusing part to me is that AFP authenticates just fine and SMB doesn't.
I am trying to setup test server with following services:
DHCP
DNS
Open Directory
Profile Manager
Software Update
But not having much of success. I have installed 10.7.3 on virtual machine (Using Fusion 4) on Mac Pro and given a 4 GB of RAM. This machine is running in its own bubble, it has no communication even with host. So I have configured DHCP and DNS services which seems to be working fine (I have confirmed with another client which can get IP and DNS server address from this server).
Now whenever I have tried to run OD setup using both tools (Server App and Admin Tool), it takes forever to configure (more than 1 hour) and then it fails with error saying "check your network settings". I have checked and machine has proper IP address (tried both DHCP and Static) and also used "lookup" utility to resolve the DNS address both ways (forward and reverse).
I've recently upgraded to Mac OS Lion Server, and I'm having a big problem that's keeping me from finishing my last bit of work on a project. I've been trying to create network users so that they can sign in on any computer, and access their files via the server, but I've been told time and time again to create a Directory Administrator.Â
I am managing a bunch of Macs and we are using Active Directory groups to assign certificates for 802.11x. I am binding the device to AD using JAMF software and was wondering if I could use a script to then add the deive to an active directory group.Â
1) In an environement that contains two directory servers (one master, one replica), how does a client find the replica in the event that the master goes offline?
2) Is there any command to issue from the client side that will return all available directory servers in the domain?
I have been reading through the Lion Server pages for Active Directory and came across the following question. Does the procedure listed in the URL below allow the users whose Macs are joined to the OS X server, to login with Active Directory credentials. Pass-through auth. for lack of a better term. [URL]...The procedure reads as if it is just joining the server to the domain and not configuring authentication.Â
I've got a new Mac Mini Server that I'm using to set up file sharing for the first time. I've enabled OpenDirectory and verified that the users I'm creating are being created in (they show up in the Server app and Workgroup Manager app, but not in System Preferences | Users).Â
File sharing seems to be working fine, but I don't like the fact that each user has access to their home folder share when they connect to the server using a mac elsewhere on the network. I prefer only the shares I explicitly set up to be available.Â
Thus, a couple questionsWhy is there a home folder created on the server at all? Do I really need a /users/johndoe folder for each and every account in OD?How can I configure sharing such that I won't see the home folder when I connect from another mac on the network? I don't want to leave little "cubby holes" for my users to stuff files into
Im having all kinds of 'not found' issues with lion server but i think alot of them may stem from not being able to stop kerberos from running on Open Directory.Therefore currently im running two Kerberos realms OD and Active directory.. When I try and stop it in terminal it errors see below...Â
shutting down kadmind kadmind shut down shutting down kdc
[code]....
then on server admin it shows kereberos for OD as "running".. still so i know it hasn't worked?
We have a local Admin account on all Macs, enterprise wide, for local and remote administration.
All Macs are joined to Active Directory. Our users DO NOT have Admin rights.Â
On ALL our LION Macs (10.7.4), when joined to Active Directory, we lose functionality to the local Admin account.
We can log into the local Admin account, but the desktop is useless. Nothing opens. We cannot create any files/folders without getting an Access Denied error.
AND then best part... everything on the Desktop, files/folders, are gone! Almost like a bran spankin' new account. With no access to anything locally.Â
So this is my first time really implementing Macs in an Active Directory environment and everything is going fairly well, except when it comes to the Home directory. All of my users are running 10.7, and with the latest patch, they can all log into the Domain without any issue. The problem is that their Home directory in the dock is displayed as a question mark. I'm guessing I'm missing something in the configuration, but everything looks right. Anyone have the 411 about how to set up a Mac user to map a Home directory to a network share on a Wiindows 2008 AD network?
I have an OSX Lion 10.7.4 Server set up with Profile Manager and it is joined to AD.Â
I am able to see AD groups in the Profile Manager groups section. I can also see and add AD users and groups using the server app.Â
I have enabled the "Can Enable Remote Management" check box for Domain Users through Profile Manager. I have also added Domain Admins to the Workgroup group in the Server app. I'm not sure that I want or need either of these options, but they were suggestions to try. I am not able to log on to the Profile Manager or My Devices pages with AD logins.Â
I found these directions about nested groups in Workgroup Manager [URL] but I don't have a [URL] local group or any groups like are shown in the picture.Â
updated to 10.7.4 and cannot turn on my Open Directory service in Server Admin. It's there, but says it is stopped, and it won'y start.After reboot it is still the same.
Adding 10 IMACS with OS 10.7 to my active directory domain. I would like for all users to have the same basic user settings at log in. how I can configure the MAC clients.
I can see this seems to be a common problem, and it is amazing that there seems to be no consensus (that I can find) on what the underlying problem is.I have two Macbook Pro 13's.Pretty much identical setups (Lion 1.7.3 etc.).One, works flawlessly connecting to Wi-Fi whether that is my Airport Express, or any other open or closed networks.The second, will continually refuse to connect to the Airport Express or even a wide-open 802.11b network.It will continually pop up the "connection timeout" erorr, and refuse to connect.Iphones etc all connect perfectly.Even when connecting to the iPhone hotspot - the same error.
This will happed consistently, until I give up.I can leave it for a day (use ethernet), and come back tomorrow, and voila - it will connect.I may be able to use it for a day or several, but once it decides to 'fail', there is virtually nothing I can do to bring it back it will continue to fail over and over again.All updates are applied, I've cleaned out all other networks etc from the list.Tried all civilized things that I can.Anyone have any other insight? I was thinking to yank the wi-fi module from the working notebook to the non-working one as a test.
I'm getting ready to migrate our company server to a new server box. I'm doing a complete clean install, and migrating specific information over (we had some corruptions from the initial installation Lion Server). All our users are in LDAP, not the Local directory, and I can't seem to figure out (and don't have the ability to test) if using the Ser Admin app's Archive feature of Open Directory, will include all LDAP information. My understanding is that if I create an archive and restore to it, then all of my users and there information will be put back like nothing happen, but can't get any clarification on it.
I work remotely a lot. After I upgraded to Lion server, I am unable to connect to the VPN service remotely unless I physically go over to the server (mac pro) and log into the desktop manually.Â
Previously, if my Snow Leopard server restarted (due to power failure, etc) and it re-booted up to the login screen, I could still logon to the VPN remotely as the VPN service would always startup (at the login screen) without a user having to be logging in. Â
Now, with Lion Server (10.7.4), if the server restarts, I cannot login back to the VPN. I have to get someone to go over to the server and manually login, then I can access VPN just fine. (I do not, and will not turn automatic login on on my server due to the huge security risk.)Â Â
How do I get the Lion Server VPN service to startup before or at the logon screen even if no user is logged in?
I am running an open directory/active directory network. Authentication is from the Windows server 2003 active directory. It has worked fine until the last month. Now clients stop authenticating & when I check the AD plugin it says network accounts are not available. I can force the server to unbind, then renew the binding & everything works great.Is there any work around or fix for this other than upgrading the windows server to 2008?Â
I have a few labs that will be running Tiger. I have an XSERVE that is running Tiger Server. All of my users are stored on a Windows 2003 server in AD.
I know how to bind an OSX machine to AD. What is the best way to set up my mac labs/Xserve so that when the users log in they get their home folder on the Windows server but have their preferences managed by Workgroup manager?
i want to learn one think about Mac OS X Server 10.6.i have got 300 clients Windows and i want to setup Mac OS X Server work like a Active Directory same as Windows... (User's Account,Profile ....etc) is it possible with Mac OS X Server or not ?
I am currently trying access profile manager on both my macbook air and iphone 4s on local wifi. However, it would just hang when i try to access it via "http://macmini.local/profilemanager". If i try go to go url...I can access url... fine and ping "macmini" fine.
Is there an option in Mac OS X Lion (10.7.3) where I can set my system to automatically login to my university's remote folders and drives on their network?
I upgraded to 10.7 from 10.6.8. I've ran all the updates etc, but now I cannot connect to my OS X Server (10.6.8) or any other machine for that matter. The server appears in my finder window and will allow me to connect as a guest but if I try to login by clicking connect as or by using COMMAND+K and typing the IP I get a long wait after entering my PW only to receive an error that says "There was a problem connecting to the server "pggfx01". Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator. It should be noted that I have other machines that came with Lion that connect without issue and other machines still running 10.6.8 that connect flawlessly.
I back up my laptop on a backup disk at work (with their permission). I connect to the network, click on my work Mac mini (1.66 Core Duo, 2 GB RAM, OS 10.6.8), and then click on the MiniStack backup drive to mount it on my desktop.But recently I upgraded to Lion and now that's not working. I can see the mini in the Finder sidebar, but when I try to connect to it just says, "Connection failed" and doesn't give a reason.
Info: MacBook Pro, Mac OS X (10.7.3), 4 GB RAM, 160 GB HD
