[Samba] Samba 3.5.6 with Win7 failure (XP works)
jblaine at kickflop.net
Tue Jan 4 14:59:40 MST 2011
On 1/4/2011 4:35 PM, Gaiseric Vandal wrote:
> this may be of help
Thanks Gaiseric. FWIW, I *did* look at the wiki first, but
completely ignored the "Developer" section where this is
linked from. IMO, it is not in the right section :)
At any rate, my problem isn't related to joining a Win7
box to a Samba-served domain, as far as I can tell. I
am having trouble accessing a Samba share from Windows 7.
I tried the recommended registry modifications from the
wiki and rebooted. No luck.
I can get things to work if I disable Communications Signing
on the win7 box. This is not acceptable to our corporate
information security folks though.
That at least pinpoints the problem. Now I just need to get
Samba to accept communications signing from the client.
I don't see that I am doing anything wrong.
client signing = mandatory
> On 01/04/2011 04:32 PM, Jeff Blaine wrote:
>> Hi all,
>> We're testing 3.5.6 as an upgrade to our old 3.0.x instance.
>> Our XP boxes can see our Samba 3.5.6 shares fine.
>> Our Win7 boxes cannot.
>> "The specified network name is no longer available."
>> Relevant config portion is as follows:
>> log level = 20
>> workgroup = OURCOMP
>> security = ads
>> encrypt passwords = yes
>> realm = OURCOMP.ORG
>> password server = DC1.OURCOMP.ORG
>> client signing = mandatory
>> I've also tried "client signing = auto" to no avail.
>> Thanks for ANY advice!
More information about the samba