New Mini Server, ethernet problem

I had setup my mini using wireless, but want to switch to being hardwired. I turned off the wifi, set my airport extreme to assign a particular IP to the MAC address of the mini's ethernet port, and rebooted. The mini only gets a 169* IP -- it never gets a real ip address and I'm baffled. What is the story there?

Hi
Frist obvious thing that springs to mind - is the APX your DHCP Server?
HTH?
Tony

Similar Messages

SSD for new Mini Server?

Hi, guys!
First time poster here
I would like to know your opinion on the following:
I am planning to go for a new Mini Server and run it in pair with an external Thunderbolt RAID storage. All shared data will be stored on the external RAID, while the internal Mini's disk will be used for running OS, storing account data and running basic services like File Sharing, Print Sharing and VPN. The question is: will I benefit from replacing the default 7200 HDDs with an SSD?
Of course, the machine will start faster and generally run smoother, but I don't really care about that as I will hardly ever see its interface after the setup is done. I am interested in whether SSD will contribute to increasing speed when my users will access their data (stored on the external RAID)? The access chain is as follows: Client computer - LAN - Mini Server (with HDD or SSD) - Thunderbolt connection - RAID.
Another question that bothers me is redundancy, of course. With 2 HDDs I would make a RAID 1 massive to provide for user account data redundancy. To achieve the same goal with SSD I would need to add a second one, which is getting quite expensive, frankly speaking But this is a completely different issue, I guess.
Would greatly appreciate any feedback.

I'm unsure of the proper procedure as I'm not experienced dealing with Fusion Drive setups. If Disk Utility shows you have a 1.5 TB drive, then what do you see when you boot the computer and check disk drive space using Get Info? I know you can revert the volume you have back to standard format if you don't mind using the Terminal in your Utilities folder:
Open the Terminal and paste or enter the following at the prompt:
diskutil list
Press RETURN. This will list for you the device information for your HDD. Here is an example of the output:
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *120.0 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS Yosemite                119.2 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
You want what you see at the top left - /dev/diskn, where n is the integer number. Then enter or paste at the prompt:
sudo diskutil cs revert /dev/diskn ; replace the n with the integer number found above.
Press RETURN and enter your admin password when prompted. It will not echo to the screen, so be careful typing. Press RETURN again. Wait until it completes the process which is when the prompt returns.
Given the potential danger when using the Terminal in this way, please be sure you have first made a reliable backup. Better safe than sorry.

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.

Mountain Lion Mac Mini Server Ethernet Port Not Working

I have a Mac Mini Server and once I upgraded to Mountain Lion Server the Ethernet port is unresponsive. It worked before upgrading. Is there something with Mountain Lion Server that is causing the Ethernet port not to work properly?

Make a "Genius" appointment at an Apple Store.
Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

MAC Mini Server Startup Problems

Help!
MAC newbee. Just bought a new MAC Mini Server, got monitor connections in place; have wireless keyboard and trackpad; at startup I get the white screen with apple background then followed by a screen with a graphic with some rounded-corners rectangle; it just sits there with the rotating gear, rotating forever.
SUpports says I need a wired, USB, keyboard to get it started. Makes no sense to me. Help anyone? I am about to return the product--with disgust.

Below is my the answer to a previous helper. Yes, you need to start with USB before setting your devices to work with bluetooth. Thank you jut the same. Best, Larry
----------------my response-----------
Thanks. You are right. I bought a cheap USB keyboard and mouse and have been doing fine ever since. All's well and working.
There is a rather subdued mention of the need for an initial USB connection in the documentation, however, you'd think that sales--that department is a bit on the weak side--would have said something to me while putting my order together for bluetooth devices only.
Oh well....have been doing fine ever since...all set up. Again, sincere thanks.

New Mini Server - Can't see volume to migrate from.

I literally just opened my mac mini server (Lion Server) and as usual the setup screens started. Once it said I could migrate a server I proceeded with that option. However there's no volumes that the Mini Server recognizes. I am plugged into the LAN which has our Snow Leopard server, but it doesn't see that.
Is the mini server supposed to be able to see network attached Mac computers or not? Do I need to physically plug our Snow Leopard server into the mini? This is stange. Just opened a new machine and can't even get past the setup. Is there a server migration assistant?

I have not tried migrating a server in this way, but I would imagine it would be a similar process as to how Migration Assistant works.
If so, you would either need the old server drive connected as an external disk, perhaps by using FireWire Target Disk Mode. It would not apply here, but if you for example had a Mac Pro originally running Snow Leopard Server you would be able to do a similar thing when migrating to a new Mac Pro running Lion Server by fitting the old hard disk internally and then be able to migrate from it.
In your case FireWire Target Disk mode sounds like the easiest option. See http://support.apple.com/kb/ht1661

