New
#41
Lets face it Windows 7 is a dead duck - in the corporate environment, this sort of problem is totally unacceptable.
I'm going back to XP.
Lets face it Windows 7 is a dead duck - in the corporate environment, this sort of problem is totally unacceptable.
I'm going back to XP.
What a depressing read first thing in the morning...Go back to XP!?!
....sigh....
...I haven't given up yet!!!
OK. My RTM new build machine works fine and is still logging in and out of my Samba domain. The spelling mistake was with the 'RequireSignOrSeal' key - I originally wrote 'RequireSignOnSeal'.
The Internet reports that NoDoze's problem occurs if you have upgraded to Samba 3.3.6 for Win7 support - 3.3.4 is required until the Samba team release official support. Maybe you should double check 'smbstatus' as superuser just once more?
You shouldn't need to reboot after making registry changes but, of course, it doesn't hurt (and MS have supposedly made Win7 the fastest rebooter yet
Last edited by Morphaniel; 30 Aug 2009 at 08:47. Reason: ...messed up again...
ok....uhmmmm...Hmmmm....
I fixed the spelling error... rebooted....tried logging in, same error....
BUT...when looking at the DC samba server logs...NO ERROR listed!?!?!
Just the VERY last line says:
It all looks good, but why now is it failing...? What kinda error is that!?!Server exit (failed to receive smb request)
LOL...when I have more time I'll look into it...
Anyone in here have any insight...?
Hmmm....I'm puzzled...
I have the EXACT same setting as you, but still am getting the trust error...
However, I am running samba 3.4....so maybe downgrading it back to 3.3.4 is the answer....?
But then again, I've done SO many tweaks to the security policies, I'm affraid I've made a change somewhere that's preventing it from working....is there a way to reset the security policies back to default so I could start from scratch again?
Thanks.
I haven't had time to try this, but this is what I was told.
If some one tests this before I do post the results.<fn'gd> ismell: you need to take either the latest 3.3.x release or 3.4.0.
<fn'gd> ismell: then you still need to modify 2 registry keys (do *NOT* modify the netlogon registry keys)
<ismell> ohh
<ismell> the SignOrSeal ones ?
<fn'gd> ismell: yep, do please not modify them.
Have a read of Microsoft's KB article KB972407.
There was a WinDOZE 7 update yesterday which seems to address this issue.
Not sure if this is "the cure" as I had already somehow managed to get my WinDOZE 7 machine on the domain (thanks to all the other posts, gawd only knows which fix sorted it!).
There were quite a few updates, so probably worth a go.
This update? Download details: Update for Windows 7 Release Candidate for x64-based Systems (KB972407) Date Published: 8/24/2009...only applies to 64bit systems...and doesn't make much sense on how that would influence a domain controller....? I'm running 32bit...