Jim, Your Samba system can participate in the network in a couple of ways: 1. As a member of a workgroup that just happens to have the same name as the NT domain. This would be roughly equivalent to a Windows 9x machine participating and serving some shares. 2. As a member of the domain (requires a machine account to be created on the PDC). This is also known as being a "member server."
The parameter in smb.conf is "workgroup = ". If you have a WINS server, use the "wins server=" parameter to register your machine with it. As I always do at this point, I strongly recommend that you take a look at the "Using Samba" book that comes with every distribution. It talks in detail about how to go about all these things, and how to troubleshoot if there are problems. Your experience with bias is certainly nothing new or unique. Just remember that this stuff does work, when done correctly. With some people that actually counts for something. Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 10:34 AM To: [EMAIL PROTECTED] Subject: Integrating Samba in a windows network I am faced with the unenviable situation of a definite M$ bias. Our network folks will not let me set up Samba as a master ANYTHING. I am not sure what to tell the network folk in order to have my samba definition on Linux participate in the local windows arena. The machine's DNS name is 'rockhopper' but I am not certain what workgroup to tell them and I am not finding anywhere in the SMB.CONF to specify what domain (even if that's needed) to be in. This was their last response to me - Basically they're not sure either. -------------------------------------------------------------- Can this live in a Windows NT network domain as a member server? LAN Services would probably not allow it to act as a domain controller within one of its domains without psychotically intensive testing. Since Windows NT uses NetBIOS as an APPC protocol, I'm guessing that your machine would need it to be part of a domain. Maybe not. Dunnofersure. As far as the DNS name is concerned, I think that we would need to add it to a WINS database unless users would access it through a TCP/IP client software package instead of their Windows Explorer. Dunnofersure on that, either. Chris -------------------------------------------------------------- If anyone has been down this road before, please let me know. -J