Screen Share for Brand New Mini Server

Hello all,
just unpacked the brand new Mac Mini Server and don't know what to do. We all work on laptops in my studio so have no keyboards to use with the thing. I haven't turned it on yet, but is there a way to immediately go into remote screen sharing so I can configure it etc? Thanks for any tips that keep me from having to go dig up a keyboard!

Hi
Do you see an option to Screen Share on a client mac?
With the MacMini there should be two disks. One of them is for installing the Server Administration applications. Install these on a client mac - must be 10.6. Once installed launch Server Admin. Switch on your MacMini and connect it to the network. Good idea to have DHCP running somewhere. Presumably whatever you're using for your Router/Firewall? Make a note of the MacMini's Serial Number (first 8 characters) Launch Server Admin and dismiss the authentication prompt. Select "Set Up Remote Server" from the Server Admin Menu.
It should be fairly obvious from there - hopefully?
HTH?
Tony

New mini server not showing upgrade to Server.app

We have a client that just upgraded to a new Mac mini server that shipped with OS X 10.8 and had Server.app 2.0.23 installed. The Software Update feature is not showing the option to update Server.app to 2.2.2. If I search in the App Store it shows as something that can be purchased. Any thoughts?

Actually though I've seen some big reviews discuss Server.app 2.2.2 being used in OS X 10.9, it is actually for OS X 10.8 which is what my client is running. Server.app 3.0 is what you purchase for OS X 10.9. I appreciate our input though. So my issue is that the machine shipped from Apple with OS X 10.8.1 and Server.app 2.0.23. I have successfully upgraded to the latest firmware updates, OS X 10.8.5 etc, but it does not offer Server.app 2.2.2 as an option which is strange and I have no idea how to rectify it. As long at it works fine for their needs I will not worry about it and hold off until they do go to OS X 10.9 and they can purchase Server.app 3.x at that time.

2 brand new mini ipods, same problem!

Me and my brother each bought a mini ipod today, and we both have the same problem. the ipods are skipping parts of songs and getting stuck, like a cd player does when the cd is scratched. please help!

Mine had a similar problem after I plugged it into my computer's speakers to play. I sent it in for repair and they sent me a new one...still don't know what the problem was though.

Linksys print server/ethernet problems

I am trying to hook up a ethernet Linksis print server to my Comcast wireless gateway 3. When I plug the ethernet cable in I get an orange light. When I try to send a print job nothing happens. can anyone help me?

Can you tell us your printer server model number and the model number of your gateway?

New Mac Mini server/OS X Lion, no Internet access

I set up new Mini server on home network, I can access all internal network resources (other computers, airport express, NAS, etc) but cannot get to connect to external/internet sites (apple.com, google.com, iTunes Store, Mac Updates, Mail, etc). All other Mac hardware on network can access internet (MBP,iPads). What am I missing?

Double check your DNS settings. DNS is what translates the web names to IP addresses. I would double check this.

Singing the praises of the new Mac Mini Server

I've been running Maya (a 3D modeling and animation application) on a mid-2010 17" MacBook Pro: dual core 2.66GHz i7 processor, 8GB of RAM. It's done quite well, even when rendering frames of animation, but I knew I needed to speed things up a bit when I'm rendering out longer animation clips at reasonably high resolution. When the new Mac Mini refresh kicked in I decided to take the plunge and pick up the new Mini Server as an extra render node.
Wow, was that a great decision.
With the same 8GB of RAM, but adding quad core i7 plus Sandy Bridge, it screams. I just ran a disributed render test: 10 seconds of animation at 24 frames per second, 1080p HD. The Mini Server easily rendered three frames for every one the MBP churned out. That means my overal render time has been cut to roughly 25% of what it was before.
If ever you wondered what that extra horsepower means in actual useage terms, now you know.

Any time. I have some real numbers:
240 frames, 1080p resolution.
MacBook Pro alone: 4 hours, 17 minutes.
With Mac Mini Server added (distributed render): 1 hour, 3 minutes.
Yeah, I'm pleased.

Mini Server: Time Capsule backup.

Hello,
Does Time Machine do a reliable backup of a Mini SL 10.6 Server to a Time Capsule?
if so, does it back up BOTH volumes of the new Mini Server?
Thanks!

Hi,
In answer to your 'both volumes' questions, yes it does. When you enable Time Machine on servers and normal Mac OS X, there is an Options button that allows you to exclude certain folders, for example I exclude my Downloads folder and my VMware Fusion Virtual Machines folder. You'll see by default the only thing in there is the external disk you are using to backup to.
In terms of 'reliable', I guess that depends on what you mean ! Personally I've been using Time Machines since it first appeared in Mac OS X, and recently having upgraded to an iMac I used my Time Machine backup to restore everything to my new machine and it was absolutely spot on, everything including Applications was exactly as my previous machine was. As I'm a new 'server' customer I'm afraid I can't comment on that, I would like to think it's a thorough as non server Mac OS X though ! I guess if you want the absolute assurance yourself, give it a go, plug a disk in and let it backup then rebuild your mini using the backup.
Mark

