Hello all,

I'm going through every n00b's rights of passage with Samba. The specific issue that I am having is trying to get samba running just as a client app, not as a server. We have 2 windows server 2003 boxes acting as the DC and associate DC. All I need with my samba is the ability to see the other computers in the domain.

I am going through the steps found at these sites, and following instructions to the letter.

http://hr.uoregon.edu/davidrl/samba/install.html

and locally at linuxquestions

http://www.linuxquestions.org/questi...n+an+NT+domain

Here is the contents of /etc/samba/smb.conf

[global]
netbios name = Redhat01
security = domain
workgroup = GENXWIFI
log file = /var/log/samba.log
log level = 1
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192
wins support = yes
domain logons = yes
os level =99
password server = *
winbind uid = 10000-20000
winbind gid = 10000-20000

When I use the /usr/bin/testparm command to check on smb.conf, here is the result:

[root@workbox usr]# /usr/bin/testparm
Load smb config files from /etc/samba/smb.conf
Server's Role (logon server) NOT ADVISED with domain-level security
Loaded services file OK.
Server role: ROLE_DOMAIN_BDC
Press enter to see a dump of your service definitions

# Global parameters
[global]
workgroup = GENXWIFI
netbios name = REDHAT01
security = DOMAIN
log level = 1
log file = /var/log/samba.log
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192
domain logons = Yes
os level = 99
wins support = Yes
idmap uid = 10000-20000
idmap gid = 10000-20000

What confuses me about this output is the line Server's Role (logon server) and ROLE_DOMAIN_BDC. I didn't put those values in any config. When I searched for the text ROLE_DOMAIN_BDC in my /usr/sbin dir, it is found in the files winbindd, smbd, and nmbd. Of course those files are binary, and I can't edit them.

If someone can please point me in the direction of just using samba as a client into the winblows domain, I would greatly appreciate it.

Thanks,
JimBass

smb.conf has to do with samba server, which you didn't want to do.


The only packages needed for client side use of samba is samba-common and samba-client.

To use it as a client there is not much to do other than to just use it. No special configuration.
The smbclient is used to connect to a shared resource.

Thanks for the help. I had some luck simply by pulling the "domain logons = yes" line out of smb.conf. I was fighting the DC for the rights to do that, and it crashed out the entire domain. Withthat removed I was showing up in the Windows folks' Network Neighborhood, although it would ask them for a pass, then not accept any of the username/passwords that are configured on my box. When I get in to work tomorrow I'll try your 2 suggested commands, and see how those work out. Thanks again.

JimBass