Than that is an Apple fault. Best practice has been around since the days of unix/linux servers to use .local for many servers, so they should really have known that before making bonjour use it!
For reference our domain is not .local either, the hardware seems to be fine and the mac mini still runs like a 486. 10.whatever.3 hosed it completely and as its a server I am not keen on rebuilding the whole thing just because Apple finally got around to releasing a hotfix. It is still slow as anything under a different user and my old Pentium M (installed to Windows 7) tablet outperforms it for web browsing.
@seawolf As to the strong EM field, maybe I do, the macs in the library seem to be alright but this mac mini and these ipads are just junk. Apple is zero help and their devices couldn't provide enough useful feedback to track down anything. Just because it does not generate an error doent mean that its working, just that it is not bothing to tell you anything useful as that might confuse someone somewhere. Also no error means they can just blame everything else with no real proof.
As someone else said, possibly on a different thread, their experience turned to hell when they put ios 7.11 on as it suddenly needed to phone home to apple to connect to wireless, no internet, no wireless. The response from someone to this was that obviously everyone else was doing it wrong and they should just let Apple access whatever it wanted. This non-standard behaviour broke stuff for no good reason and then the blame is shifted to the victims by the bully. A windows machine may try a DNS lookup to see if it can get net but won't disable the connection if it can't.
This is yet more pointless idiocy just to make things harder despite their just works façade. If they could just stop being toolbags for a few seconds each year it would be lovely.
Last edited by SYNACK; 6th June 2014 at 05:27 PM.
Here's but one article as to why. Just because everybody and their uninformed brother does something doesn't make it a well thought out plan.
Why you shouldn't use .local in your Active Directory domain name.
Zero-configuration networking - Wikipedia, the free encyclopedia
Microsoft has never been great help in my experience either, but that doesn't stop most people. Macs do provide quite a lot of useful feedback in the log files, but of course you have know what you are looking at (console logs, safari debugging mode, etc). This applies more to Macs than iPads, which are a bit tight lipped about what's going on under the hood as a result of the sand boxing, etc.Apple is zero help and their devices couldn't provide enough useful feedback to track down anything.
You know, I run into issues with Windows servers and clients (and other people's software) on a regular basis, but I don't feel the need to damn Microsoft to oblivion every time something stuffs up (sometimes Windows stuffs up quite majestically). It is quite interesting to watch the meltdowns occurring from the cheese being moved.
That article is correct for single named like server.local however some companies and professionals who have been dealing with servers since the early 80s (before I was born) using Unix and DOS did use server.company.local and have done since. I worked in an environment (IBM in London) where a small handful of these legacy servers are running still due to some old legacy system still in place and work seamlessly with other Unix/Linux/Nt based servers.
Hell IBM, Intel and Novell all did manuals (old school ring binders which were as thick as my palm) which said it was best to use the .Local domains. Many have since said if doing single side ones don't use it but if doing more then it's best practice. I may even have one of these manuals at my mums. When I go round on Sunday I'll have a hunt for it.
I'm starting to get the impression that Synack really really doesn't like iPads
There are currently 1 users browsing this thread. (0 members and 1 guests)