Mac mini server VPN

I've got a new mac mini server (2010). I cannot get the Cisco VPN client from the University I work for to install on the mini. Anyone else having this problem?

Heh Michael
I got this working using the settings in the screenshots below. I know I had a heck of a time trying to make it work but it does using these for me. Sometimes on the first connection it rejects the credentials, but on the second time it connects - no idea why. Hope this helps:

Similar Messages

Mac Mini Server VPN Issues - Driving me insane

Mac Mini Late 2012
Late 2012
Software OS X 10.8.2 (12C2034)
Server Version 2.2(166)
Previous Issues experiencing: Before i rang apple support and spoke with enterprise support i had no luck at all for weeks getting the VPN connected.
After calling support it seemed to have something to do with my useraccount - Guided through the process of creating new dummy account and trying to connect then. Which sssucceeded..!!!
However. Back on my main account and deleting other user accounts im facing great difficulty setting up a VPN for the purpose of a VPN.
The issue now is: Once i get connected to my mac successfully from my iPhone using the VPN server all is good to go.
However. WHen i restart my computer (For testing purposes this was done) When the MacOS boots up again I have to relog into the Server app. Resign into the program, THen try and reconnect my VPN (WHich will be impossible to do if im out of the country). But it doesnt end there. I keep having to reisue a new Shared Password. FOr testing i Used 1234abcd. Got a good connection - Proceeded with restart and then had to change 12345abcd.
So i have tested this well over 50 times. Trying to find a solution.
In summary: Everytime i use the MAC Mini Server, I have to.
1 Auto login.
2 Repopen the Server.app even though i have enabled it to autostart.
3. Log into the server app (Not another networks Server)
4 Change my shared password
5 Try and reconnect and pray it works.
Whats the quick fix for this. Its driving me insain and honestly making this a 1000$ peice of junk. Its hopeless regarding a server. I want it to be completely operational when i leave the country. My server is designed to Shut on and off between down times (Night Times) when i wake up i jsut want to be able to reconnect via a VPN and no issues, be on my way with life. Not having to wory about remote logging into the PC to then reset up the server.
Any help please!

I sometimes get this same message window or a VPN Not Authorized window after rebooting my server. I have the Mac Mini late-2012 base model running OS X Server. When I do, I just try reconnecting and after no more than 3 attempts a connection is made either by my rMBP or my iPhone5.
I leave my server running 24/7 and I rarely get either of the two messages mentioned above.
You shouldn't need to open the Server.app unless you need to manage services. The Server services you configured should start everytime you restart. I have the Server.app icon on my Dock, but I do not launch it automatically. I manually click to launch it when I need to manage the Server, Accounts or Services.

Mac Mini Server VPN requires restart of service after each reboot

Mac mini Server (Late 2012)
OS X 10.8.4
After a reboot, when viewing in Server.app, VPN service is turned on, however no connections can be made until the service is turned off then back on again.
VPN service log entry shows "Listening for connections..." but doesn't allow incoming VPN calls until the service is restarted.
Anyone else having similar issues or have suggested solutions?
Thanks much!
Jim

Try this
https://discussions.apple.com/message/22564125#22564125

Mac Mini Server VPN-Window 7 client

Hi,
The VPN connection from MacBookPro to Mac Mini Server (2011 with Mountain Lion 10.8.2) VPN works like magic. But, I never had any luck with any of Windows 7 laptops. Could any one take me to a good link to the Windows 7 VPN setup instruction?
Thank you so much in advance for your time reading this.
Best,
Michael

Heh Michael
I got this working using the settings in the screenshots below. I know I had a heck of a time trying to make it work but it does using these for me. Sometimes on the first connection it rejects the credentials, but on the second time it connects - no idea why. Hope this helps:

Mac mini server on two different location

