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.
Originally posted by tuantran sewer_monkey,
when you setup smb.conf file, I look at the line
................................................................
domain logons = yes (or domain logon = yes no "S")
.................................................................
It tell me that ALL WINDOWS users must logon to this server (Linux box), isn't it? If YES, DO we need to do anything else with the Linux box or we ONLY need to edit smb.conf file to make it works like domain logon server for WINDOWs users? I have no problem with SAMBA at workgroup mode but don't know how to make it works like domain server. IF you have time, please drop me few lines to help me out. Thank you.
No, if you set up the server as a PDC, you certainly don't have to log on to it (as a domain member) in order to access the shares. You can still have a Windoze computer browse for the Linux box in the workgroup (in my case the workgroup and the NT domain name is "HOME_NET", defined by the line "workgroup = HOME_NET" in my smb.conf).
In order to make your Windoze clients log on to the NT domain, you have to:
Properly configure SAMBA as a PDC (this includes creating UNIX and SAMBA accounts for each client machine, a.k.a. "machine accounts").
Configure the client workstations and make sure they join your NT domain.
Apply registry patches for compatibility with SAMBA, if necessary. For example, you need to patch Windoze 2000 and XP workstations before they can work successfully with SAMBA acting as a PDC. These registry (.reg) files are usually in /usr/share/doc/samba-x.x.x/docs/Registry, where "x.x.x" is your SAMBA version. Make sure you convert them to DOS format before applying them!
For more info check out the SAMBA HowTo collection here.
Last edited by sewer_monkey; 06-15-2002 at 07:48 PM.
Herm I have a problem with LinNeighborhood.. It try to MOUNT the shared drive to a path using smbmount (or a command like this) but I don't have this command (progs) in my samba/bin....
How can I enable this? I suppose it's an option I have to enable at compile time but I don't found wich one in the read me files...
I use xSMBrower as the GUI interface. This does not setup Samba, it allows you to connect to the Windows computer. You can find it easily with a web search. After install you will have a script, but when you click on the script, you will find that you are reading the script, not executing it. Make a "link to application" to the script and click on that.
Linux and Windows handle the shares differently. To access linux from windows, you have to first set up a user on linux that is the same "name" as your Windows Networks login name. Then, when the Windows Network tries to log in, it will be logging to that user account on Linux.
Going the other direction, you can set a password on your shared resources (good idea) but then you will have to enter that password when you log into the Windows computer. Note on this -- xSMBrowser unfortunately saves the password in an unencrypted file for login purposes. Therefore, I always type the password.
You also have to import the password user list into smbpasswrd. I forget the specfics on this, but Windows can't log into Linux until you accomplish this.
Logging into Windows from Linux is fairly easy with xSMBrowser if your Samba client is running. If you don't have a browse server on the network (a waste of resources for one or two computers), you make a "favorites" entry and identify the other computer by IP. You can then browse to it. I have found that the "mount" command won't mount the drive for some reason, but the "explore" command will.
Check this out for details on creating machine accounts and what they're for. I also suggest you print this document and/or keep it handy. It's very useful. In fact, I learned 70% of what I know about SAMBA from this document (the SAMBA HOWTO Collection).
Note that XP boxes will refuse to log in to a pre-made machine account. You'll have to create a root account on the SAMBA server (smbpasswd -a root), and the SAMBA password should be different than your real UNIX root's password for security. When you ask XP to join your domain, it will ask you for an admin account on the PDC. Use the root account you just created. When done, disable the SAMBA root account, or delete it. See the man page for smbpassword for an explanation on how to do this.
The registry patches (.reg files, for use with the Windoze Registry Editor, you know, regedit.exe) are in /usr/share/doc/samba-x.x.x/docs/Registry/, where "x.x.x" is your SAMBA version. Make sure you convert the file into DOS format before applying the patch (the line endings). Open the patch file in Notepad on Windoze before applying it. If it looks messed up, correct it and then apply. You can use metapad to do this conversion automatically.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.