I have a Windows 10 desktop which functions as the Samba server. When my Early 2008 MacBook, running Lion, attempts to connect, the connection always fails because it does not detect the server despite the server appearing in the side bar in Finder.
As noted here ( -mac-computer-fails-to-connect-to-a-server-via-smb), OS X versions newer than 10.6.8 use a proprietary SMB client which makes identifying the resembled SMB protocol more difficult. Apparently, the SMB client in Lion (10.7.5) is designed to resemble SMBv1.
I have a 2008 Mac Pro (MacPro3.1 -- dual 3 GHz quad-core Xeon, 6GB memory) running Lion (10.7.3) that I'm using for as a server for a business (files, print, media, etc.) as well as a development server for a pretty standard PHP stack. From time to time, but most of the time, other machines take a VERY long time to reach the machine over the network -- ten seconds to display a trivial html page, for instance. The problem seems to be one of reaching the machine -- if I watch the apache server logs after making a request, I'll initially see nothing happen, and then a burst of activity once (I'm guessing here) the request reaches the server and gets handled. But there are other times when performance is fine.
Hardware failure: either a switch or network interface is failing. Since you have another machine working (presumably) on the same switch, perhaps your ethernet port or ethernet cable have problems. Try a different cable. Try setting up another interface (perhaps via WiFi, or better yet via USB ethernet dongle) just so you can ping it and see if it ever goes down.
Configuration jitter: something may be causing your network settings to change unexpectedly, similar to if you changed the Network Location. Check your system.log and console.log. See what is happening around the times of these outages.
I'm betting that you're using the machine name and depending on Bonjour/mDNS for name resolution, which is almost always machines' last resort (hence the waiting for every other possible means of resolution to give up).
The fact that you're seeing redirects from the router suggests to me that you have some sort of routing issue. Was that happening when you ping from another computer on the same subnet? If so, the router shouldn't be involved at all (and the redirect is basically its way of saying, "why did you send this to me?"). The situation I'd expect to cause this sort of thing is when the computers (and/or router) don't all agree on what the subnet mask is. Does everything agree on what the network's address range is?
Questions seeking product, service, or learning material recommendations are off-topic because they tend to become obsolete quickly. Instead, describe your situation and the specific problem you're trying to solve. Here are a few suggestions on how to properly ask this type of question.
My IT department restricts my access to the Screen Sharing part of Lion's preferences so I needed an alternative. I was able to get RealVNC running as a server with a free license (phone and email required). This was using 5.0.1 and Lion 10.7.4. Very easy.
Lion's built in VNC server works just fine, they just changed the authentication process and many clients are no-longer capable of logging on, especially ones that haven't been updated since Lion came out or where Mac compatibility is a low priority.
Apparently that doesnt uninstalls completely Lion Server, I Uninstalled it that way by mistake, and when I tried to reinstall Server in the Mac App Store it says I'm Running OS X Server and I need to buy a bundle of Lion and Lion Server, Any idea on how to solve this to reintall Server?
I also went through this process and hit ok on the assumption I would not be charged again as I already have licenses for both of these. When it comes down it still has the same setup which is what I am trying to remove as seems I made a mistake in changing the network name and the profile manager became unresponsive. i.e. dead webserver. Maybe I just have to start again completely?
The instructions given by Apple aren't complete : all the UNIX stuff remains on the machine and I suppose one has to manually unload/disable all the services (with launchctl) then remove the launchd configuration files (in /System/Library/LaunchDaemons).
As you've discovered, simply deleting Server.app doenlsnt undo the Lion to Lion Server conversion process. The first time Server.app ran, it used Software Update to download additional server essentials from Apple in order to perform what was designed to be a one-way conversion. (For those familiar with how Mac OS X Server installers were put together, the basic "client" version of Lion already includes the server essentials like servermgrd.)
As Apple suggests, you can turn off the performance dedications for server processes. However, you still need to stop each service individually using Server.app, Server Admin, the serveradmin command, or by stopping each process required by each service with webappctl, apachectl, or launchctl, etc.
However, even turning off services does not completely revert Lion Server to the vanilla Lion state. Deleting the server version property list file only makes Mac OS X say "Mac OS X" instead of "Mac OS X Server."
Please excuse my slight derail...I know this is off-topic, and isn't the place, but It's the latest post I saw Gerrit in and wanted him to see this. I just wanted to say thank you for your the CUPS printer solution in that thread from 8 months ago (it's been archived so I can't add to the post and I don't see an email address for you in your profile).
This was a VERY frustrating issue and I tried several days worth of solutions from other places / people, and while replacing CUPS didn't seem like a good idea, it worked like a charm and for the first time in months, I'm able to print booklets for people here at work without it being a complete nightmare. I can't thank you enough!
This guide shows all steps for installing Moodle on Mountain Lion running OS X Server. This server is a commercial product. OS X Server can be used as an inhouse server as well as an internet server. You will find all documentations about the web server on the Apple support pages.
This guide DOES NOT show you how to setup Moodle on MAMP or XAMPP. If you do not have a web server currently running on your computer, please see Complete Install Packages for Mac OS X that can be downloaded from
These instructions have been written based on my experience setting up Moodle in a highly customized server. I will test all instructions in a clean environment once I have more time availability. Anyone who would like to test these instructions and report back any errors, please leave a comment with the section and error. Please do not test these instructions on a production machine.
*All production servers should be secured and have a trusted SSL certificate. If you are storing real student data and you do not use SSL, your users will be passing their username and password in clear text.
I am looking to create a Secondary Server, so if the Main Server goes down the Secondary Server may be able to maintain the clients working with no interruption or just a small gap (10 - 15 minutes for example).
I would like to know if you have any suggestion regarding backup tools and also ask how to create the backup Server on a way that if the main server goes down the backup server will supply our clients without them noticing that the main server went down.
For backup, does the client need something they can hold in their hand ? Any HIPAA or other privacy requirements ? Rotated external drives might do the trick but keep in mind that Time Machine volumes are not encrypted by default, and if they are that will increase the time for backups - the data & extent of change(s) to that data will have direct bearing on this. Testing with your data is called for.
ServerBackup Usage:
ServerBackup supports the following options:
-cmd backup -source SOURCE_VOLUME : Will start the backup process for the supplied
SOURCE_VOLUME. This should always be / for Server.
e.g.; ServerBackup -cmd backup -source
Note: the SOURCE_VOLUME for backup must be at version $MINVER or later.
-cmd browse -path PATH -service SERVICE: Will obtain browse listing of service SERVICE.
SERVICE can be specified as [all] to get all service browsable items.
e.g.; ServerBackup -cmd browse -path /Volumes/xxx/Backups.backupdb/xxx.sparseimage -service sharePoints
-cmd list : Displays a list of the backup snapshots in the backup repository for this system.
-cmd listVerbose : Displays a list of the backup snapshots in the backup repository for this system, uses options -Alh.
-cmd purgeSnapShot -path SNAPSHOT_PATH : This will remove the snapshot at path SNAPSHOT_PATH
NOTE: Use with care!!!
-cmd prefs : Validate or create settings for ServerAdmin backup.
-cmd postBackupComplete : Remove the /.ServerBackups backup folder from the root drive.
-cmd destination : Show current destination for backup. Can be a local volume or a network volume.
-cmd restore -path PATH -target DESTINATION_VOLUME : Will start the restore process with
the supplied PATH for the indicated
DESTINATION_VOLUME. Note: the DESTINATION_VOLUME is always /
e.g.; ServerBackup -cmd restore -path / -target /
Since data could be overwritten
this should be used with care. Also, any special
service handling should be considered!!!
Use with care!!!
Note: the DESTINATION_VOLUME for restore must be version $MINVER or later.
-cmd services : Lists the names of services.
-cmd size : Calculates the size requirements for doing a backup.
The line returned represents the number of Kilobytes required for storage.
e.g. total := 1872
-cmd version : Returns version information for this binary.
e.g. Server Backup (ServerBackup), Apple Inc., Version 10.8
-cmd verify -path PATH -service SERVICE : Will verify the live data against the snapshot
for the service SERVICE.
e.g.; ServerBackup -cmd verify -path /Volumes/xxx/Backups.backupdb/HOSTNAME/SNAPSHOT -service sharePoints