Mountain lion server won't take my password for install

I have never run a server version of apple software.  I am wanting web sharing to host a small website.  This option was removed from sharing preferences in mountain lion. 
I purchased server to avoid the need to use the command line interface.  It was requiring a password and I don't use a password on my system and it wouldn't take a null.  I am finding a similar problem with attempting to install server on mountain lion.
When I run the mountain lion server installer it prompts for an administrator password.  I hit return as I set up the system without an administrator password.  This fails, but works with all other admin password requests for software installation.
Any assistance would be appreciated.
Best Regards,
David Finell

I just decided to setup passwords.  I just wanted to avoid the pain.  It worked.  Now to figure out how to share folders over the web in server.

Similar Messages

  • Mountain Lion Upgrade Won't Recognize AOL password

    I just upgraded to mountain lion and aol won't recognize my password.  Gmail and iCloud no issues at all. Driving me nuts. Quit and tried again-no luck. Rebooted-no luck. Installed latest version of aol for mac-no luck. Unchecked SSL-no luck.  Any suggestions

    Which versions of Office?  If you upgraded from Snow Leopard and you're on Office 2004, you're out of luck.  If you're on a newer version of Office you should be OK.

  • Using mountain lion, why does it take so long for mail to show up?  messages appear on my iphone but not on my iMac

    Using mountain lion on iMac.  Email appears on my iPhone but when I open mail on desktop the messages aren't there and take several minutes before they appear.  Thoughts as to why this happens?  Anyone else experiencing this too?

    Thank you.  Check for new msgs is set for every minute.  However, I got your message on my iPhone and it still hasn't appeared on iMac.

  • Password problem after migrating to Mountain Lion Server

    Hello everyone,
    Yesterday, I migrated our Lion Server to Mountain Lion Server. Everything seemed to work fine. Except since this morning, none of the network user cannot connect to their calendar, reminders, and wiki. They can connect to their account and to their mails. The following line appears multiple times in ApplePasswordServer.Error.log:
    Aug 16 2012 16:52:50 700250us    client response doesn't match what we generated
    It seems that only web services are concerned (vpn, mobile accounts, and mails are working). My initial guess is that the hash computed on the basis of the user password is not computed on the same way on the client machine (which is running Mountain Lion by the way) and on the server. On the other hand, this would be very surprising, since all this stuff is based on standards and unlikely to have changed since Lion.
    I tried to create a new "Test" user. Even this new user, created after the migration, cannot connect to its calendar, etc. I also tried to reset my user password using the Server App. It makes no difference, the same lines appear in the logs.
    Is anyone experiencing a similar problem ? Does anyone have a clue of what to try next ?
    Thanks a lot !

    I found out the following:
    After looking at the contents of the password server database using the slot numbers of several user accounts, it seems that all users where WEBDAV-DIGEST authentication is failing, have two entries for the digest method "*cmusaslsecretDIGEST". This is obviously wrong. All users who can authenticate successfully have only one such entry.
    Deleting and recreating the user account has no effect. In fact, updating the password server with a new entry may actually trigger this error. It could be that all users where this is failing have changed their passwords after the server was updated to Mountain Lion.
    It would be interesting to know if you also see duplicate entries for "*cmusaslsecretDIGEST" in the database. You can display a password server record via the user account's slot number (in your example, the 0xd6ace...) using the command
    sudo mkpassdb -dump <slot-number>
    At the end of the record dump, you should see 10 digest entries with their method identifiers.

  • Complications migrating from Snow Leopard Server to Mountain Lion Server.

    I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
    "Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
    This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
    As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
    My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
    What are my options here ?
    This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
    Clear directions on how to procede would be VERY MUCH appreciated
    Thank you.

    Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
    If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
    Destroy any Open Directory replicas
    Archive your Open Directory Master (to make a backup)
    Note down your DNS records in case they get messed up
    Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
    Keep a full back of the server (you should always have backups)
    Note down your DHCP server settings in case they get messed up
    Note down any other service settings
    Install Mountain Lion
    Install Server.app
    Install Workgroup Manager (extra free download)
    Run Server.app
    Make sure settings for services are as much as possible the same as before
    If your lucky that may be all you need to do, otherwise...
    Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
    Make new Open Directory Master
    Run Workgroup Manager
    Import users and groups you previously exported
    You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
    When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

  • Unable to add/remove users in Mountain Lion Server (Options are greyed out)

    For some reason, im unable to add/remove users in Mountain Lion server. The + and - are greyed out. It seems like something is wrong with the permissons because it looks like it cant write the the Ldav3 file (although that may be speculation). Does anyone have any advice for me? I URGENTLY need to add users.
    Maybe theres a way to restore default permssions for the boot drive (if that in fact is the issue). Hopefully there is a way that I can fix this while leaving all users, groups, their permissions and shares intact.

    Anything interesting and relevent in the server logs?
    Anything interesting in the server alerts?
    Since it's far and away the most common cause of problems with OS X Server and with distributed authentication (Open Directory is entirely based on network encryption and digital certificates and on responses from your local DNS server(s)), verify your local DNS configuration is working and requires no changes with the following Terminal.app (Applications > Utilities) harmless, diagnostic command:
    sudo changeip -checkhostname
    sudo requires an administrative password.  You might get a one-time warning about the sudo, and that can safely be ignored.  The command will display some details, and indicate whether the local configuration appears valid and no changes are required, or further diagnostics for (most) common errors that can arise.

  • Upgrading to Mountain Lion server and all services breaks down...

    Hi!
    I have, after endless hours of scanning logs and .plist and other files' content and permission settings found why Mountain Lion Server.app in some cases doesn't seem to be able to take control over all service, stating it can't read or write its own setting files etc.
    As a Swede I of course run a system set in the Swedish language. Mountain Lion can't upgrade a Swedish system, only fore languages are accepted !!!
    See Migration Logs!
    //Excerpt from the Mail Migration log:
    Begin Mail Migration: Thu Aug  2 19:34:24 2012
    purge: 0
    sourceRoot: /Library/Server/Previous
    sourceType: System
    sourceVersion: 10.7.4
    targetRoot: /
    language: sv
    Did not supply a valid language for the --language parameter, needs to be one of [en | fr | de | ja]
    As you can see, it can only upgrade in English, French, German and Japanese system language. With no inital warnings the system crashes and causes a true mess half the way through its installation when you start Server.app.
    Solution:
    Throw Server.app in the trash or move it outside the Application folder, to force the computer to realized "its not a server". It can take half a minute or so for the system to realize it is no longer a server. You will see a sign.
    Change the language setting to English in your system preferences and restart your computer. Move back Server.app from the trash (or where you put it) and start Server.app, thereby initiating a new Servers installation. I was happy to find that all mail accounts etc was found again. I thought for several hours they where lost.
    The various sites hosted by the server did however not appear in their correct new location (when I tryed this). I had to manually move them from the "Previous" folder in /Library/Server/Previous/Library/Server/Web/Data/Sites/   to    /Library/Server/Web/Data/Sites/
    I hope this helps anyone out there....
    Cheers!
    Stefan

    Please explain.... when are you stoped from upgrading?
    I haven't actually had problems with the actual OS upgrade it is when you launch Server.app the first time everything goes to f-n h....
    Server.app should reconfigure and move around a lot of files and it does, but not succeeding doing it correctly. Many services can't read their config files and have them in two places. I trying to figure out which ones are being used. Somethime both locations are used but only parts of the settings in the files !?!?
    I am soon giving up...

  • Configuring postfix on Mountain Lion Server

    I'm trying to upgrade from Snow Leopard Server to Mountain Lion Server and did an install of Mountain Lion Server on top of a working instance of Snow Leopard Server.  The "crippled" GUI on Mountain Lion Server is forcing me into using terminal to configure Postfix to handle incoming email.
    I would like to configure Postfix to only accept email that is forwarded from a gmail business account.  The public email address is [email protected] which is received by Google Mail, goes through their spam filters and then is auto-forwarded to  [email protected]
    The server WAN domain is nonpublic.com  The ip address is 96.231.165.126
    The server LAN is nonpublic.local  The ip address is 10.6.18.201
    The server is a MacMini running Mountain Lion Server 10.6.8 hostname server so the FQDN is server.public.com.
    The network on the MacMini is configured to handle both LAN and WAN traffic through the 1GB physical ethernet port which plugs into a CISCO 3750 switch.  The external traffic to the WAN flows through the switch as tagged packets.  The LAN traffic is not tagged.  The VLAN connection is running 802.1q
    When an email is sent through the WAN to [email protected] the Postfix SMTP log shows:
    Jun  7 19:29:22 server.public.com postfix/smtpd[42181]: connect from cisco.public.com[96.231.165.123]
    Jun  7 19:29:22 server.public.com postfix/smtpd[42181]: disconnect from cisco.public.com[96.231.165.123]
    I can send emails from a client on the LAN through this server with no problems.  The incoming mail server can connect to the machine via the Cisco router/switch but Postfix just shows "cisco" as the connection (that's the router's DNS name) and provides no more info.  I suspect Postfix possibly doesn't like the 802.1q connection and drops the SMTP request to connect on port 25.
    I have turned on "debug" logging in Postfix, but that is all that appears in the SMTP log file
    I've spent most of the week reading through everything I can find on how to install and configure postfix on Mountain Lion Server and work around the cripled GUI in the "server" application.  I'm barely OK using Terminal and not familiar at all with configuring Postfix directling editing the config file.
    What is the best approach to configure Postfix to allow SMTP connections from the outside to deliver incoming email that is forwarded from gmail.com?
    I did find an "aliases" file in /etc/postfix/aliases but I'm not sure how to add the aliases and if adding aliases with a text editor is going to cause the "server" app problems and if the changes will be lost when the machine is restarted.
    Any help would be appreciated.

    MrHoffman, thank you for your response to my challenge to get the new test server working.  This is a migration from Snow Leopard Server to Mountain Lion Server.
    Here is the "checkhostname" test results:
    blue:~ admin$ sudo changeip -checkhostname
    Password:
    Primary address     = 96.231.165.211
    Current HostName    = blue.pderby.com
    DNS HostName        = blue.pderby.com
    The names match. There is nothing to change.
    dirserv:success = "success"
    blue:~ admin$
    Here is the response from postconf -n
    blue:~ admin$ postconf -n
    biff = no
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    daemon_directory = /usr/libexec/postfix
    data_directory = /var/lib/postfix
    debug_peer_level = 2
    debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
    dovecot_destination_recipient_limit = 1
    html_directory = /usr/share/doc/postfix/html
    imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
    inet_interfaces = loopback-only
    inet_protocols = all
    mail_owner = _postfix
    mailbox_size_limit = 0
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    message_size_limit = 10485760
    mydomain_fallback = localhost
    newaliases_path = /usr/bin/newaliases
    queue_directory = /Library/Server/Mail/Data/spool
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpd_tls_ciphers = medium
    smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
    tls_random_source = dev:/dev/urandom
    unknown_local_recipient_reject_code = 550
    use_sacl_cache = yes
    blue:~ admin$
    I agree that I should change the LAN domain from .local to something like .internal or whatever.   I've been running with .local for 5 years  on snow leopard server and never had any problems so that was a low priority.
    I hope I'm just not seeing some obvious setting in main.cf

  • VPN to Mountain Lion Server issues

    Hi,
    I checked a lot of VPN threads here today, but I wasn't able to find a solution for my problem just now. I try to connect by VPN to my Mountain Lion Server, but I get an error message that the VPN server is not responding. I get this message from iPhone and Mac. The Mountain Lion Server is a new installation, no upgrade from an older server.
    Some informations on my setup:
    I installed the server with a hostname like myserver.mycompany.com and option 3 (internet access), as I want to use it for email at a later stage. All services are working fine (except VPN). DNS is active, but basically it only contains the adress myserver.mycompany.com and forwards everything else to our router.
    I changed the DNS settings of our domain ( hosted by an ISP - so not in the local DNS ! ). I created a subdomain vpn.mycompany.com which points to the static IP of our router.
    In the router I opened the UDP ports 500, 1701 and 4500, and for 1701 i made the same thing for TCP (I found this in a forum, but I think this is not necessary?), the ports are pointing to the ip of the os x server.
    In OS X Server I started VPN for L2TP using the vpn.mycompany.com hostname, and a shared secret.
    When I try to connect with I client from outside I try to connect using L2TP via vpn.mycompany.com using the shared secred and user-id and password. The user-id is created in OS X Mountain Lion server and is configured to use VPN service. When trying to connect I get the error message "L2TP-VPN server is not repsonding...".
    In the log file of the server I see some entries for each connect:
    Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: Connecting.
    Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IPSec Phase1 started (Initiated by peer).
    Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: receive success. (Responder, Main-Mode message 1).
    Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Responder, Main-Mode message 2).
    Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: receive success. (Responder, Main-Mode message 3).
    Oct 10 20:21:45 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Responder, Main-Mode message 4).
    Oct 10 20:21:48 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Phase1 Retransmit).
    Oct 10 20:22:06 --- last message repeated 2 times ---
    Oct 10 20:22:06 myserver.mycompany.com com.apple.SecurityServer[17]: Succeeded authorizing right 'system.privilege.admin' by client '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] for authorization created by '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] (2,0)
    Oct 10 20:22:06 myserver.mycompany.com com.apple.SecurityServer[17]: Succeeded authorizing right 'system.privilege.admin' by client '/Library/PrivilegedHelperTools/com.apple.serverd' [1716] for authorization created by '/Applications/Server.app/Contents/ServerRoot/usr/libexec/ServerEventAgent' [2967] (100000,0)
    Oct 10 20:22:06 myserver.mycompany.com racoon[13873]: IKE Packet: transmit success. (Phase1 Retransmit).
    No more entries in log file now. Anyone any ideas what's going wrong. Might there be a problem as I use another servername outside as inside (vpn... instead of myserver...)?
    Thanks!

    Solved, first of all we tested to establish the VPN connection locally by adding the ip address of the server to /etc/hosts for vpn.mycompany.com. The VPN connected without problems then, so it was clear that it is a firewall/router problem, and not a server problem.
    After that we studied some more documentations and found that we don't have to open port 50, but ip protocoll 50 (ESP) on the firewall. After that was done, the connection was working from the internet as well.

  • Server App can't connect to a Mountain Lion server

    Hi,
    I installed OS X Mountain Lion Server (2.2.1) on a 2012 Mac Mini running OS X 10.8.4. I am able to access all the options using the Server.app on the Mini. Then I installed the Server.app (2.2.1) on a 2010 MacBook Pro running 10.8.4. On trying to configure the Server options on the Mac Mini from the MacBook Pro by providing the correct Mac Mini admin credentials, the password is not validated correctly. This happens when both the systems are on the same network or on different networks.
    I am certain that the username / password provided is correct, since using the same credentials I can successfully remote into the Mac Mini using Apple Remote Desktop (3.6.1) when both the systems are on the same network or on different networks.
    My situation supersedes the resolution provided in http://support.apple.com/kb/TS3960?locale=en_US. Note that the command sudo launchctl list | grep -q com.apple.servermgrd && echo loaded || echo not loaded returns loaded on the Mac Mini.
    Please help!

    I am having exactly the same setup and exactly the same problem - nevertheless I would like to add some more information in order to hopefully find / get help from other readers in here.
    I am using DynDNS - not a dedicated domain. I do not utilize an AirPort Extreme for port forwarding and else. All the necessary port forwardings were triple checked!
    - First of all "Apple Remote Desktop" is able to connect to my server over the internet (screen sharing) and locally in my LAN. No troubles here.
    - My iOS devices can connect using various VNC clients without any troubles.
    - VNC connections started within Safari (MacBook Pro) do work very well, too.
    - All kinds of WebDAV connections are working like a charme.
    - When connecting with "Server.app" from my MacBook Pro it asks if I would like to trust the self-signed certificate before I can enter name and password. After trusting that certificate it doesn't matter which account information I am entering: none is accepted. It does not make any difference if I am using a local user account or a user network account (both configured as being allowed to administer that server). "Server.app" does not accept any information provided.
    I've been following the KB advice, too that c xavier mentioned. "servermgrd" is loaded!
    For some odd yet unknown reason neither WAN nor LAN FTP login does work, too. It just gives me a time out, as already mentioned WebDAV is working fine.
    Sorry I could not help You, c xavier! I just thought that some additional information could help...

  • Mountain Lion Server bond support?

    After migration to new Mountain Lion Server from Snow Leopard Server, the Server App don't recognize the Ethernet aggregation of my Mac Pro! The services that was active in Snow Leopard Server are active, but if I try to stop the service of net install I don't try to restar the services because there isn't no interface!!!!! it's Possible? And probably it's the same for the other services!!!

    Yea, I actually run our current SUS on an older Mac Pro. It provides both Apple software updates and Adobe software updates (for our Adobe deployments) and is dedicated to these two services. My primary server (running Mountain Lion—capable of Mavericks, but again, because of the File Sharing issues in Mavericks Server, we're sticking with ML Server for the time being) is a loaded 2009 Xserve—which I don't run "secondary services" (my term <G>), like SUS, on.
    Unfortunately, the current SUS box won't do Mavericks Server (though, I have tested running a VM of Mavericks Server, just for SUS and Caching, inside the physical OS, and it worked fine, but seemed like a waste of system resources and just really didn't make much sense—and a bare metal install doesn't work because of RAID, etc.), so I was considering the Caching Service in ML as an alternative (if it did, in fact, feed Mavericks clients). I realize I could just "turn it on" and see what happens, but would rather look into first (as I assumed others would have ML Caching Service on, and probably had Mavericks clients on the network, so would have the info I was looking for).
    Anyway, at this point, unless ML Server Caching Service will do the trick, Reposado it is.
    k.

  • Start Mountain Lion server on boot

    Is it possible to start OSX Mountain Lion Server when I boot up my Mac Mini?
    I have to login now each time I boot to start the server service.
    Any help would be appreciated.
    Mike

    Once you have installed Server.app and configured and started the services you want to use they will automatically start when your Mac is booted. It is not necessary to login for the services to run, nor is it necessary to have the Server.app running. The Server.app is used purely for configuring settings and is not the server software itself.
    Some administrators would argue having a server logged in and showing the Finder etc. is an additional security risk even if you have a good password and the screensaver locked.
    It is purely up to you, however if you really want to have the Mac server automatically login and automatically run Server.app then you can do this in System Preferences -> Users & Groups -> Login Options, and then turn on Automatic login for the Administrator account. Then for the Administrator account set Server.app to be run in the Login Items tab.
    Note: You also need to check to see if Automatic Login has been disabled in the Security & Privacy preference pane and if needed re-enable it.

  • Update to Mountain Lion Server kills Time Machine Backups

    Okay, here's the scenario:
    Client: 
    MacBook Pro running Mountain Lion
    Server: 
    Mac Mini running Mountain Lion Server using an SSD boot and Promise Pegasus Thunderbolt RAID
    Prior to updating the Mac Mini to Mountain Lion Server (previously just using regular Mountain Lion) I was happily backing up using Time Machine over AFP.  Since the update to Server I get the Time Machine message:
    "The network backup disk does not support the required AFP features."
    The network drive is also no longer available for selection within Time Machine (once it's been deselected).
    Any easy ideas on a fix?

    Time Machine won't back up to Mountain...: Apple Support Communities

  • Will Mountain Lion Server be slower that Lion Server on my 2009 Mac Mini?

    I have a 2009 Mac Mini running Lion Server. Specs are: 2.0 GHz 8 GB ram.
    As always, I'm wanting to reap the benefits of the latest OS without upgrading my hardware. I know mirroring won't be supported, but who cares about that on a server.
    Does anybody have Mountain Lion on a similar setup?

    We've found Mountain Lion Server to run just as fast as Lion.  MLS boots a bit slower on our Mac minis, but it's
    neglegable.
    Also have had trouble migrating from Lion and 10.6.8 server to Mountain Lion Server.  Issues with Open Directory and Mail.
    Hope Apple puts out a .1 release to address the issues soon.

  • Mountain Lion Server with Network User

    I have a Mountain Lion Server with a network user. The whole system has been redone from Lion Server and on top of that I moved location, ISP, hardware and a few other things. The way I used the setup on Lion was to bind my MBP to the server and login from the MBP login window with the network account. If for whatever reason I wanted to look at the network account on the server, I could fast user swtich and everything that was open ie Safari, Mail, etc would be the same as it was on the MBP.
    Now if I'm logged into the network user on the MBP and then go to the server, it logs in as if I've just booted. They share the home folder and any new files/folders created on one shows on the other. But if Mail is open on the MBP it won't be open on the server.
    Does anyone have any ideas or suggestions?

    Thanks for your reply.
    I believe I got it to work, but,... How do you get the network account users to show up on the login window of the client computer? The login window shows the name of the client computer and the local accounts on the client computer. When I select Other in the login list I can login using a network account user id and it logs in. The network account user names do not show up on the login window

Maybe you are looking for