Apogee duet - no sound - mac mini server OSX 10.9

Hi
all posts relating to my query are very old so I pray someone can help with an updated solution.
I purachsed an Apogee DUET FIREWIRE to work with ABLETON LIVE 9 on my MAC MINI 2011 i7 16gb runing OSX 10.9.5 (ok - so i can see alreday that I am not on YOSEMITE - but the APOGEE driver application states its for 10.9 and 10.10). It second hand
Dowloaded the nec software from Apogee site, plugged in, Duet recognisedstraight away....then NOTHING !
No output. changed system settings accordingly. NOTHING. when I click on the drop down in ABLETON it HANGS for ages. Then after its selected, the track doesnt play....
So It tried ITUNES. Same. after clicking play NOTHING happens - track status bar does not move. When I re-select the mac output (through my stereo / headphone socket) I can hear itunes / Ableton perfectly.
I am sensing this is a driver issue.? I wont lie to you - Im a NEWBIE to MACs. Converted this Xmas - but I seem to have picked up a well stocked MINI MAC - but is a there a school boy error here I am missing?
BTW - just to be safe Ive ordered a new 400-88 firewire cable just in case...as apogee came with a 800, 9 pin to 9pin cable, so I am using an adaptor (which again may be the probem - even though its high quality),...new cable will arrive tomorrow.
MANY THANKS - NICE TO FINALLY GET A MAC !!
Jof

I think you're trying too hard...
I have zero tech or network expertise, but my Mac mini server intalled without a hitch on my home network of three other Mac desktops (Ethernet from AEBS), a MacBook, and a PC laptop, both via the AEBS wireless. The AEBS is connected to a cable modem.
I also have a static IP for my AEBS.
If you hook up your server, computers, and AEBS first and then reinstall Mac OSX Server, the server set-up will configure your network for you. You shouldn't have to set your own IPs at all...
I'm no genius at this stuff and I'm mostly playing around and experimenting, but we use file sharing, a common calendar, a family Wiki, centralized backup, and also run iTunes continuously to serve an Apple TV.
Let Apple do the work for you. See if the defaults work before tweaking it. It worked out of the box for me... Good luck.
Charlie

Similar Messages

Mac Mini server OSX 10.6.5 & Airport config: cable/modem--AEBS--Mac mini