Too bad mini server won't boot from an external drive

It won't. Enterprise TEch support confirmed this. I bought thew new mini server to get a good value fast machine with a quad i-7.
What's the purpose of Thuderbolt if my apps and doc folders have to reside on a SATA disk?
They really should have non server version with the i7 quad.
Even better Apple should make it clear that this is the case. Even the guy in the apple store said I coud boot it form an external drive!

Yes this will all take some time for sure.
If you want to keep lion server on your current machine, then yes, that is correct. It doesnt hurt to have a few spare 500gb+ hard drives to help the long process.
See there was previous controversy with the mac mini servers with the dual cores (the one I have) because we all wanted the better processors but to not run the server version and some also wanted to be able boot from other drives. Same as you..
In non lion versions of OSX you would normally put the SL Server DVD or SL DVD into your mac and instead of installing a fresh OS, you would select utilities , then restore from time machine backup. You could also obviously use an external drive or SD card with SL or SL server installer loaded on it to install the OS or perform the restore.
That being said
I personally only know how to use a Snow leopard Server or Regular snow leopard installer DVD (or disc imaged external hard drive partition as just mentioned) to use time machine to restore an OS. I personally dont have experience with the lion disc repair for using its utilities to restore from a backup. Im sure it works the same way though when you hold option and boot from it..
If you are looking to go NON server on your OS you must have a Snow leopard retail version DVD (not leopard upgrade version) to be installed on to an external drive.
So what you would do is Set up a partitioned external hard drive and load it up with Snow leopard, upgrade it in app store to lion ($29 ) , then update it with software update, back it up to another partition using time machine, then boot from the install dvd (or disc imaged partitioned installer of SL) , go to utilities, and select restore from backup, when its asks wher eto install choose the external you want to boot from (must be partitioned using GUID partition table) and install. When you want to boot from that drive, hold option right after you power up your machine until it gives you the option of the drive you want to boot from, select it and boot.
Unfortunately like I said you will have to have a snow leopard retail installer (no longer at the apple store only online or ebay for $30) and then would have to 'upgrade' to lion in order to NOT have lion server version on a mac mini set up for server.
If lion server version is good for you then yes do what you wrote in the reply would work. My experience with server snow leopard was that it was slower than snow leopard regular and it extremely interfered with my music production even though I was not running any of its server options..
I hope this helps..

Connect Windows 2000 to Mac Mini Server

Hi all,
I just got my new mini server and trying to setup the network for local and overseas staffs to access the files in the server. I wonder if anyone can tell me how to setup on Windows 2000 and Windows vista.
We have static IP address and all our macbook pro laptops are running fine, except Windows laptops.
Looking forward to any reply. Thanks a lot.

Servers and server-oriented networks expect substantially more knowledge of the administrator. The Apple servers are among the easiest I've encountered, but they're still (far) more involved than running a client box.
You need local DNS services. Mac OS X Server expects that.
You need a server-grade firewall. With TC, you have a home-user widget with port-forwarding. A server-grade firewall typically offers programmable pass-through, (for this case) VPN end-point and various other features depending on your current and planned usage. Anti-malware and anti-spam and other defenses can be available. Free (open-source) and commercial firewall options exist.
You need a business-class tier of service with your ISP, as a residential tier can and variously will be blocked by the ISP.
Everything that's not behind a firewall or a VPN will be directly attacked. The servers I administer get attacked quite frequently, as do the external firewalls. Getting breached stinks.
My usual approach here would be a VPN from the remote box into your server-grade Firewall (which also handles NAT and some other issues), and (via the VPN) the remote client (Windows or Mac or Linux or whatever) then appears to be directly connected to your local LAN.
Reading material [private (on-LAN) DNS services|http://labs.hoffmanlabs.com/node/1436], [public (external) DNS services|http://labs.hoffmanlabs.com/node/1594], [firewalls and networking|http://labs.hoffmanlabs.com/node/275], and most definitely read the [Apple Documentation|http://www.apple.com/server/macosx/resources/documentation.html].
And while no offense is intended, it's going to be fastest to call in somebody to set this up, and as an escalation path for your organization. You probably have a business to run and customers to deal with, and networks and network security and VPN setup and such aren't something you probably want to spend your own time on; they're something you can out-source.

New Mini Server, ethernet problem

Similar Messages

Maybe you are looking for