Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Windows pc can go to http://servername:8085 and get to the site fine The Macs go to the same page and get a time out error

DNS on all machines point to the DC at that branch, the second DNS entry points to the DC at the main branch.

Any ideas what could be going wrong?

share|improve this question
up vote 5 down vote accepted

You have to add your AD domain as a Domain Suffix/Search Domain on the MACs. With this, every time you don't supply a Fully Quallified Domain Name but only a Hostname, such as in your example, MAC OS will add the suffix to it.

For example if your domain is EXAMPLE.LOCAL, then http://servername:8085 becomes http://servername.example.local:8085 and MAC will be able to resolve it fine. Windows clients do this automatically when joined to an AD Domain and that's why your windows machines work fine.

If I remember correctly the setting is at Apple > System Preferences > Network > Ethernet (or any adapter you use) > Advanced

There you should find a setting for Search Domain. Add your AD domain there, i.e. EXAMPLE.LOCAL.

share|improve this answer
thanks so much for the tip. I never have to work with macs so when one of these odd problems comes up its hard to even troubleshoot. I added the domain and it is working fine now. – evolvd May 19 '11 at 19:30
@evolvd You're welcome. Also keep in mind that you may face the same problem with Linux clients or Windows ones that belong to no Domain at all or to a different one than the server. The solution on all cases is the same. – AlexTsr May 19 '11 at 19:39

Couple things. First off, is the DNS resolving properly? Try pinging from the Mac.

I know Apple's mDNS can kick in if your FQDN ends with '.local', which was a suggestion for many Microsoft internal domain names. And mDNS probably won't work. So that could cause you some issues.

Otherwise, I'd recommend using tcpdump on the Mac. Verify it's sending packets out on that port, see if it's getting a response, or even an error code from the server.

share|improve this answer
with over 2,000 rep, you should know better than to add a signature line to your posts. Please give the FAQ the once over. – Ben Pilbrow May 19 '11 at 19:03
Yeah, I'm aware. Probably something I'll keep doing, unless I see significant complaints. Consider it some small bit of counterculture. – Christopher Karel May 19 '11 at 19:16
And that is totally the wrong attitude.... – Ben Pilbrow May 19 '11 at 19:19
And there we'll agree to disagree. C'est la vie. – Christopher Karel May 19 '11 at 19:21 it's not counter culture, all it does is clutter the site. – Zypher May 19 '11 at 19:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.