Unable to join domain

Hey Morphaniel, can you post your smb.conf file?

My log isn't showing any erors anymore, but lots of fail connects...with netlogon and "getpeername failed. Error was Transport endpoint is not connected"

I'm thinking now it's something I may be missing in my smb.conf file...

I googled the getpeername failed error and it said I should add "smb ports=139" to my smb.conf file....

Was curious what you had for your global section and netlogon sections...

Thanks!

BOOOYAAAA!!!! IT WORKS!!!!

I read back though this thread:
Nabble - Samba - General - Windows 7 RC
...and updates to it confirmed it was a DNS Suffix issue....!

These are my settings...

In the registry I have...
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
“DomainCompatibilityMode”=dword:00000001
“DNSNameResolutionRequired”=dword:00000000

And....
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters]
“RequireSignOrSeal”=dword:00000001
“RequireStrongKey”=dword:00000001

On the end user's PC, I have the DNS of the PDC as #1 then my Primary DNS as my #2

AND as the "DNS suffix for this connection:" I have my domain... domain.com ...as suggested in the thread link I provided. It says to make this change in the registry...but editing it here is sufficient.

And under the WINS tab I have the PDC again, and "Enable NetBIOS over TCP" radio checked.

logged off, and logged right into the DC user! WAMMO!! LOL

In retrospect, I don't think the WINS info is needed, nor do I think the registry netlogon perameters are needed either....but I'm not going to mess with it anymore cause IT WORKS!!! LOL

FYI - on the server side, I'm running 3.4 the latest samba. The logs SHOW THE SAME ERRORS!!!

So as the other thread said the issue is with the DNS Suffix on the windows 7 side....FIX IT MICROSOFT!!!

LOL

Thanks everyone for your input and patience!

Nodoze what build of windows are you running? 32 or 64? thanks and congrats on figuring it out on your own, and thanks for posting the answers.

Ken

UPDATE!!!

OK, simply just adding the domain.com into the DNS Suffix does not work...
after rebooting, you're once again unable to login to the DC user.

Dispite the entry being there, within the registry it DOES NOT RETAIN THE INFO!!!!!

The registry changed suggested in the thread I linked:

; [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\System\DNSClient]
; Enforce DNS suffix
; It seems this is not necessary - see below
; "NV PrimaryDnsSuffix"="domain.local"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]
; Overwrite DNS domain. Usually the domain is supposed to be propagated automatically
; when joining the domain. But with Samba this does not work (yet).
"NV Domain"="domain.local"

Actually DO NOT exisit in Win7 RTM, probably got changed...

So I instead changed it in...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\ Then click the current ACTIVE interface with the {lettersnumbers}...it should have a lot of entries... look for Domain, and modify this entry as your domain.com

Note: there are other 'domain' entries for adapters, but you don't need to change the other ones... it is JUST the one I listed above that carries the DNS Suffix info. process of elimination/trial and error...hehe

I rebooted and was able to login to the domain user...

Yes, Windows RTM...incase you didn't catch it above Ken hehe

I'm SO happy!!!

Thanks everyone! I hope what I've learned helps everyone!

ok, since my last post I've had mixed results with the settings made to connect windows 7 with a domain controller.

I was curious if anyone has seen anything new about Microsoft's support of samba/ldap/domain controller....?

I think it's ridiculous the extent needed to go to have compatibility...

NoDoze said:

ok, since my last post I've had mixed results with the settings made to connect windows 7 with a domain controller.

I was curious if anyone has seen anything new about Microsoft's support of samba/ldap/domain controller....?

I think it's ridiculous the extent needed to go to have compatibility...

Nodoze

What version of windows do you have? (pro, ultiimate, enterprize, etc)

ken

NoDoze,

Re Your comment below

"This update? Download details: Update for Windows 7 Release Candidate for x64-based Systems (KB972407) Date Published: 8/24/2009...only applies to 64bit [COLOR=#0072bc !important][COLOR=#0072bc !important]systems[/COLOR][/COLOR]...and doesn't make much sense on how that would influence a domain controller....? I'm running 32bit... "

The KB article DETECTS WHICH VERSION of Windows you are running and gives slightly different versions of the KB article. Spooky, huh?!

I have yet to try a detailed test as it is so long-winded, but it appears a combination of the Local Policy Security Options and the 4 Regedits suggested do actually fix the problem which is not just confined to Sambe environments - mine is plain Windows (Server 2000).

Thanx to all those who contributed to a finally successful joining to the domain. Note some of these fixes (if not all) might also apply to Vista (NT6.0) which is hardly surprising as Windows 7 is not Windows 7 at all, it is a service pack or upgrade to Vista (NT6.0) actually version NT 6.1. Checkout Win Explorer > Help > About.

Ken

What version of windows do you have? (pro, ultiimate, enterprize, etc)

I personally have ultimate, but have tried it with both professional and ultimate RTM versions...AND and an official Win7 Ultimate version.

PeterM42

Install this update to resolve an issue in which there is loss of access to shared data on a computer departing a homegroup or when joined to a homegroup and upgrading to a more recent build of Windows 7. After you install this update, you will have to restart your system.

I believe their use of "homegroup" is VERY vague. But for a computer to "leave" or "join" would require a "check" with the domain controller. And a "loss of access" could also be said for the inability to access or logon to a domain controller. Again, vague...but an update that can't hurt!

Windows 7 at all, it is a service pack or upgrade to Vista (NT6.0) actually version NT 6.1. Checkout Win Explorer > Help > About.

I'm not sure how you come to this conclusion...? IN Win 7 there is no explorer>help>about...How did you get there...? Windows 7 is a completely new build from the ground up...which is why it's NOTHING like Vista!

Ref quote: "Windows 7 is a completely new build from the ground up...which is why it's NOTHING like Vista!"

Er..... I think if you look a BIT MORE CLOSELY not only will you find a LOT of Vista (NT 6.0) in Windows 7 (NT 6.1), you will find quite a bit of XP (NT 5.1), Windows 2000 (NT 5.0) and even a fair bit of NT 4 and, of course, LANManager. Many years ago I told Phil Cross when he was interviewed for his job at Microsoft, that they should make more of LANManager. (He was required to give a presentation on it for his interview).

It may have been a coincidence, but it is now the basis of "Windows Networking".

Windows 7 may be a new "build", but during development, Microsoft do not less than one rebuild every day. Help > About shows the build number. Released versions are usually numbered in the thousands. Microsoft do not just throw away all their previous work, they build on what has gone before, regardless of the product marketing name. Everyone does in this arena.

I have windows 7 Pro SP1 and windows 2003 server with domain. I am having the same problem and unable to log on to domain. I can however access the server and open its files that are shared.
I tried some of the registry editing on windows 7 suggested above but unable to log on. Tried to change LAN Manager Authentication Level and it is set to SEND NTLM and it is grayed out, thus unable to change it. I am the administrator of both PCs.
This is a local domain with IP addresses being given by my ISP.
Also unable to connect to XP Pro PC which is loged onto domain and Unable to see the PC in the network folder. When log of the domain able to access this XP Pro PC. which is why I want to connect my windows 7 to the domain.
Appreciate any input.