Mac Mini Server on my university network?

Hello,
I am a university professor and I would like to install a Mac Mini server in my laboratory to connect all my Macs (I have 4 so far). Obviously, my Macs are already connected to the Internet through the campus network (fixed IP), but since my university is an anti-Mac institution, I cannot have access to network drives and other networking goodies (we are on Novell). Anyway, that's why I want to buy a Mac Mini server to connect all my Mac and be able to share files, allowed different permissions to my undergraduate, grad, Ph.D. students, etc. plan and call meeting with iCal Server, communicate with my lab users with iChat, etc. However, I don't need email services; we use the one provided by the university.
So my question is simple : can I create my own little local network with a Mac Mini Server that will be connected to my university network/server? I am kind worried about IP conflicts and other network related problems and being called to the IT office...
Your comments will be welcome!
Thanks!

The real answer to this depends on two things:
1) whether you're just trying to do this within your lab, or you want external systems to be able to get to your services (e.g. students be able to access these resources from outside the school network)
2) whether each device in your schools' network have real-world IP addresses, or whether the network uses NAT.
If the answer to 1 is that this is only within the lab then there isn't likely to be any issue - get an IP address for your server from the network admins (which is why #2 is relevant) and you're set. The network guys would only have other involvement if you wanted to get external access working, in which case you've got to talk to them about opening holes in firewalls, etc.
If this is purely internal (or, at least, doesn't need access from outside the school network) then there isn't likely to be any problem. You could even get away without DNS, although it would be nice if you could get a sensible hostname from the DNS administrators (e.g. server.yourlab.yourschool.edu) but even without that there shouldn't be anything preventing you from running a service and having internal clients connect to it (other than policy issues, of course…). For the most part the admins wouldn't even know you're running a server.
Getting a static, non-conflicting IP address that valid for the school's network is going to be key, though.

Similar Messages

How do i make HD2 on my mac mini server useable by my networked macbook pro for time machine?

What do I need to do to make HD2 on my new Mac Mini server useable for Time Machine on my MacBook Pro? I can access the server, but HD2 is not visible, although I have set it up to let everyone have read/write permission.

FWIW, I personally would not use any disk drive that is internal
to a Mini for a backup of anything. The reason for that is if something
should happen to the Mini, your backup will be unavailable. And of
course, that is when you will need the backup, Murphy's Law. getting a
drive out of a Mini is no small task.
Personally, I keep any backups on external drives, as they can be
easily moved and replaced.
The only case where I would keep a backup internal to a computer
would be in the case of a Mac Pro where you can easily remove and
swap hard drives.
Just something to consider.

Mac Mini Server on Yosemite showing x2 Servers with one being redundant

Hi
I have a Mac Mini OS X Server that worked fine with setup/name of 'server' on Mavericks, however since upgrading to Yosemite the server has now become Server (2) (or server-2) leaving a redundant 'server' (server) in the shared tab.I can't access 'server' on the Mac Mini server or via the Network (even with connect as) and cannot rename \server-2' to server. I have re-installed the OS with no change.
Does anyone have any ideas what is going on here please and also how I could reset the 'serve-2r' to show correctly as 'server' and remove the erroneous one?
Thanks
Glennyboy

The real answer to this depends on two things:
1) whether you're just trying to do this within your lab, or you want external systems to be able to get to your services (e.g. students be able to access these resources from outside the school network)
2) whether each device in your schools' network have real-world IP addresses, or whether the network uses NAT.
If the answer to 1 is that this is only within the lab then there isn't likely to be any issue - get an IP address for your server from the network admins (which is why #2 is relevant) and you're set. The network guys would only have other involvement if you wanted to get external access working, in which case you've got to talk to them about opening holes in firewalls, etc.
If this is purely internal (or, at least, doesn't need access from outside the school network) then there isn't likely to be any problem. You could even get away without DNS, although it would be nice if you could get a sensible hostname from the DNS administrators (e.g. server.yourlab.yourschool.edu) but even without that there shouldn't be anything preventing you from running a service and having internal clients connect to it (other than policy issues, of course…). For the most part the admins wouldn't even know you're running a server.
Getting a static, non-conflicting IP address that valid for the school's network is going to be key, though.

How can I set-up my mac mini server to be a central file server for my windows boxes (they don't see the mac on the network), and how do I set-up a central iTunes server so that all my devices sync to the mac mini?

I am looking for step by step instructions to configure my mac mini server to support the following:
1. Central itunes server for all my devices (ipad, ipod, iphone, etc.)
2. Central file server so that my windows devices can save and retrieve data from the central system (the mac does not show up in the network for the windows systems - all running windows XP or 7)
Thanks,
Keith

You will need to enable file sharing in System Preferences
as well as setting up sharing and permissions for the
directories that you want shared. You may also want to
setup a non-administrative user or allow limited guest
access. The user would require entering a user name and
password to make the connection, but would allow remotes
to change files, if set up tat way.
As for serving iTunes media, better to post in the iTunes forum.

I have a mac mini server which I want to set up for remote access from windows and mac pcs. How do I do this. I can access it form my home network OK

I have a mac mini server which I want to set up for remote access from windows and mac pcs. How do I do this. I can access it form my home network OK

Posted in error.

Small fast network with Mac mini server and Promise Pegasus?

I have 7 Mac Pros and iMacs that need to be connected to the same storage. I'm doing non MPI-based numerical modeling so the transfer rates have to be fast but not infiniband fast. I'm considering a setup with a Promise Pegasus thunderbolt RAID connected to a Mac Mini running Lion server for Access controll/Roaming homer directories. The Mac Pros and iMacs would the be connected via 1Gb ethernet.
My question is where the bottlenecks in this setup would be. The server software/hardware? The network? What else am I forgetting

I assume you're looking at Mac mini because you've already run the numbers on Mac Pro and ruled it out. I wonder how many buyers are opting for Mac mini solely for those Promise Thunderbolt arrays.
I also assume that each of your users is currently using a single gigabit Ethernet port to connect to the LAN.
If these assumptions are accurate, then I think that a Mac mini will work as long as you and your users have appropriate expectations. The win from putting this server in place won't be networked storage that outperforms an internal SATA drive, although in bursts it probably can. The solution you've described is smart because it's centralized, securable and adds a layer of data protection (RAID).
You asked about bottlenecks. I can think of three, two of which you can work around now or in the near future. The first is Mac mini's slow internal hard drive(s). You'll have a solution in hand: Boot Mac mini from the array. Some consider that to be a controversial choice, but you shouldn't spend extra for the Mac mini server with dual 7200 RPM drives. The less costly Core i7 configure-to-order upgrade will give you a bigger boost.
Booting from the array also protects you from the most likely "repair" scenario for Mac mini: Swapping out your entire machine.
The second issue is Mac mini's lack of an expansion bus. If you get more users or start using apps that demand more from the LAN, you might want to fire up additional gigabit Ethernet ports. Mac mini has just one. At present, the only way to add a gigabit port is with a Thunderbolt PCIe bus expander. Early next year, there should be more options that connect directly or via an intermediate bus like ExpressCard/34 or USB 3.0.
The one limitation you're powerless to work around is RAM. Mac mini tops out at 8 GB. That meets requirements, but it will be tight if you try to use Mac mini as a client and a server. I deploy them headless so no one's tempted to use the console.
You can improve your odds that gigabit will cut it by using heavy, short Cat6 cables and a switch dedicated to the Mac LAN. Use Mac mini's built-in Wi-Fi to keep Remote Desktop and other low-priority traffic off the wire.
Whatever solution you choose, I wish you the best of luck.

Mac mini server networking and DNS setup help

Thanks in advance to anyone who can help me with this. I'm working at a small business where I'm the only guy with any IT experience at all, but I'm new to Macs and OS X (<1 year) and being a server admin so please bear with me.
We just bought a Mac mini server as we are expanding from a bunch of workstations and Google Docs. I've just gone through the installation process, but nothing else is on the server, no user data at all, so if the answer is to reinstall from scratch, I can do it.
We'd like the mini to be a file server, print server as well as the gateway for the internet. I realize we could stick to our router and have the server as another node in the network, but we also got a Time Capsule for backing up the server and will locate it in another room to be another wireless access point there.
When going through Server Assistant, I didn't really know what to name the machine so I used corp-Server.local for the Current Hostname and corpserver.private for the DNS Hostname (though i actually use a 3-letter company acronym instead of "corp").
However, i realized after setup we'd want to access the server externally by name, so I changed the DNS hostname to server.companyname.com in the Zones tab of the DNS section of Server Admin (edited primary zone name, changed Nameservers entry for both primary and reverse zone).
I don't know what else I need to do though because there are loads of instances where corpserver.private still shows up, like in the Open Directory section of Server Admin (which btw always hangs when I open it) and the Contact Info of users (eg. user email is [email protected]). I also had trouble earlier using Server Preferences and Server Admin either not connecting or not recognizing my login, but that seems to have abated.
I guess my problem is, where else do I change the DNS hostname? Or do I have to change the DNS hostname back to corpserver.private (in Server Admin)? That way, I think at least everything will be consistent, but would I be able to still configure it somehow so that externally, we could access the server by the server.companyname.com URL?
Also, can the mini be a wireless router for the office? As mentioned before, we want to cut the existing wireless router out and use the mini instead (and use the Time Capsule as a wireless bridge).

So the ISP<->router connection can have a dynamic IP address, but the router<->server one should be static? I guess that means I have to set the IP address in the router. I hope I can get access to it. I don't suppose it matters which one I set first?
An IP router does not assign addresses.
A DHCP server does assign IP addresses upon receipt of a DHCP request from a client.
Some routers (and many firewall routers) do include a DHCP server.
A box with a static IP address does not need to send a DHCP request; it has a static address.
You'll need to ensure that the IP address pool within the DHCP server does not overlap the addresses that are manually assigned to your local hosts; the static IP addresses on your LAN.
[Here is an overview of the pieces involved here, and some of the typical terminology|http://labs.hoffmanlabs.com/node/275].
I hate to belabour the point, but I just want to clarify: in my setup where ISP<->router<->server<->clients, where the server is the only machine connected to the router, which one should be the local DNS server? The server, right? So if the DNS server is turned on in the router, I should turn it off? Or do I need both (ie. router for its LAN (to server), and server for its LAN (to clients))?
So to confirm, the configuration includes (probably) a modem, a router (firewall) and a router (Mac), and then the rest of the (local) show? That is not the simplest configuration, and it's Particularly given that Mac boxes make expensive and slow routers.
The usual configuration is ISP>firewall>LAN and the LAN is usually built from WiFi, wired connections and switches. Within one subnet (which is typical) any host inside your firewall is connected on the LAN, and can communicate (directly) with any other LAN client. The firewall is configured as the gateway; that's the default route for outbound connections.
One more thing that's bugging me: I still don't understand why I couldn't connect to the internet when I plugged in the Ethernet cable from server to router. Even if I was using DHCP to get a dynamically allocated IP, shouldn't it still have worked? I'm worried that I'm going to set up everything as it should be but the connection still won't work.
That's likely because you're trying to use the Mac as a router, and that takes specific configuration steps. It's easier to have ISP>firewall>LAN, and have the Mac OS X Server box and the rest of the stuff as peers on your LAN. If you really want to use the Mac as an IP router, look around for setting up static routes on Mac; there are postings around for that.
If your data is more valuable and your security preferences and requirements are higher, then you may want a firewall with a DMZ, and put your web-facing boxes over in the DMZ. If you're serving stuff to the web or a mail server or such, it's possible to get breached, and a breach means folks can potentially get further into your LAN. With a DMZ, they're somewhat more isolated from your LAN.

Why does my mac mini server keep dropping off the network?

I have Verizon FiOS and use its router/wireless to connect all macbooks, macbook pros, etc. connect to each other and the snow leopard server, which runs the printers and time machine for one of the laptops. I'm not using any other heavy duty server apps. I just want the mac mini to stay on the network and do its job. Invariably when I go down stairs to the mac mini and ethernet to the router to share screen, I find some update that needs to be installed, which apparently is why the mac mini has gone on strike. I usually can see the problem when I go to connect to server and see the other macbooks, but not the mac mini. Then after much coaxing, I'm able to get the server back on line for a few days, until the next software update. The server is set to auto restart, but why is it balking at rejoining the network?
mac mini is running snow leopard, as are three of the four macbooks. router is an actiontec model. wireless network is WPA2 and mac mini is ethernet connected to the router.

I've just experienced this problem when using a Marantz SR4001 receiver between my Mac Mini and HD TV. I noticed that the problem didn't happen all the time and I have found a workaround solution.
The problem is not a fault, but seems to be caused by the receiver defaulting the HDMI video properties. It's an old unit so I'm thinking that 720p is a default resolution for the receiver.
I can make the problem happen if the receiver is turned on before the TV. Seems that without an output connection the receiver is telling the mac that it expects 720p.
If I turn on the TV before the receiver, the TV seems to tell the receiver that it is expecting 1080p 25fps and the receiver obliges and the Mac retains those display properties.
So it appears that the video output device dictates the output properties back to the receiver and the receiver in turn back to the Mac. In absence of an output device the receiver defaults to 720p.
Solution: Turn on the TV before the receiver.

New Mac Mini Server Network Issue

I recently purchased the new Mac Mini Server with 10.6 to use as a Content Filter/Web Server for a small private school. While trying to set it up, using the on board ethernet and a USB to Ethernet adapter, I have lost all ability to acquire an IP. IT does not matter if I use the on board ethernet, the USB adapter, or the Airport. All three return a self-assigned IP. I know this is related to the machine since I can still access the cable modem setup by typing in 192.168.100.1. And I brought it home to work on it a little more and the bonjour services are detecting the other macs on the network.
I tried trashing my network preference plist, but no change.
I am considering doing a fresh install since I think the initial setup was borked. But I thought I'd hit up the board and see if anyone else had a thought before I begin that process.
thoughts?

I have setup this configuration several times with both a MacPro and the smaller mini setup. The gateway setup we are describing is about as simple as it gets (static IP, gateway running all services so 1 IP address, gateway set as 192.168.1.1 on the local net. Simple DHCP and DNS "server.local", and "server.xxx.com" external).
I would be overjoyed to find that I can configure this by setting up some simple overrides in the routing. I would point out in defense that _everything else_ works perfectly basically by default.
1) dns on server: local and external, forward and reverse from itself and the local network - check
2) services on server (all of them): from itself and the local and external networks - check
3) network access (ie NAT & Firewall) for local machines - check (web, streaming, even bittorrent)
The only issue I see is that remote clients cannot access the gateway itself properly though VPN. UPD return packets seem to be mis-routed through the physical interface rather than the virtual one.
ALL other operations (Mail, iCal, iChat, Push, Web Services, Wiki, Web Mail and iCal, NAT) work perfectly for the server, local network, and external hosts. The above problem only happens for vpn clients, and then only for connections from them to the gateway itself, and only for UDP packets.
I would really love to know how to fix it, especially if this can be explained by a needed custom rule (But I'm guessing not given the otherwise full functioning system). Are you saying that to make VPN work you need to add custom routing info that is not described in the Server docs? If so what?
Thanks,
Hunter

Download iOS 8 once to Mac Mini Server and upgrade all iOS devices in the network

Is it possible to download iOS8 only once to the Mac Mini Server and use it to upgrade all eligible iOS devices (iPhones and iPads) in the same LAN?
I tried the following methods and they are just not working:
1. Connect an iPads Mini with Retina Display to the iTunes on Mac. I chose Download Only. Once downloaded the iPad Software Upgrade, I upgraded the connected iPad to iOS8. Then I connect another iPad (used to be on another Mac) to the same iTunes. I had to download iOS 8 again. It's not using the same downloaded iOS 8 file. (I did the same thing for an iPhone. Same result.)
2. I turned on the Caching Service (not Software Upgrade Service, i.e. for Mac Software) on the Mac Mini Server from the Server app. I then repeat step 1 above and got the same result. It seems that the Caching Service does not cache the iOS 8 Software Upgrade like what it does for other apps. (I think I may need to use some Apple Scripts but I have no such experience.)

Yes, it should work that way. However, I was told by an Apple Support that there was a problem and thus Server 3.2.1 was unable to do so.
I paid for Server 4 and it better provides the expected Caching Services for both iOS Software and Mac Software through the iOS and Mac App Stores.

How to add a computer to Mac Mini server network?

Hello,
Can anyone tell me how to add a Mac Air to the computers my Mac Mini server recognizes? Currently, I cannot share files between computers.
Thanks for any help!

Hmmm, not sure which end the problem is on, if you don't get an answer here you might post over here...
https://discussions.apple.com/community/servers_enterprise_software/mac_os_x_lio n_server

Adding computer to Mac Mini server network?

Hello,
Can anyone tell me how to add a Mac Air to the computers my Mac Mini server recognizes? Currently, I cannot share files between computers.
I have "All Users" checked under sys prefs >sharing.
Thanks for any help!

Hmmm, not sure which end the problem is on, if you don't get an answer here you might post over here...
https://discussions.apple.com/community/servers_enterprise_software/mac_os_x_lio n_server

Configuring Mac Mini Server via Airport Extreme via Netopia Modem

Can any anyone help me with the settings to allow internet access to my Mac Mini Server by a Web browser. What way to you configure the modem and extreme. The modem seems to want to duplicate a lot of the features of the extreme in it a has its own port forwarding etc. I have manually set all devices with fixed ip addressas it shares the net work with a Windows SBS. I have a static IP Address and Domain name registered and hosted dns has the domain tranfered. Nat is enabled and ftp, itunes ports open.
Internet is working on the local network which has a 3 Capsules, IMac, and 2 apple TV's all working and streaming from the server. Running Lion from last week.
Would appreciate any help as this is is my first time to use the forum.
Thanks again.

First welcome to the discussions.
To set up the client you'll first have to ask the Network Administrator for the name of the VPN server. The username and other details you will need to log on.
You will also need to find out if the VPN uses PPTP or L2TP over IP Sec. with that information in hand open Internet connect in the Applications folder choose NEW VPN Connection then you click on either PPTP or L2TP whichever the network uses, then click continue in the confiquration pop up menu, Choose Edit confiqurations Then enter the information the Network administrator gave you.
Bear in mind that the OSX client does not work with all VPN's.
You may have to purchase a universal VPN client such as VPN Tracker from Equinux ($90.00).
http://www.equinux.com
Good Luck Don

Mac mini server - MATLAB - Apple Remote Desktop

Hi all,
I am thinking of buying a Mac mini server, upgrading it to 8GB of RAM memory. I will use it mainly as follows:
- to be my HT"PC"
- to make intensive use of MATLAB
I know (think) that I will have no problems with the HTPC part, but I am wondering if it will be powerful enough for MATLAB. I have a mid-09 MacbookPro and it works fine there. And, I would like to access my MATLAB from the University, so, I need to know if Apple Remote Desktop will be fast enough to work properly with my server at home...(my uni internet connection is great, and my domestic connection is fine). I have read that ARD is quite good working with computers that are in the SAME network, but i don't know how it compares when the computers are not in the same one.
Thanks in advance

As far as being able to run Matlab, there should be no issue.
Accessing it over a network might be. I have never done it
myself, but some software, especially pricey stuff, can some
how identify it is being accessed over a network and refuse to
run. I have run into this occasionally when connecting and
attempting to run things on a PC remotely.

Please help me decide on a Mac mini server or MacBook Pro i7 for Logic

Hi folks,
I've really taxed my brain trying to figure out what's the smartest way to go. I'd love to know what any of you think I should do.
My current setup:
2007 MacBook Pro 2.33 GHz Core 2 Duo
2GB Ram
FSB 667 MHz
M-Audio ProFire 610
WD-Passport external drive for samples and audio files
Logic 8 (looking to upgrade to 9)
Record 1.5
Various AU plugins including Omnisphere, Miroslav Philharmonic, Amplitude 2, FM-8, BFD 2 and Korg Legacy Analogue
Final Cut Studio (latest version) for modest HD editing but sometimes multiclips as well
I tend to use lots of tracks - around 10 vocals, 4 guitars and lots of software instruments.
As you can imagine, Omnisphere runs like a dog past 2 instances and BFD practically makes everything grind to a halt.
Since going to Record 1.5, rewiring also seems to be unusably slow.
I'd love a new iMac or Mac Pro but I make several plane journeys to visit my Mum in another country. My solution has to be mobile, although I have got monitors, a keyboard and mouse that I can use at my Mum's.
As far as I can see, there are 2 options:
1
A new MacBook Pro 2.66 Ghz i7
2
A Mac Mini Server 2.66 Ghz Core 2 Duo
Physically, the Mac Mini is the better option:
- much lighter in my hand luggage so I could take it in addition to my existing MacBook Pro.
- more USB ports
My worries with getting a Mac Mini are:
- Is it powerful enough or at least significantly better than my MacBook Pro?
- Will it run the latest version of Final Cut Studio (a little off-topic, I know but I couldn't seem to find any straight answers elsewhere).
- Is it noisy when under a heavy workload?
- There is no Superdrive so can I use my MacBook Pro to install the software DVDs across a network?
Thanks for reading this. Let me know what you think.
Kind regards,
Steve

The mini will be about as powerful as your current MBP. You could have more RAM in the mini, 2 GB is certainly not enough for any serious work.
People on this list were initially(LP 9.0.0) underwhelmed by the MBP i7 dual core, it is a step up from your older MBP, but don't expect miracles. Get lots of RAM/a SSD for optimum performance.
9.1.3 may have improved performance, not sure,
Fast and relatively cheap: iMac i7 quad core. Not very portable, though.
Not ideal either is your M-audio interface, its drivers are below par making your Mac sweat more than necessary.
My 2c,
Zip

Mac Mini Server on my university network?

Similar Messages

Maybe you are looking for