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

I setup Server 2008 R2 running Active Directory and now Win7 clients who are members of the domain can no longer see/access our OS X File Server. Doesn't show up in Network, nor can it be accessed by \osxservername. Did I break something, or is there a way to get around this?

share|improve this question
Computers don't have eyes and brains and don't "see". Tell us what error messages you're receiving when you try to perform specific activities using the computers. – Evan Anderson Mar 15 '12 at 16:46
W7 Client: Login to Domain, go to Computer and type \\OSXserverName into the address bar and hit Enter, then "Windows can't access \\OSXserverName" with an error of "Error Code: 0x80004005 Unspecified Error". Win server08 R2 has same error, but the Macs in the office (not on domain) can still access it. – David Mar 15 '12 at 16:49

Sounds like a name resolution problem to me at first blush. Can you PING the OS X server machine by name and IP address from the computers where users are having the issue?

Could also be that domain policy has modified the NTLM vs NTLMv2 settings in the clients, too, preventing authentication from working. Anybody know if the OS X SMB server supports NTLMv2 yet?


PING works by name? How about accessing the server via a UNC with the IP address? If that works then you've definitely got a name resolution problem.


In the DNS forward lookup zone for your AD domain add an "A" record for the OS X server's name and IP address and I predict things will get a lot better for you.

share|improve this answer
Ping only works by IP. I haven't modified any domain policies other than mapped drives yet. – David Mar 15 '12 at 16:53
Ping does NOT work via name. – David Mar 15 '12 at 17:04
@David Then, definitely a name resolution issue. How are your Windows devices doing name resolution for the other systems; NetBIOS name resolution? Or DNS? – Shane Madden Mar 15 '12 at 17:42
Whatever is default, I haven't rolled out any W7 clients yet, just trying to iron the kinks out before I deploy, by testing in VirtualBox. – David Mar 15 '12 at 17:46

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.