Hi,
With my partner we are working on very havy image file from two different location. we wont to be able to share those file to each other easly and quickly mad make sur those file are allways up to date.
- My first idea was to install in my place one mac mini server with external hard drive (RAID 0) and install the same server in my partner place. then I would like to create a VPN connexion between both Mac Mini server and setup a kind of RAID 1 between then. link that if my partner modify an image file on the server, With a short delay I will be able to see it on my side. this solution would be the best for me as all the data would be save in two different location and I would not have any backup issue.
I did not buy the MAC mini server yet but as soon that I know the best soluiton and that it is possilbe to do so I will buy it.
- My second idea (if the first one is not possible or if you guy's convins me that my idea is stupide) would be to have one MAC Mini server in one location setup with an external hard drive in RAID 01. my partner will need to connect to this server through VPN. This solution seems to be a good option but my partner will need to copy the file in local to work on it (few Gb eatch file) and copy it back on the server when he finish to work on it.
With this solution I will also need to organise manual backup through another hard drive to avoid to have all our data in the same location.
Witch one of those solution seems the best and can work with MAC mini server? If you have another idea for my situation I m more then happy to read it.
Knowing that other user may need to access to my file, is the MAC Mini server VPN connection safe and fast?
Thank you in advance for your help.
Chris.

The fact that you are both working on multi-gigabyte
files, the statement BDAqua made about network speed
is a big issue. Small incremental changes in a single
multi-gigabyte file still require that entire file to be transferred.
There in lies the big issue with network speeds.
Basically, it seems idea 1 will probably not work well and
besides, RAID is for local drives and not for over networks.
One solution to the synchronization issue is have a single
computer that has the application and the data and log into
it and work remotely. However, it sounds like these are image
files and working and any kind of graphics over a remote
connection is problematic unless there is a very high speed
network connection.
Second idea is the simple solution. As for the backup, that
can be automated with backup software and the backup could be
put any where.

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.

VPN on a new Mac Mini Server setup! PLEASE HELP

I want to use my newly purchased Mac Mini Server as a VPN. I cannot find any solid information on how to set this up. Can anyone help me with a tutorial or even a link? thanks!!!

Have you enabled the service, set IP-range and set a shared secret?
Then you have to choose who (users) should be able to access VPN.

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.

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 question

I'm working on replacing the Mac Mini server in a small office configuration where the Mini is acting as a fileserver, a Filemaker Pro server and Time Machine backup server. There are 8 machines in the office using the server. The files being shared and the time machine backups are on a drobo. Currently it's a late 2009 Mac Mini server with a 2.53Ghz Core2Duo. For the purposes outlined above, is there any reason to get a 2.8Ghz or 3.0Ghz processor, or is the mid-range 2.6Ghz i5 totally sufficient? In either case I would be maxing the RAM.
I'd also be buying a new Drobo to attach to the new Mac Mini, so I was going to keep Time Machine backups on the old drobo, but move filesharing to the new Drobo. Originally I had thought I'd have both those drobos connected to the new Mac Mini, but then it occurred to me that perhaps it would be advantageous to also keep the old Mac Mini server in use with the old Drobo. Is there an advantage to keeping the old Mac Mini server running in the office and utilizing it SOLELY as for centralized Time Machine backups, leaving the new Mac Mini server to just be a fileserver and Filemaker Pro machine. Would that make any difference?

I don't see any advantage with a 2.8 or 3.0Ghz processor versus a 2.6Ghz. The 2.6 should be plenty of processing power for your needs.
In my opinion, keeping the old Mac Mini to offload some of the "duties" is perfectly fine. For example, I have a home network with 2 MMs. One runs ML and Server. It services the household Macs for file sharing and time machine back ups. The other MM runs Mavericks and Server. It services some file sharing but mostly network accounts, VPN services and time machine back ups (for both servers). Both only have 4GB of RAM and work great for my needs. It's overkill for a home network, but I have a back up server and can easily add the services from the other if one goes down. You would have that same capability keeping your old MM.

Mac Mini Server and Windows SBS

I am running an aging Dell server with SBS 2003 and wondered whether it would be possible to use one or perhaps two Mac Mini Servers for my needs. I used to host my own Exchange on this server but I was running out of HD space and it was not easily upgradable so I opted to use Hosted Exchange and use the old server for two things: as a File Server and to run a databse that was written for us in MS SQL Server. I access the SQL database via RDP from my Dell laptop (docked in the office and connected to two monitors with extended desktop). I have long been a Mac user at home and have someone else working on my team now who uses a Macbook Pro. He is currently not using the server at all, but it would make sense for him to be able to access some aspects of the File Server. My question is whether I can replace this Dell Server with a Mac Mini Server but booting in Windows SBS 2008 or whatever the newer version is, assuming it can still run the old SQL Server database. Would it be possible to use the same Mini Server as a File Server or better to use a separate one for that or perhaps some other solution for a File Server. I would like things to be RAID so that I have backups which are required for compliance reasons. I currently run a nightly backup of the data on teh File Server and the SQL database onto an external drive and also the same back up is done using iBackup as an offsite back up. I need the developers of the SQL Server database to be able to remote in from their Windows machines in India for periodic updates and system maintenance. I also would need to be able to access the same database from my laptop in the office, and I believe there are limits on the number of connections one can have with SBS. I do have VPN access set up via my Sonicwall TZ210 router/firewall that enables me to access the Server if I am traveling with my laptop or am at home on my iMac (although that client has never worked properly) but currently our internet connection is too slow to make the VPN usable when I'm away from the office.
Thanks to anyone who can answer all or part of these questions. Perhaps I should have one Mini Server for the SQL database and one as a File Server (or could that just be done with a network drive? I'm not sure I really know the difference - I'm a solo act here, not a systems guy, so am feeling my way somewhat).

Hi might see if you can run that Server version in OSX using...
Parallels...
http://www.parallels.com/
VmWare Fusion...
http://www.vmware.com/mac
VirtualBox...
http://www.virtualbox.org/wiki/Downloads

Mac mini Server & Mavericks?

Am I supposed to update my Mac mini Server with Mavericks?

Upgrading to Mavericks server is a two step process. First you install the free Mavericks upgrade and it will give you a message about it stopping some of the server services. After that is done the second step is to purchase Server 3.0 ($19.99) from the App store and install that.
Some people have reported issue with the upgrade but mine went flawlessly. However, there is an issue with the VPN server not working correctly. Here is the link to the discussion on that issue.
https://discussions.apple.com/thread/5468992?start=0&tstart=0

Mac mini Server as a gateway/router

I'd like to make my Mac mini server my main gateway for my office.
I'd like it to perform the following tasks:
- DHCP & NAT for sharing an Internet connection
- a wireless access point so that no AEBS or TC is necessary
- VPN for access to the Daylite server that will be running on it as well as file sharing for remote users
My goal here is to create a single Internet alliance that will prevent me from having to use a separate router and will provide secure remote access to the LAN.
I have a Mac mini server and a USB Ethernet adapter. I connected the USB Ethernet adapter to the WAN which has a static IP. And the built in Ethernet to the gigabit switch for the LAN.
So far, I have two problems:
1) I can't seem to VPN in from remote despite my best efforts of setting this up with the gateway assistant.
2) I have no idea on how I can use the built-in airport card to become a wireless access point for the wireless clients in the office. I chose the airport in the gateway assistant but wireless clients are on a different subnet and can't see the LAN resources.
I'm interested in hearing other ideas and strategies on how to use the mms in this way. Is anyone else doing this? Everyone seems to want to use an AEBS or TC in addition to the mms and maybe I'm missing something but why would you need one?

