TNG definitely not working on my libc5 system

Kurt Fitzner kfitzner at
Fri Apr 14 04:08:38 GMT 2000

I am still having problems getting TNG running at all on my libc5 system.  I
was told that I was running old binaries somewhere, but that is definitely
not the case.  I am explicitely starting up all the TNG binaries by full path.

What I am noticing is a little disturbing.  That is, when I use the command:

 ./rpcclient . -U root%

and subsequent

 createuser foo -p foo

The lights on my cable modem go crazy for a couple seconds before I get the
messages back:

 socket connect to /tmp/.smb.0/agent failed: No such file or directory 
 cli_establish_connection: failed to connect to GUARDIAN<00> (
 cli_net_use_add: connection failed
 ncacn_np_use_add: connection failed
 please use 'lsaquery' first, to ascertain the SID

This is a little disturbing, since I am not using the interface my cable
modem is attached to in my smb.conf.  I tried adding 'bind interfaces only'
and giving as an interface as well (as per the man page), but the
behavior continues.  Sending out packets on interfaces other than what is
explicitely specified is an official "bad thing" <tm>.

I really don't want broadcasts, or any other type of packet, going out on
anything except my local lan.  Is there any way to keep TNG from using my
other interfaces?


p.s.  ifconfig output and my smb.conf are as follows:

$ ifconfig
lo        Link encap:Local Loopback  
          inet addr:  Bcast:  Mask:
          RX packets:56461 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56461 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0      Link encap:Ethernet  HWaddr 00:C0:A8:4E:42:EF  
          inet addr:  Bcast:  Mask:
          RX packets:342862 errors:0 dropped:0 overruns:0 frame:0
          TX packets:408954 errors:0 dropped:0 overruns:0 carrier:0 coll:1471
          Interrupt:11 Base address:0x320 

eth1      Link encap:Ethernet  HWaddr 00:00:6E:21:35:E6  
          inet addr:  Bcast:  Mask:
          RX packets:469954 errors:0 dropped:0 overruns:0 frame:10
          TX packets:304931 errors:19 dropped:0 overruns:2 carrier:37
          Interrupt:10 Base address:0x340 

$ cat smb.conf

interfaces =
bind interfaces only = true
#debug level = 100

#NetBIOS name isn't needed if it's the same as the hostname 
netbios name = GUARDIAN
workgroup = MAINFRAME

#flat files that map Unix groups to NT type groups. 
#these files take the form unix_group = `Windows NT group'' 
domain group map = /opt/samba-tng/private/ 
domain alias map = /opt/samba-tng/private/ 

#Domain controllers use user security and we need encrypted 
#passwords (see ENCRYPTION.txt) 
security = user 
domain logons = yes 
encrypt passwords = yes 

#And in order for us to be *sure* to win browser elections 
os level = 65 
domain master = yes 
preferred master = yes 
local master = yes 

#WINS is the equivalent of DNS for NetBIOS. 
wins support = yes 
time server = yes 

#the next lines are equivalent to the various profile details 
#found in NT's User Manager 
#logon script = login.bat 
#logon drive = U: 
#logon home = \\GUARDIAN\%U
#logon path = \\GUARDIAN\profile\%U

#share all home directories 
browseable = no 
writable = yes 
comment = Users' home directories 

#set up netlogon share for system policies and login scripts 
path = /opt/samba-tng/netlogon 
writable = no 
guest ok = no 
comment = PDC netlogon share 

#the profiles share
#to create automatic subdirs for the different users
#chmod 1777 /opt/samba-tng/profile
path = /opt/samba-tng/profile
writeable = yes

#a public share 
path = /opt/samba-tng/public 
browseable = yes 
public = yes 
comment = Public share 

More information about the samba-ntdom mailing list