After deciding to go in at the deep end with Windows 7 I have struggling to get the Lappy to see and authenticate into an OS X Server (Leopard 10.5) OpenDirectory environment.
I could go into the network pane and the server was visible, double click and an error would pop up “0×80070035 Network Path not found” Obviously it was found – the icon is clearly sat there!
I messed around with the Samba setting on OS X Server, this had to be done at the command line because Apple don’t do UI’s for complex tasks. If they can’t make it look pretty then it’s “screw you dude your an your own, open Terminal”.
It didn’t work.
I messed around with the network settings on Windows 7. Turn IP6 off, tweak this, fiddle with that. Turn IP6 back on. Is the OS X box a WINS server? no! why not? Should it be? Could that be the problem, spend a while pissing around with that idea.
It didn’t work.
Check that DNS was working on OS X Server. Apparently if anything isn’t working on OS X Server it’s a problem with DNS.
DNS was fine.
Authentication, hmm, authentication, wait a minute AUTHENTICATION! What about OpenDirectory and Kerberos?
Nope and Nope!
GOOGLE GOOGLE GOOGLE!
Now ok, the first path a Google led me down was bogus, it wasn’t a Firewall/Router issue on either machine, although that did look promising at the start. The actual solution took a bit of digging, it was a know problem for Vista but Windows 7 has added an extra sting in the tail.
It turns out that Vista, by default, will only use NTLMv2 for authentication. OS X Leopard’s version of Samba doesn’t support this protocol. The fix is slightly different depending on your version of Windows.
NOTE: This downgrades Vista and Widows 7 security level when talking to Samba.
Vista Business & Ultimate
Windows 7
With Windows 7 Microsoft have increases the baseline security level even further by default, so…
Vista Home & Home Premium
Neither of these versions of windows have the Local Security Policy snap-in, so we need to take a trip into the registry.
NOTE: All the standard warnings apply: Backup your registry, be very careful, the world may end if you do something wrong, it defiantly isn’t my fault if you hose your system – It works on my machine.
A few versions of what I searched for to hopefully make this easy to find.
Let’s not have MS bashing please, you know, “MS are just spitting their dummy out and making it hard to talk to Macs…”, “Why haven’t MS made this easier…”, or anything with dollar sign in it.
NTLMv2 is an inherently more secure protocol and the blame here falls squarely on Apple inc. for not supporting it. It took a fair bit of digging around to find the solution, and it was, in the main, Microsoft staff and Vista users who supplied the information. I honestly don’t know if the Apple Support site talks about the problem or offers a solution, mainly because the site is a joke, search results are non-existent or totally irrelevant. Its time you sorted your stall out Apple Chaps.
OS X Server has Kerberos & NTMLv2 authentication for Samba. Looking at a server right now and that is the first setting in Authentication.
Chris – That’s true. The point of the article is that NTLMv2 support for OS X Server is horribly, horribly broken. The only way to get Vista to authenticate to OS X Server using NTLM is to dial it back as described. It still doesn’t work as of 10.5.8. Hopefully it’ll be fixed in 10.6, because right now it’s embarrassing to have to explain to windows-centric clients that the reason they can’t connect to the network is because Apple hasn’t fixed their stuff…
I’m happy I located this site, I couldnt obtain any knowledge on this subject matter prior to. Also run a site and if you wish to ever interested in doing a bit of guest writing for me if possible feel free to let me know, im always look for people to check out my blog. Please stop by and leave a comment sometime!