It wasn't so much the $50 that I was worried about... just the redundancy... having both an OS X Server AND an Airport Extreme (or third-party router) seemed like such a waste if the server could be made to do it all.
So, at this point, I see two options:
1) Put an AEBS on the gigabit switch (LAN) and turn off everything... essentially reducing it down to a wireless access point... and put it in Bridge mode so that wireless clients can see the wired LAN.
2) Use the AEBS as my gateway and DMZ the server... turning off the gateway features (DNS, DHCP, NAT, etc...) on the server. This would remove the need for the USB Ethernet adapter but would I still be able to configure it as a VPN?
Either one seems a shame. I was really hoping for a single-box solution to sell my clients.
The other problem is still happening... for some reason, I can't connect to the VPN... it doesn't even seem to be getting to the authentication part. It simply says, "The Server is not responding". This is strange since other services for which I've forwarded specific ports seem to respond without issue. I assumed that all the neccessary ports would be opened when I turned on the VPN feature... did I miss something?

After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"

After i installed updates for my mac mini server, the web services for the server app wont start, it gives an error massage: "Error Reading Settings"
The system logs reads:
Mar 29 22:06:25 server servermgrd[82]: servermgr_web: Error Domain=XSServerFoundationErrorDomain Code=4 "Failed to read settings: Exception:
          undefined method `downcase' for nil:NilClass
          ." UserInfo=0x7fc547901080 {NSLocalizedDescription=Failed to read settings: Exception:
          undefined method `downcase' for nil:NilClass

To check the local network for some of the common configuration problems, launch Terminal.app and issue the following diagnostic command:
sudo changeip -checkhostname
That'll report some local configuration information and then either no errors detected and no changes required, or it'll point to whatever configuration errors or issues it might detect. That doesn't catch everything, but it catches the common errors.
FWIW, 192.168.0.0/24 and 192.168.1.0/24 are poor choices for the local network, as VPNs are based on IP routing and IP routing gets tangled when the same subnet is used on both ends of the VPN. 192.168.0.0/24 and 192.168.1.0/24 are near ubiquitous in home networks and coffee shops.

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

Mac mini server VPN

Similar Messages

Maybe you are looking for