10.6.4 Server on Mini Server - DNS Problems - Slow, EDNS log messages

Like a few of other people here, I'm having a hard time getting DNS to work smoothly on my new Mac Mini Server, now running Snow Leopard Server 10.6.4. I'd been running Leopard Server on a previous machine with much smoother DNS (though the Server Admin config didn't work, that's another story).
Resolution takes a very, very long time and eventually I'll get messages in the log saying 'success resolving 'xxxxxx' after reducing the advertised EDNS UDP packet size to 512 octets'.
I've searched everywhere and there seem to be two reasons why this is happening:
1. The DNS server is stopping responding on TCP, and is only responding on UDP;
2. Some other portion of my network (maybe the router) doesn't like UDP packets bigger than 512 octets.
For the first - is there any way I can fix this within OS X Server? There is no problem in the network since the router itself (running Linux) can resolve via TCP (using the forwarder addresses that are set up in my OS X Server config) instantly, and any clients that I switch from using the internal OS X Server (for DNS resolution) to use an external resolver work immediately too. I'm not sure why the daemon on OS X Server stops listening on TCP port 53 and only accepts UDP - and then only forwards on queries via EDNS via UDP - which is where I seem to have a problem.
Secondly - can I disable EDNS somehow and just do plain old DNS?
Some of the threads point to routers that don't like UDP packets over 512 octets, some point to firewalls and adaptive code that closes off ports when an app tries too many times, etc. I've opened ALL firewalls - turned off the OS X Server firewall, turned off the SPI firewall in the router (it's a Netgear DG834 with the DGTeam custom firmware), and I'm as far as I can go without buying a new router.
If the only answer is 'OS X Server needs a better router' then I'd appreciate what router I should buy - this situation is becoming untenable since the DNS resolution performance of my entire network is unpredictable, and I don't want to have to reboot the Server on a regular basis when there are loads of clients and their home directories sitting on it, since OS X Client gets twitchy when your home folder vanishes off the network…
I'm happy hacking config files - but can't seem to see anything in the DNS config that would allow me to either turn off EDNS or restrict the packet size to 512 octets (there's a comment in the config file that the directive is ignored for this one, fat lot of help that is). As to why the server itself stops listening to TCP port 53…. I have no idea and I can't find a solution with a search.
So in the absence of solutions - can anyone help me with a workaround? The only 'answered' question in this domain was 'answered' with the OP finding a workaround in their router firmware that changed the DNS cache packet size. I can't find anything like this in my router config, so I can't use this workaround. Are there any workarounds I can apply to my OS X Server, that don't rely on my router?
Yes, I know the router isn't that special, but it's a small business network. Advice on an upgrade would be welcome but doesn't solve the problem for me now. I'm based in the UK, if anyone also in the UK can recommend a suitable small-business NAT router I can use then I'd find that helpful, but I don't want to be told to purchase an enterprise-class router, turn off NAT and be recommended a store in the USA as it won't be that helpful
Ideally there'd be a way to tweak the DNS server on OS X to not bother with EDNS, or to stick to 512 octet sized packets (can I do this globally for all UDP from my server?), or to keep working on TCP…
Anyone know? The machine hosts client homes internally and serves mail, web and DNS externally. It's not a high-traffic system and it sits at the end of a business-grade ADSL line. I'm not being DoS'd - this behaviour seems random as to when it strikes. I try to restart the named daemon on the server when it strikes, but I need to be on the network to make that happen….
Solutions appear to be out, but I'd really appreciate a workaround. Many thanks in advance!

Hi Rob,
Not much of a MAC person myself however this support matrix might help:
http://www.adobe.com/products/coldfusion/coldfusion7/pdfs/cfmx7_systemsupportmatrix.pdf
Seeing your getting a few Java errors perhaps the JVM in CF7 1.4.2_09 is too early for MAC OS 10.6.4?
HTH, Carl.

Similar Messages

  • How To Set Up Mountain Lion Server/Point DNS to Mac Mini Server

    Hello, First of all I have no experience with setting up servers whatsoever. Below is what I have
    - Mac Mini with Mountain Lion Server
    - Time Capsule as my router
    - Comcast as my service provider
    My goal is to set up my MacMini as a sharepoint for files and other data with my other partners.
    - I have purchased a domaine name from NetworkSolutions. Does this mean that they are my DNS hosting as well? Not really sure. My biggest question is how to point my DNS to my mac mini server correctly.
    1. How do you point the DNS to my mac mini server.
    2. I've read somewhere to use the IP address from my mac mini server. The only IP address I see is from my Time Capsule (router). I know what my public IP adress is but I am not sure if that's the one to use. I think once I figure this DNS thing I can figure out the rest.
    Thanks - Need lots of help.

    Here's a detailed write-up on setting up internal (private) DNS on OS X Server, and no, you're probably not going to be setting up external DNS on your servers.  Your public DNS service will be hosted on and served from the Network Solutions DNS servers.

  • 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.

  • Using Mac Mini server, DNS, static IP, and external domain name

    Greetings!
    I need to know the direction to take in order to use my domain name for the great features offered in the mac mini server, while having local and public access to my server with security.
    I am trying to do the following on my new mac mini server:
    -Set up DNS (myserver.private)
    I have a static IP I want to use for all this with my ISP
    -ftp access
    -ichat ([email protected])
    -email ([email protected])
    -ical etc. ([email protected])
    -my work website(mydomain.com) with public access!
    -host websites(other domains)
    I need to know the direction to take in order to use my domain name for these features. I have a domain name with godaddy, and I am happy with keeping it with them, however, how to I make my external domain name work on my private server with public access is the question?
    Thank you,
    Daniel G

    [Read this|http://labs.hoffmanlabs.com/node/1436] as a start; you're basically going to decide if you want to use NAT or not; if you have enough public static IP addresses to avoid the disaster that's NAT. If you want to use NAT (and few reasonable folks want to, but sometimes we have to), then you get to run your own DNS services internally, and establish public DNS and power-forwarding at a (preferably server-grade) firewall. With NAT, you end up with split DNS, and that's covered in the cited document.
    ps: it's easier to [use sftp|http://labs.hoffmanlabs.com/node/942]; while that shares three letters with ftp, it avoids most of the problems of ftp.

  • Website on Mac Mini Server not accessible. Error 403 index document not available.

    Dear all,
    I'm trying to host a website on my Mac Mini Server. As far as I can see, my DNS is working correctly. Also my firewall is setup correctly. (I'm hosting another website which works OK). But I setup a new site. Basically a copy of the working site. But this site doesn't reflect an index.htm page. I receive an Error 403 with further information that there is no index document or that the site is secured. There is a contact link on this page directing to my webmaster. So I conclude that something is working, but no index.htm page. Has anyone similar experience? And offcourse a solution?
    Many thanks.

    Launch Terminal.app and issue the commands:
    cd /Library/Webserver/Documents/
    ls -al
    And see if the files are readable by the web server.   Here's an example index file listing that's owned by root and with group access for admin folks, and this file is marked as readable and writable for the owner and the group, and is readable for everybody else:
    -rw-rw-r--    1 root  admin   5094 Jul 25  2009 index.html
    In this configuration, the web server would be using the other access; the web server can read this file, but not write to it.  Here is how to duplicate these ownership and access settings on your own index.html file, assuming that you have that file present in the ls listing above, and assuming that you have issued the cd (change default directory) command shown above:
    sudo chown root:admin index.html
    sudo chmod ug=rw,o=r index.html
    You will need to enter your administrative password for the sudo command.
    I would very strongly suggest that you start learning some basics of bash and of Apache, because you're going to be needing those skills very soon.

  • Please help. Can no longer connect to my Mac Mini Server

    Up until two days ago, my iMacs were connecting to my Mac Mini Server normally. All of a sudden I could no longer transfer files without being prompted to type my password. Enter password and nothing happened, then got an error message stating that I don't have permission to do that. Now, a day later, no acces to my server. Has anyone ever experienced this? Can anyone please help? I've read the Mac mini booklet but doesn't have any troubleshooting info. Thanks in advance.

    Hello MrHoffman,
    Thank you for the advice. I went into Terminal first and typed in your command and this is what resulted:
    Last login: Fri Jan 24 22:39:08 on ttys000
    serverX:~ serverx$ sudo changeip -checkhostname
    Password:
    Sorry, try again.
    Password:
    Sorry, try again.
    Password:
    Primary address     = 192.168.1.7
    Current HostName    = serverX.private
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    serverX:~ serverx$
    serverX:~ serverx$
    I'm not very experienced with programming or coding, but this message seems to indicate that there's a problem with DNS just like you noted. I've highlighted the note in bold...What can you make of this or the logs from console below?
    Below is what I found in Console:
    1/24/14 8:55:08 AM          com.apple.launchd[1]          *** launchd[1] has started up. ***
    1/24/14 8:55:19 AM          com.apple.launchd[1]          (com.apple.NotificationServer[73]) Suspicious setup: User "jabber" maps to user: _jabber
    1/24/14 8:55:25 AM          edu.mit.Kerberos.kadmind[58]          kadmind: starting...
    1/24/14 8:55:27 AM          org.jabber.jabberd[53]          ERROR: Could not create /var/run/jabberd: Permission denied
    1/24/14 8:55:27 AM          com.apple.launchd[1]          (org.jabber.jabberd[53]) Exited with exit code: 1
    1/24/14 8:55:27 AM          com.apple.launchd[1]          (org.jabber.jabberd) Throttling respawn: Will start in 1 seconds
    1/24/14 8:55:28 AM          org.jabber.jabberd[130]          ERROR: Could not create /var/run/jabberd: Permission denied
    1/24/14 8:55:28 AM          com.apple.launchd[1]          (org.jabber.jabberd[130]) Exited with exit code: 1
    1/24/14 8:55:28 AM          com.apple.launchd[1]          (org.jabber.jabberd) Throttling respawn: Will start in 10 seconds
    1/24/14 8:55:28 AM          com.apple.printservice_LPR_mDNS_Plotter_Epson_7600[70]          Registering Service Plotter Epson 7600._printer._tcp port 515 TXT txtvers=1 qtotal=1 rp=Plotter_Epson_7600 pdl=application/postscript ty=\(null\)
    1/24/14 8:55:28 AM          com.apple.printservice_LPR_mDNS_Plotter_Epson_7600[70]           8:55:28.703  Got a reply for service Plotter Epson 7600._printer._tcp.local.: Name now registered and active
    1/24/14 8:55:30 AM          org.jabber.proxy65[52]          /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python /twisted/persisted/sob.py:12: DeprecationWarning: the md5 module is deprecated; use hashlib instead
    1/24/14 8:55:30 AM          org.jabber.proxy65[52]            import os, md5, sys
    1/24/14 8:55:30 AM          org.jabber.proxy65[52]          /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python /twisted/python/filepath.py:12: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
    1/24/14 8:55:34 AM          com.apple.launchd.peruser.501[174]          (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/24/14 8:55:35 AM          ServerScanner[200]          Preference says we shouldn't scan
    Thanks!

  • Is the Snow Leopard Mac Mini Server the right solution for my office?

    I'm the de facto "sysadmin" for my small office, which usually just means I set up the wireless, configure network printing, troubleshoot little issues with Mail and MS Office products.
    Currently, we have 4 employees all on iMacs. We share files through a slapped-together setup, where there is a public folder on our owner's iMac and we all share files there. There are a few problems with this:
    - If the owner's computer is off, no-one can get to the shared files.
    - The owner's computer has had some strange "permissions" issues so sometimes files in the "Public" shared folder end up being read-only, or "read & write" for "nobody".
    - A 5th employee telecommutes on an iMac, and can't access the shared folder or files.
    So, we're considering getting a Mac Mini Server to do file storage and sharing, both locally and with telecommuting employees (of which there may be more in the future).
    - Is this the best solution to our needs - really just file sharing, no web hosting or anything like that?
    - What level of access control / authentication can we do on the Server? For example, could we have a password protected folder on the server to restrict access?
    - Would we need to upgrade our standard DSL service if we want to share files on the server with folks not on the local network?
    - Am I biting off more than I can chew here, given that my technical knowledge is slim but I am the most computer-literate of anyone in the office, so I will need to trouble-shoot any issues that come up with the server?

    For your stated goal, network-attached storage (NAS) or an always-on Mac client would be a simpler solution. Either preferably with RAID, and with provisions and storage for periodic archives.
    A Mac OS X Server box is overkill. The Mac client boxes have 10-client sharing.
    If you want single-signon and shared directory services and mail and web and various of the other pieces and services that are available within, then you can grow into a Mac OS X Server box.
    A server is rather more to manage, regardless of what you choose. You're getting DNS and networking and other core pieces, minimally, and you're also responsible for many of the configuration settings and services and details that a client box receives from a server box. And you're definitely dealing with protections and such across multiple boxes.
    For some other perspectives, there are various previous discussions of this posted around the forums. A search that includes NAS should kick over a few of these; this is a typical low-end alternative to running a server.

  • Mac Mini Server freezing in install when choosing PPPoE

    I have a Mac Mini Server and when I go through the installation procedure and choose the connect PPPoE from the Network settings, the installation hangs every time.
    I have already tried several clean installs from the Mac Mini Server disc to no avail.
    Suggestions?
    Thank You.

    What part of the install process do you have trouble with? I'm assuming, and I think Tony did as well, you're talking about the server setup assistant that launches once the OS is installed. Naming your server/domain is a critical part of setup, as is DNS. If you put faulty configs in during setup, or try to setup services before DNS is working, you'll run into trouble - so please include whatever you're trying to do - if you're new to servers, most everybody around here will be helpful or at least understanding.
    In any event there's a great tutorial at
    http://www.wazmac.com/serversnetwork/fileservers/osxserversetup/index.htm
    While I agree with Tony that PPPoE isn't the best bet, you ought to be able to make it work - but you will need a static IP for your server. Best bet is probably to make it a static IP on your LAN using NAT and let your router/firewall have the live IP. But more info is always better - what are you trying to setup and what other equipment/network stuff is already going on? There are a lot of ways to setup a server and to setup a network, and there is certainly no one correct solution. Somebody smart (like Tony) may be able to give you a lot more options with more details. I'll try too, but I'm far from the most knowledgeable person around these parts.
    Another thought - if you're not using the advanced server, I believe you need DNS set up beforehand somewhere - if you just enter your ISP's DNS server info, it won;t have any records for your server. The Wazmac setup notes will walk you through setting up your own DNS for your LAN and using your ISP's DNS for everything on the WAN side.
    Message was edited by: Jeff Kelleher

  • Mac mini Server 10.6  unable to search for files on the server from desktop.

    I'm running Mac mini Server 10.6 with 15 various Apple Mac desktops 10.4 / 10.6. The problem i'm having is that i'm unable to search for files on the server from any of the desktops. I have fixed permissions and rebooted. I can perfomr a search though command - F and spotlight from the server.
    Anyone have any ideas?

    I have a Mac mini server with Mac osx 10.6.8 installed --- I have a website {UNDER CONSTRUCTION} installed on it with a REGISTERED DOMAIN NAME belizeansworldwide.com -->[DNS service w/GoDaddy]  & DSL INTERNET service  w/VERIZON --- {My server is the ONLY DEVICE CONNECTED to my VERIZON DSL router/modem}
    When I enter my DOMAIN NAME or WAN IP # in my browser(s)--> Chrome OR Safari -- i get my Verizon modem
    set-up page-->{this incl the WAN IP# as I expected}----{NORMALLY I WOULD ACCESS MY Actiontec
    modem/router via 192.168.1.1} --- While in that webpage there's an option "shared files/folders"   & clicking on that option DISPLAYS MY WEBSITE --->  {"PORT FORWARDING DID NOT RESOLVE THAT"}
    My next attempt @ a solution was through my Server's SystemPreference>Sharing>Internet Sharing
    & this the Original Object of my post ===>  "MY SHARING PANEL DOES NOT INCLUDE THE OPTION
    FOR   'Internet Sharing' among the others like CD DVD, Remote Login,Remote Management, Bluetooth Sharing, etc.etc ---- Hope this additional info will help to clarify  &/or explain my problem
    Thanks, & best regards to you & yours

  • Cannot see Mac Mini Server from Internet: DynDNS alias gets thru cable modem to wireless router, not to the Mac Mini. How to configure?

    I want to make my Mac Mini Server (Lion) visible to the Internet from my home LAN. I have followed the Lion server install wizards and also set up a dynamic DNS at DynDNS.com.
    When I enter the Internet address with the proper alias from a web browser, I get dumped into the admin screen of the Linksys wireless router WRT300N. Hint: the WRT300N provides DHCP for the LAN, not the cable modem providing DHCP. The WRT300N has DDNS service set up. NAT and RIP are disabled. The Mac Mini DHCP is reserved.
    Suggestions? I could use the Motorola Surfboard SB6121 to provide DHCP but have hesitations.
    Point me to the right discussion/article and get me back on track, please.

    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.

  • 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.

  • I'm using a mac mini server 10.6.8--no "internet sharing" option on my SystemsPreferences Sharing panel

    There  are options for DVD & CD Sharing, REmote Login, Remote Management, Bluetooth Sharing,etc
    BUT NO  "INTERNET SHARING"
    Can anyone help with this  I'm trying to resolve a problem to make a website on my server available
    on the internet & belive that this might lead to a solution or @ least point me in the right direction.
    Thanks for any help
    Rcpandy

    I have a Mac mini server with Mac osx 10.6.8 installed --- I have a website {UNDER CONSTRUCTION} installed on it with a REGISTERED DOMAIN NAME belizeansworldwide.com -->[DNS service w/GoDaddy]  & DSL INTERNET service  w/VERIZON --- {My server is the ONLY DEVICE CONNECTED to my VERIZON DSL router/modem}
    When I enter my DOMAIN NAME or WAN IP # in my browser(s)--> Chrome OR Safari -- i get my Verizon modem
    set-up page-->{this incl the WAN IP# as I expected}----{NORMALLY I WOULD ACCESS MY Actiontec
    modem/router via 192.168.1.1} --- While in that webpage there's an option "shared files/folders"   & clicking on that option DISPLAYS MY WEBSITE --->  {"PORT FORWARDING DID NOT RESOLVE THAT"}
    My next attempt @ a solution was through my Server's SystemPreference>Sharing>Internet Sharing
    & this the Original Object of my post ===>  "MY SHARING PANEL DOES NOT INCLUDE THE OPTION
    FOR   'Internet Sharing' among the others like CD DVD, Remote Login,Remote Management, Bluetooth Sharing, etc.etc ---- Hope this additional info will help to clarify  &/or explain my problem
    Thanks, & best regards to you & yours

  • 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.

  • ITunes Server with D-Link DNS-323 NAS - not showing up in Shared list

    Hi
    I bought a DNS-323 to hold all my music. I am trying to get it working with iTunes.
    I have enabled the iTunes Server function on the DNS-323, selecting which folder I want to use for music, and have allowed the device to 'refresh'. It then tells me it should appear in iTunes.
    I have installed iTunes 10.2.1.1, but under Sharing, the only option that appears is Home Share. The DNS-323 does not appear in the list.
    I have tried rebooting the NAS to no effect.
    I've searched a lot on the subject and have seen that iTunes 10 causes issues with iTunes Server on a NAS device, but many people were saying that 10.1 fixes it. However, the threads then seem to go dead with no definitive answer.
    Can anyone tell me where iTunes Server is still supported in 10.2.1.1, and if so if there are any suggestions on how to get the device to show up? ALL I get is the Home Sharing option under the Shared heading in iTunes. I tried iTunes 9.2.1 but had the same issue.
    Thanks in advance
    Dave

    Hey Travis, mine only worked when I pointed to a folder with all music files: mp3, m4a...  (all separated by artists folders)
    After that, I could see my DNS 323 but I couldn't drag any songs to any playlists.  I could also see some playlists on my DNS 323 but I couldn't modify them or add any. 
    I lost 3 days trying everithing but nothing worked.  In the end, I clicked on the itunes "File" menu (Top left) and selected "Add folder to library" and I selected the folder with all my music.  It must have taken 10 hours to import all the songs.  It took me around 1:30 hours to rename over 300 songs (out of 1700) because they weren't properly named.  They were all at the bottom of the list.
    On my second computer, I cheated because I clicked on "Edit" in iTunes and selected "Preferences".  On the "Advanced" tab, I changes the ITunes Media Folder Location and pointed to the one I created with the first computer.  The music appeared (I didn't have to rename 300 songs again) and the playlists I had created were also there.  This way, I only manage one computer and it should chage the other one.
    I'm not sure what will happen when I add new songs but I had selected the music folder on the first computer so I hope they are added automatically.  I think I might have to go back to the DNS 323 and do a refresh on the iTunes server to see new songs but I haven't tried it yet.
    Hope it helps,

  • 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

Maybe you are looking for