Samba as Primary Domain Controller for windows network
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Samba as Primary Domain Controller for windows network
Hello
I'm trying to setup my Linux server to host the profiles for my Windows clients. At the moment, all of my PCs and the linux server (which is the Primary Domain Controller) are connected through a Linksys router, which has DNS on it for resolving things like google etc. It does not resolve Internal PC names, as far as I know. I wouldn't expect it to.
I believe that i have set up my samba configuration correctly, as I followed a howto perfectly. However, when I try and add my Windows 2000 client to the domain, I get the error:
"The domain ZYZ is either invalid or does not exist"
It is the case that I need to set up my LInux server, which I have set up as the Primary DOmain Controller, to be a DNS server for the INTERNAL network?
Or, do I just set:
name resolve order = wins lmhosts hosts bcast
and run a WINS server on the Linux server?
When roaming profiles/active directory is setup on a Windows 2000 server, windows make that domian controller a DNS server.
If anyone can shed light for me, that would be great.
In addition, if you want to do both DHCP and have DNS resolving dynamic hosts' names, there is a recipe that works using ISC dhcpd and bind 9. This is not necessary, I believe [and almost certainly overkill]. However, if you'd like to see how it's done, be my guest and ask away. Note that it's a lot of trouble to set up both bind and dhcpd, so be aware that it may not be worth it.
My next problem is that when I log in with my account "hamish" (where the whole profile folder is about 150Mb) navigation becomes very slow.
For example, when I go to My Computer, it takes about 20 seconds for My Computer to be populated with the icons, including my two automtically mounted network drives.
When I access any network drive, it is unusably slow to populate the directory.
When I log in with a different user, user1, whose profile is only 10 Mb, none of these problems occur. It runs at a native speed.
My question is:
what is causeing this slowness? Is it a result of the large profile? (althou 140Mb is not actually that much), or is there something I have to alter in my smb.conf to make it cope with large profiles?
I've seen Windows 2000 choke on large profiles. I think this is mostly your client's problem.. though I'm not sure. I haven't done any research on it, so.. Google?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.