I'm new to OSX server, and have recently had to change locations of a OSX 10.6.5 Mac Mini. I am setting it up now as a home server and need to access from outside the home. I have had a wonderfully operating AEBS for many years, but once I started trying to set-up the mac mini server, I started having problems configuring the server to play nicely with the AEBS.
Back to basics, because for what I need the AEBS is sufficient (and technically capable) of acting in concert with my mini server (from all I've read, anyway). I just cannot configure them correctly without causing problems.
Equipment:
AEBS w/ version 7.4.1
Mac Mini OSX 10.6.5
iMac OSX 10.6.5
(2) MacBook Pros 10.6.5
(2) iPhones IOS 4.2
I have a static (known) IP from my ISP. I have no problem with configuring the AEBS to work with everything, until I plug in the mac mini. I realize the older configuration for the prior server set-up is incorrect, but making minor adjustments for moving to a AEBS from the Cisco UC500 set-up has been greater than my technological experience.
I am versed in networking, but cannot seem to get the correct configuration, and the only thing the Apple manuals have is a 'possibility' this can be done, but no specifics I can find for controlling the AEBS settings from the mac mini when connected on the LAN port of the AEBS (that's when the problems start).
Here's where I've tried and cannot access the Serv Admin program when I connect the mac mini to the AEBS LAN port:
(1) changed AEBS Connection sharing to Share a public ip address
(which I understand makes "advanced" "port mapping" possible)
(2) set AEBS Internet connection to connect to router on 192.168 network
(3) set AEBS to offer DHCP in 10.0.1 range
(4) set AEBS capsule own address to be 10.0.1.1
PLUG in ethernet cable to Mac Mini and Time Capsule
Activate Ethernet and deactivate Airport
(5) set Mac Mini Server Manual ip address to 10.0.1.2
(6) set Mac Mini Server DNS addresses to 127.0.0.1, 10.0.1.1
(7) set Mac Mini Server / Server Admin / DNS / Zones / Machine name / IP Address = 10.0.1.2
Any advice on where to start trouble-shooting?

I think you're trying too hard...
I have zero tech or network expertise, but my Mac mini server intalled without a hitch on my home network of three other Mac desktops (Ethernet from AEBS), a MacBook, and a PC laptop, both via the AEBS wireless. The AEBS is connected to a cable modem.
I also have a static IP for my AEBS.
If you hook up your server, computers, and AEBS first and then reinstall Mac OSX Server, the server set-up will configure your network for you. You shouldn't have to set your own IPs at all...
I'm no genius at this stuff and I'm mostly playing around and experimenting, but we use file sharing, a common calendar, a family Wiki, centralized backup, and also run iTunes continuously to serve an Apple TV.
Let Apple do the work for you. See if the defaults work before tweaking it. It worked out of the box for me... Good luck.
Charlie

Mac mini server osx server to normal 10.8.4?

I want to buy a second hand mac mini i7 2.ghz mid 2011 model which im almost sure is a server. If it comes with the server version of osx 10.8.4 is it possible to get the operating system to run like a normal mini?

Yes it is.
If it comes with OS X Server installed, you have two choices.
Reboot into the Recovery HD and reinstall Mountain Lion. Then do not install the OS X Server app.
With the OS as is, turn off all the servcies within OS X Server app, move the OS X Server.app to Trash and delete the /Library/Server folder.

Mac mini server start and restart times

I have a new Mac Mini Server that i jsut purchased 2 weeks ago. It arrived a few days ago and i have already put ram in it and configured it as a raid 1. It seems slower now than before the ram and raid.
Current configuration
late 2012 Mac mini server
osx 10.9.3
2.6ghz i7
16gb 1600mzh ddr3 corsair vengence ram
(2) 1Tb factory apple hard drives configured as raid1(mirrored)
Start time
(4gb) 0:52m
(16GB) 0:52m
Restart time
(4GB) 1:52m
(16gb) 2:14m
Shutdown time
(4gb) 0:24m
(16gb) 1:04m
Any clue as to why my restart and shutdown times are so slow with more ram? i thought ram did not affect this. Secondly does a raid1(mirrored) affect this? it also seems a bit slower to open apps and while on the web
my late 2011 mbp smokes this thing, but it is running an ssd so its understandably going to. what I dont understand is on internet browsing the MBP is still faster. thought webspeed had nothign to do with the hard drive. im a bit new to all this.
Any help would be appreciated

I have a new Mac Mini Server that i jsut purchased 2 weeks ago. It arrived a few days ago and i have already put ram in it and configured it as a raid 1. It seems slower now than before the ram and raid.
Current configuration
late 2012 Mac mini server
osx 10.9.3
2.6ghz i7
16gb 1600mzh ddr3 corsair vengence ram
(2) 1Tb factory apple hard drives configured as raid1(mirrored)
Start time
(4gb) 0:52m
(16GB) 0:52m
Restart time
(4GB) 1:52m
(16gb) 2:14m
Shutdown time
(4gb) 0:24m
(16gb) 1:04m
Any clue as to why my restart and shutdown times are so slow with more ram? i thought ram did not affect this. Secondly does a raid1(mirrored) affect this? it also seems a bit slower to open apps and while on the web
my late 2011 mbp smokes this thing, but it is running an ssd so its understandably going to. what I dont understand is on internet browsing the MBP is still faster. thought webspeed had nothign to do with the hard drive. im a bit new to all this.
Any help would be appreciated

How to install OSX 10.6 client in Mac Mini Server 10.7 Lion Server

I am ordering a Mac Mini Server with Lion Server 10.7, with 256GB SSD and 750GB HD. I want to use Snow Leopard (client/workstation) instead. Previously I have already purchased retailed version of 10.5 clients and 10.6 client upgrade. Please advise the best approach from the followings (or more suggestions from you guys...).
(A) The boot disk (likely to be the SSD) will be re-formatted and re-installed by "clean" installation of 10.6 client. But I am not sure whether all hardware drivers for the new Mac Mini (2011) are available in the 10.6 client disk. Also, it seems to me that installation disk of 10.7 server will not be provided. So I shall not be able to re-install server version again if I want to change this Mac to a server sometimes afterwards. Of course I would like to keep this server software for investment protection, no matter I use it or not. If 10.6 client can be installed, I shall use bootcamp to install Windows 7 also. So there will be 2 partitions to be usable aparently.
(B) The factory-installed OSX 10.7 server is kept, and one more partition is created (with Disk Utilties). Snow Leopard workstation 10.6 will be installed at this new partition. If 10.6 client can be installed, I shall use bootcamp to install Windows 7 also. So there will be 4 partitions, including 10.7 server, 10.6 client, 10.7 recovery drive and bootcamp for Windows 7. Since I want to put all OS software at the SSD (faster boot-up and better performance), the drawback is that each partition is with less space.
Do you guys have other ideas or suggestions?
[Background]
In fact I want to make use of its strongest computing power (amongst available Mac Mini computers in store), quad-core CPU & dual disks, to run music applications (DAWs). Operating systems are put at SSD, and data is put at traditional harddisk. As some music applications (e.g. Calkwalk Dimension) only support 10.6 currently, I need to down-grade from Lion server to Snow Leopard workstation. Also I think applications can run faster in a hardware with workstation OS (rather than server version). Please correct me if this belief is wrong.
Thanks / Howard.

If you completely wipe the original Mac mini boot drive you will wipe the Server.app software an dlose it. You should make a backup first, perhaps by saving the entire boot drive as a Disk Image file on to another drive.
In terms of install 10.6, the 10.6 DVD will not boot on the new Mac mini even if you connect a DVD drive. You need to put the Mac mini in to FireWire Target Disk Mode and connect it to an older Mac that will allow booting from that DVD, then install on to the Mac mini (over FireWire), you then need to upgrade it using the 10.6.8 Combo Updater this will add the drivers needed for the new Mac mini.

Mac Mini OSX 10.6.5 config w/ cable/modem-AEBS-mac mini server

I'm new to OSX server, and have recently had to change locations of a OSX 10.6.5 Mac Mini. I am setting it up now as a home server and need to access from outside the home. I have had a wonderfully operating AEBS for many years, but once I started trying to set-up the mac mini server, I started having problems configuring the server to play nicely with the AEBS.
Back to basics, because for what I need the AEBS is sufficient (and technically capable) of acting in concert with my mini server (from all I've read, anyway). I just cannot configure them correctly without causing problems.
Equipment:
AEBS w/ version 7.4.1
Mac Mini OSX 10.6.5
iMac OSX 10.6.5
(2) MacBook Pros 10.6.5
(2) iPhones IOS 4.2
I have a static (known) IP from my ISP. I have no problem with configuring the AEBS to work with everything, until I plug in the mac mini. I realize the older configuration for the prior server set-up is incorrect, but making minor adjustments for moving to a AEBS from the Cisco UC500 set-up has been greater than my technological experience.
I am versed in networking, but cannot seem to get the correct configuration, and the only thing the Apple manuals have is a 'possibility' this can be done, but no specifics I can find for controlling the AEBS settings from the mac mini when connected on the LAN port of the AEBS (that's when the problems start).
Here's where I've tried and cannot access the Serv Admin program when I connect the mac mini to the AEBS LAN port:
(1) changed AEBS Connection sharing to Share a public ip address
(which I understand makes "advanced" "port mapping" possible)
(2) set AEBS Internet connection to connect to router on 192.168 network
(3) set AEBS to offer DHCP in 10.0.1 range
(4) set AEBS capsule own address to be 10.0.1.1
PLUG in ethernet cable to Mac Mini and Time Capsule
Activate Ethernet and deactivate Airport
(5) set Mac Mini Server Manual ip address to 10.0.1.2
(6) set Mac Mini Server DNS addresses to 127.0.0.1, 10.0.1.1
(7) set Mac Mini Server / Server Admin / DNS / Zones / Machine name / IP Address = 10.0.1.2
Any advice on where to start trouble-shooting?

The AEBS gets your public static IP address, and otherwise performs NAT.
(The AEBS is a good home box, but not a server-grade firewall. I do run AEBS and Time Capsule boxes, but these are generally operated as WiFi Access Points (what Apple calls "bridging"), and not as WiFi routers, and definitely not as server gateways.)
The AEBS DHCP server configuration for DNS services is set with the IP address of your new server; that's your DNS server now. Caution: +There are no references to ISP DNS nor other DNS servers.+ You're running DNS (well, you will be soon), so your local network will be configured differently than a client network.
Your Mac Mini Server is configured in a /24 subnet in one of the private blocks (eg: 10.0.0.0/8) somewhere. This for future VPNs, as everything on the planet is crammed in a few 192.168.0.0/16 subnets.
The AEBS DHCP server can be used to pass out a pool of addresses in that private /24, but the server must have a static IP address.
[Get your DNS services going for your LAN now.|http://labs.hoffmanlabs.com/node/1436] Don't skip this step. DNS is essential to servers, and you'll be serving DNS on your LAN. I'd suggest a real and registered domain here or a subdomain of a real and registered domain, as changing domain names on a network is an increasing pain in the rump as the network scales up.
For DNS services, your Mac Mini (and only your Mac Mini) will refer only to itself via the 127.0.01 on its network controller. (This is an odd case; the box is referring to itself, so it's the IP loopback address and not your LAN static IP address.) Everything else on your LAN will refer to the static IP address of your Mac Mini DNS server either via static configuration, or via the AEBS DHCP server's DNS setting referencing your Mac Mini server that are received from the DHCP server with a dynamic address.
Work your way up to configuring Open Directory (LDAP), and Kerberos, then configure the rest of the accouterments.

Using Mac Mini running OSX Server (10.8) to host web sites on LAN

I would like to know how to use a Mac Mini running OSX Server (10.8 ML) to host web sites on my home network (LAN).
I am developing web sites and previously (before ML) I used my Mac Pro to 'host' the sites I was developing to test them out before publishing them to my hosting package. That was when I was using 10.7 Lion and theer was an option in the System Preferences to turn web sharing on.
I have since upgraded my Mac client to 10.8 ML and have configured it to do the same - even though there is no System Preferences option for web sharing any more.
I also have a Mac Mini running on my LAN and its been upgraded to OSX Server 10.8.
Im now trying to configure it to host the web sites I am developing but with no success.
I thought it was just a matter of adding them as sites in the Server's Websites panel (see screen shot)
but so far Ive had no success.
On my Mac client I can simply add a folder in the Sites directory and then open the web site by putting http://myhost/~myuser/name-of-folder and it will load the default file in the folder e.g. index.html
How do I achieve the 'same thing' on OSX Server?

Hi Johnfromglenver,
There are no Mac drivers for the HP Officejet K60 printer. Therefore it is not compatible with the Mac operating systems. Please call our technical support at 800-474-6836. If you live outside the US/Canada Region please click the link below to get the support number for your region. http://www.hp.com/cgi-bin/hpsupport/index.pl. There may be other solutions that could work for you.
I hope this information helps.
Advance 23
I work on behalf of HP

Who runs a regular osx lion on mac mini server ?

Wo runs a regular OSX lion (not the server edition ) on a mac mini server without any problems ?
I have a late 2011 mac mini server with a regular OSX lion 10.7.3 latest updates, wich keeps freezing unattended at certain times.
Wish to hear if this setup causes problems for anyone or that it might be a local issue with my SSD disk causing freezes

I am having the same problems with the same setup. Did you ever get this sorted?

I'm unable to connect to my mac mini server remotely since the upgrade to OSX 10.8.5. I was able to connect without problem (from an Ipad and a Mac Pro workstation)before the upgrade which I applied last week.

I installed an update to OSX 10.8.5 last week. I've been unable to use Remote Desktop VNC from my Mac Pro working station or use Mocha Vnc Lite from my Ipad to gain access to my mac mini server since I applied the update. Any help would be appreciated!

Hi David,
thank you. I tried all the steps and the thing different is that now with my usual user the CC app crashes silently, but Photoshop and Illustrator generate a crash report with this message:
/Applications/Adobe Photoshop CC/Adobe Photoshop CC.app/Contents/MacOS/../Frameworks/amtlib.framework/Versions/A/amtlib
abort() called
terminate called throwing an exception
With the Adobe user it runs with no problems, I even tried to do a "diff" of running user processes between the two users and remove all launchers and extensions but it's still the same.
I am a developer so I use XCode and other "dotfiles" and dirs within my home directory, I'm also using Ruby/RVM, NodeJS and some other. Can some of this stuff cause conflicts?
Thank you
Vito

Removing OSX Lion Server from Mac Mini Server (Mid 2011)

Hello, fellow apple fanboys!
I was wondering if anybody knew the sollution to my problem. I have recently purchased the Mac Mini Server, the mid 2011 model, and I wanted to replace the server edition of Lion with the standard one. However, when I plug in my lion installation thumbdrive the system just displays a stop sign, meaning that I cannot boot from it. I was wondering if I could just wipe the Server HD and reinstall standard Lion OS on it.

I have the 2011 Mini Server and all I did was just not enable
any server functions. It works just fine. Unlike previous
versions of OSX, the server is an add on to the OS and
not intertwined with the OS. So, my suggestion is don't
bother. Just isn't worth the time.
As to why the thumbdrive doesn't work, it is probably a version
that is older than what the Mini was shipped with. This is not
anything new as this is the way OSX has always been.

Setup VPN on Mac Mini Server running OSX through a BT Hub Router

Hello everyone,
I know this question has been posted several times and I have looked at the suggested solutions, trying each of them. I think this is really down to my lack of knowledge hence hoping someone out there could point me to the right direction for more resources / information, please.
I am trying to setup a Mac Mini Server with VPN access. My server sits behind a BT Hub router. These are the steps that I have been through:
1. I am using the server app and after registering a free account with no-ip, I got myself a host name <myname>.ddns.net.
2. Then I setup the server using a domain name
3. I configured the DNS by first setting up a primary zone - zone: ddns.net. Then added machine record host name: <myname> pointing to my server which I have configured my router to assign a static ip address to it at 192.168.x.x
4. Then, I configured the VPN setting up for L2TP and PPTP, setup the shared secret, change the ip address range to match that of the DHCP range on my router. My router by default has a DHCP range between 64 - 253.
5. Then, I also configured my router to port forward 500, 1701, 1723, and 4500 to my server at 192.168.x.x (I selected both TCP and UDP).
6. Finally, setup a user account with account name test and password abcd12345
7. Gone on my "client" machine which is basically my Samsung S4 handphone, selected VPN -> PPTP -> server address: <myname>.ddns.net -> entered account name test and password abcd12345.
This didn't work.
Then, I read some post about manually configure DHCP on the server app. Went on the server app, turned on DHCP and setup a network named TestDHCP. Assigned ip address range between that of the default DHCP range on my BT Hub router.
This does not work either.
Could someone please kindly help me with it? I am completely lost.
Thank you in advance.

To run a public VPN server behind an NAT gateway, you need to do the following:
1. Give the gateway either a static external address or a dynamic DNS name. The latter must be a DNS record on a public DNS registrar, not on the server itself. Also in the latter case, you must run a background process to keep the DNS record up to date when your IP address changes.
2. Give the VPN server a static address on the local network, and a hostname that is not in the top-level domain "local" (which is reserved for Bonjour.)
3. Forward external UDP ports 500, 1701, and 4500 (for L2TP) and TCP port 1723 (for PPTP) to the corresponding ports on the VPN server.
If your router is an Apple device, select the Network tab in AirPort Utility and click Network Options. In the sheet that opens, check the box marked
Allow incoming IPSec authentication
if it's not already checked, and save the change.
With a third-party router, there may be a similar setting.
4. Configure any firewall in use to pass this traffic.
5. Each client must have an address on a netblock that doesn't overlap the one assigned by the VPN endpoint. For example, if the endpoint assigns addresses in the 10.0.0.0/24 range, and the client has an address on a local network in the 10.0.1.0/24 range, that's OK, but if the local network is 10.0.1.0/16, there will be a conflict. To lessen the chance of such conflicts, it's best to assign addresses in a random sub-block of 10.0.0.0./0 with a 24-bit netmask.
6. "Back to My Mac" is incompatible with the VPN service. It must be disabled both on the server and on an AirPort router, if applicable.
If the server is directly connected to the Internet, see this blog post.

OSX 10.7 Lion (client) on Mac Mini Server?

So you think OS 10.7 Lion client is going to work on a new Mac Mini Server? With all the problems with 10.6.3 Client not working with a Mac Mini server I'm wondering if 10.7 will have all the correct drivers (the SD card drive, and ethernet, and issue with DVD player app.)
Anyway, what do you all think?

Apple has not announced system requirements yet, so anything anyone here can say will just be a guess. My guess is that I can't image that 10.7 won't support 2010 hardware, but again, that's just a guess. We'll have to wait until Apple releases official specifications, which probably won't happen until sometime next spring. Beyond that, there's nothing more we can say.
The workstation version of 10.6 works fine on the Server version of the Mac mini if you can get a copy of the disk that shipped with the non-server mini. Otherwise, you'll have to wait until Apple ships a newer version of the retail CD, one with 10.6.4 or later.
Regards.

Cannot Search Mac Mini Server

Setup a small office network for our art dept, but have lost the ability to search for files on the Mini server. I have seen a ton of threads about this, but no definite fixes or reason. Please help! It is very difficult to work with a server that you can't use a search function on!
Imac- OSX Lion 10.7.4
Imac- OSX 10.6.8
Mini Server- OSX Server Lion 10.7.5
Thank you
-Prodigal

This sounds like a simple port forwarding issue, but I don't understand your LAN setup.
The WRT300N has DDNS service set up. NAT and RIP are disabled.
The chances are, you're running NAT somewhere in your network. If not the WRT then what? If it's your cable modem then you must have port forwarding configured on the cable modem, and that's where you need to focus - change the port forwarding to point to your Mac Mini's address rather than the WRT.
HOWEVER, it is far more common to have the wireless router perform NAT and DHCP, which is why I question your setup.
Not directly related, but:
The Mac Mini DHCP is reserved
Nix this. Your server should be configured manually, with a static IP address, not DHCP, even with a reservation in the DHCP server. The only advantage of DHCP is for dynamic hosts (hence the 'D' in 'DHCP') or if you expect to change your entire local subnet on any kind of frequent basis. The reality is that you can't just change the IP address of Mac OS X Server like this - there are too many dependencies, so it's better to set it manually, knowing that there's a cost (and pain) to change the server's address.

How to set up my mac mini server to use two drives seamlessly?

I have a mid 2010 mac mini server, with OSX Lion installed. It has dual 500gb hard drives.
I've been moving all my important files to it, and I've always assumed that once I filled one disc, it would seamlessly transfer over to the other and continue backing up. This does not seem to be the case.
I'm at roughly 495gb of data, and when I try to move a 10gb file onto my server, it tells me that I don't have enough disc space to continue the operation.
What can I do to make use of both drives?
-Thanks

It sounds like what you're asking for is to have the two drives in a RAID 0, where the two 500 Gb drives look like a single 1 Tb drive. I'm not sure the exact procedure for installing RAID 0 on a mini's internal drives, but the process would involve backing up, reconfiguring for RAID (which destroys all data,) restoring data from the backup, and more risk than I would personally find acceptable. I'd expect to lose a full day with the backup and restore steps. I can guarantee, there will be pain.
Instead, I'd suggest looking at what's consuming the 500Gb, and seeing if there are particular folders that can be moved. For example, a shared folder is pretty easy. Copy it over. In file sharing setup, edit the share to point to the new location. Make sure remote users disconnect, and reconnect to the "new" share. When you're happy there is no data loss, delete the old location.
User's home directories can also move, but the process has a few more steps, and depends on how the accounts are built (local vs. OD)
If the majority of the data is in a single "your backup files" folder, shared or otherwise, then I would just set up a second folder on the second drive and write to it, leaving the first alone. If it is truly a backup, then you could make the first folder read-only at this point for extra protection. If you go the 2 folder route, keep in mind your boot drive is operating with 1% free space, I like my drives to have at least 15% free, and OS drives more like 25% (you'll find some range in recommended %-free, but most will agree 1% is too little) so move SOME stuff to the new folder, before closing the old.

Mac Mini Server Setup for Print Shop

Hello!
I run a digital printing company. We get lots of large files from customers all day long. So far, we have been using Dropbox as our file server. It's great in every way except for speed. Because we run about 7 computers in our shop, every time we add a client file to Dropbox it has to sync with the internet plus those 7 computers. When we get the exceptionally large file from a customer, our network is toast and it can sometimes take us hours to recover.
I tried the OSX Mini Server route months ago but because I found it difficult to get it to do what I wanted, I turned it into one of our production computers. However, I'm getting more desperate and I want to put more research in to figure out what I need to do. The primary problem we had with the Mac Mini Server was that we could not easily remotely access it. In fact I couldn't figure that out at all. That's one thing that's super nice about Dropbox is that if our designers go home and want to work on a file in the evening, they already have it on their computer with Dropbox.
Is there an easy way I can accomplish this with an in house server? I need the following:
Easy access to files in-house
Easy access to files remotely
Fast speed, no bogging down the network
Off-site regular backups (in case the computer gets stolen or our shop burns down)
We run 3 of Apple's latest Airport Extreme's, one in each main room. And all the computers connect via ethernet for optimal speed.

This may sound to simple, but have you considered SFTP instead of dropbox? Let people pull the file when they need it as obviously the large files syncing across multiple mac bringing your network to a halt is not working. You could monitor the incoming FTP with Hazel and push "small" files to Dropbox, but put the large files that cause the problem in a FTP folder for people to pickup when needed. That way you get the best of both worlds. Maybe combine that with selective sync on the dropbox client.
As for remote access to the Mac Mini, that is actually quite easy. In the sharing preference panel select screen sharing then Click on Computer Settings, Set a VNC password and check "anyone can request permission to control of the screen". Open up the ports on your router and set up the port forwarding and you should be able to connect with a VNC client.It works remotely either with the screen sha
Good luck.

Apogee duet - no sound - mac mini server OSX 10.9

Similar Messages

Maybe you are looking for