[Samba] Problems in SAMBA 3.3 to 4.0 migration
soonerdew at gmail.com
Sun Feb 22 18:30:27 MST 2015
Out of curiosity based on your last reply, I did a bit of snooping about the
RequireStrongKey behavior and found what I think is precisely the situation
that drove this problem for me, discussed at length between the Samba dev
team and some MS engineers some years ago:
If I read this thread correctly, there was some issue just prior to the 3.4
release way back when about how Samba and Windows 7 betas were exchanging
protocol negotiation information, and this very issue (RSK) was central to
the discussion. Under 3.3.4, RSK=0 implied a 64-bit protocol negotiation key
and worked for Win7 clients. The fix for the errant negotiation flags
exchange led to a release of Samba 3.4 that broke existing Win7 clients when
upgraded from 3.3.4 environments.
This matches my situation almost perfectly, because my PDC was Samba 3.3.4
when this project of mine started. I migrated directly to 3.6.24 in the
hopes of solving an unrelated library incompatibility issue. By the time 3.6
was released, it was well-established that RSK should be 1 for Win7 clients,
and mine weren't, so for my situation the mere installation of 3.6.24
introduced this situation for me. That explains (at least I think it does :)
) why setting RSK=1 fixed the problem.
View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4681265.html
Sent from the Samba - General mailing list archive at Nabble.com.
More information about the samba