Add windows 7 client samba domain
Background: I am setting up a Linux box for a local accounting office. Requirements: No password authentication required for logged-in Windows users to access Samba share. As little manipulation of current Windows security policies as possible. All users who access the share should have full read and write permissions execute is NOT necessary.
What I have tried: In smb. And just about every setting I have run across. Other things of note: The Samba share IS seen by the Windows domain and is actually accessible from a Windows administrator session.
One more thing: I am very new to Samba so please bear with me. Improve this question. Add a comment. Active Oldest Votes. Is it feasible for you to set up an account for each user that will be connecting? I've never set up a Samba share inside a Windows domain, but here's a link to the Samba doc on Domain Menbership that I quoted above: Samba Domain Membership Give the doc a look, and maybe it'll help you with what you need to do.
Improve this answer. Aaron Aaron 6, 5 5 gold badges 30 30 silver badges 45 45 bronze badges. Another advantage to this approach is that you don't have increased usage of your internet pipe for updates to network time. ClearOS can reference other servers on your network and be used only for its own purposes, or ClearOS can be used as a primary location for DNS queries. Samba Directory.
In some cases it may be useful to refer ClearOS to different DNS provider for the implicit purpose of resolving a specific or several specific domains. This is recommended for Active Directory Connector and you can use this guide to assist you. While this is not required for anything related to this specific topic, it is useful to mention. This can be useful in poisoning a specific DNS host or redirecting it for other purposes. For example, if on the local domain is web server that has a public IP address that is forwarded into your domain, you will not be able to use the external address to get to it.
But by using a DNS include you can override the external lookup and provide the internal hostname to IP address designation. For Windows 7 and later you will need to make changes to the workstation. You can manually make the changes using 'regedit' or create this as a file in notepad and save it with the '.
Then, double-click to add it to the registry. Here is the code:. By setting this parameter, you tell your workstation that you want it to use NT4 style domains.
There is no security risk here other than the kerberos-layer differences intrinsic between NT4 and and it does not prohibit the workstation from joining an Windows domain or later domain. As part of the domain join process, Windows and later domains not only make a computer account for the domain but also create a DNS entry. The workstation then validates that the DNS entry resolves before allowing the workstation to join the domain.
There is no integration point in NT4 domains to DNS so this doesn't occur and as a result, the workstation will not join the domain. In our opinion, this was added to Windows domains and later in order to make management of DNS for workstations smoother. It doesn't enhance security but since it is required by default and doesn't work this way under NT4-style domains, we must disable it for the time being.
Microsoft have decided for security reasons to disable logon scripts from running in Windows 10, now preferring to use Group Policies. To re-enable logon scripts in Windows 10 you need to make some registry changes before you join the domain. At the beggining sorry for late respond but I was overloaded by work lately. I tried change you suggested in smb.
I can't belive it still not allows me to join domain. Any more ideas? Tags for this Thread join domain , opensuse Bookmarks Bookmarks Digg del. Contact an administrator to verify the account is in the domain.
If the account has been deleted unjoin, reboot, and rejoin the domain. Therefore, if I try again a second time, without deleting the already created computer account, I get a different error:.
Note that until a while ago samba wasn't configured to automatically create computer accounts. What I did whenever I wanted an XP to join was to manually create it. When I first attempted to solve the Windows 7 join problem, I setup samba to do this automatically, as this is what most people do, as I understand, and I thought that it might be related. I haven't attempted to add an XP since I made this change, so I don't know if it works, but whether it works or not, the problem remains.
Update 2: The server has a single network interface eth1 also an unused eth0 that shows up only in the kernel boot messages and two ip addresses; the main, One of the problems I recently faced was that samba was using the latter IP address. The above dump occurs when I click "OK" to join the domain , until it asks me for the username and password of a user that can join the domain. I don't know why the client is contacting the second IP address. This should resolve your issue. Sign up to join this community.
The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Windows 7 cannot join samba domain Ask Question.
Asked 9 years, 7 months ago.
0コメント