Uh yeah, it's the "netbios name" tag that goes in your [global] section. In addition to that you have have "netbios aliases" where you have have your machine show up on your SMB network with more than one name. I usually have 2 or three names for each of my *NIX Samba servers.
e.g.
Take what you want out of the above but it is an example of one from one of my Samba servers (changed the domain and machine names for the example). This example would make it appear that there are 3 NT servers on your network with the names LINUXSRV, WINPRINT, and DEVELOP.
In this example Samba is set up to emulate an NT server that is a Member of an NT domain. Authentication is done against an NT PDC just like an actual domain member server does. I can use the NT domain groups and IDs in applying my access in both Samba and on local file permissions. But the key parts you were interested in are "netbios name" and "netbios aliases".
Couple more important tags if you are in an NT domain environment and use WINS for both netbios resolution and for DNS (if you use MSDNS and have have it configured to also resolve WINS addresses) are the "wins server" tags and "password server". When Samba starts it will insert appropriate WINS records to the "wins server" machine. And password authentication will be done against the PDC listed in the "password server" tag (you can put more than one server in the list separated by spaces if you also want to add the BDCs). I assume you understand how to create the actual Samba services (sections outside of the [global] section).
Now by far the best and most accurate graphical configuration utility is the one that comes with Samba. It's called "swat". It would be very helpful for you to get swat installed (if it is not already) and configured. Once you install and configure it point your browser to your Samba server on port 901. That would be
http://mysambaserver:901Click on the links next to each field for an accurate description of each tag.
I only have one problem with swat (but one that I can easily fix) and that is if you use NT Domain groups in your Samba access permissions. You need to use quotes (") in your domain groups if your domain group has a space contained in it's name as you will see in my example above. Well swat does't like having quotes as it screws up the field where you use the quote.
So I installed the Samba source RPM and hacked the "swat.c" file to correct this problem (just changed a " to a ' in 4 places), recompiled swat and replaced the swat binary with the new one. However, if you don't use NT domain groups in your fields you should never run across this issue. Don't know why they still haven't fixed it. Unless there is a way to handle domain groups containing spaces other than using double quotes. I've tried several ways and the quotes are the only way I have found that works...
[ September 12, 2002: Message edited by: void main ]
