It will depend on what the security protocol is that will be attempting to
bind against your 2008/2008R2 DC. Before we upgraded I contacted my vendor
got the upgrades needed for the non-Windows o/s and then built a test lab to
verify that the connections worked as expected.
If you aren't testing before your upgrade, your production network becomes
your test lab. So I strongly urge you to take the time and test, test,
test...
http://support.microsoft.com/kb/942564/en-us
--
Paul Bergson
MVP - Directory Services
MCITP - Enterprise Administrator
MCTS, MCT, MCSE, MCSA, MCP, Security +, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
http://www.pbbergs.com Twitter - @pbbergs
Please no e-mails, any questions should be posted in the NewGroups. This
posting is provided "AS IS" with no warranties and confers no rights.
"Mike55" <> wrote in message
news:F9AC18E3-856F-4E9F-B388-...
> I'm working on adding 2008 R2 DCs into my 2003 domain. I've done all the
> adprep steps and everything checks out health-wise. I'm running the 2008
> DC
> wizard and I get to the screen that talks about the "new more secure
> default
> for the security setting named 'Allow cryptography algorithms compatible
> with
> NT 4.0'" section and it worries me. We have some FreeBSD Unix machines
> that
> use SAMBA, LDAP, etc. to authenticate against AD.
>
> Will the FreeBSD/SAMBA/LDAP auth be affected by adding a 2008 R2 DC into
> the
> domain?
>
> Does it matter what the domain function level is?
>
> Thanks,
> Mike
Linear Mode
