Pablo Chamorro C.
2006-Mar-10 14:40 UTC
[Samba] samba4wins - all ok but how to use nmblookup from my PDC?
I installed samba4wins on two of my Fedora Core 3 servers (from src rpm), on one PDC (samba 3.0.21c) and on one standalone server without samba, in order to test samba4wins. I think I managed to install and to setup properly the software but it seems nmblookup is not working on the PDC samba: [user]$ nmblookup '*' querying * on 192.168.19.255 name_query failed to find name *>From any other linux, including the standalone machine nmblookup '*'works. I followed the instructions given on samba4wins-1.0.1-HOWTO.txt. On the other side, I am having similar samba4wins records both for user machines and for users! Is this ok? Please look below. Thanks Pablo Chamorro C. My setup: 1. My PDC, eth0: 192.168.19.9 ("pdc") for the PDC, and 192.168.19.109 (pdc-wins) for samba4wins: in /etc/samba/smb.conf: netbios name = pdc workgroup = group bind interfaces only = yes interfaces = 192.168.19.9 socket address = 192.168.19.255 wins server = 192.168.19.109 in /etc/samba4wins/samba4wins.conf: [globals] netbios name = pdc-wins workgroup = migrupo interfaces = 192.168.19.109 bind interfaces only = yes log level = 4 nbtd:disable_broadcast = yes 2. in the linux without samba: eth0: 192.168.19.7 ("standalone") and for samba4wins: 192.168.19.107 (standalone-wins) [globals] netbios name = standalone-wins workgroup = group interfaces = 192.168.19.107 bind interfaces only = yes log level = 4 nbtd:disable_broadcast = no 3. in the PDC /var/lib/samba4wins/private/wins_config.ldb: # returned 2 records # record 1 dn: CN=STANDALONE-WINS,CN=PARTNERS distinguishedName: CN=STANDALONE-WINS,CN=PARTNERS objectClass: wreplPartner pullInterval: 1800 pullRetryInterval: 30 pushChangeCount: 0 pushUseInform: 0 type: 0x3 address: 192.168.19.107 # record 2 dn: @BASEINFO distinguishedName: @BASEINFO sequenceNumber: 23 4. in the standalone server /var/lib/samba4wins/private/wins_config.ldb file: # returned 2 records # record 1 dn: @BASEINFO distinguishedName: @BASEINFO sequenceNumber: 6 # record 2 dn: CN=PDC-WINS,CN=PARTNERS distinguishedName: CN=PDC-WINS,CN=PARTNERS objectClass: wreplPartner pullInterval: 1800 pullRetryInterval: 30 pushChangeCount: 0 pushUseInform: 0 type: 0x3 address: 192.168.19.109 Sama4wins is generating this kind of records: # record 12 dn: name=USER,type=0x03 distinguishedName: name=USER,type=0x03 type: 0x03 name: USER objectClass: winsRecord recordType: 0 recordState: 0 nodeType: 0 isStatic: 0 expireTime: 20060313052429.0Z versionID: 17 winsOwner: 192.168.19.109 address: 192.168.19.1;winsOwner:192.168.19.109;expireTime:20060313052429.0Z; registeredBy: 192.168.19.1 -- Tel: +57 (2) 7314752/3222/2595 - Fax: +57 (2) 7310514 Carrera 31 #18-07 Parque Infantil - PO Box 1795 - Pasto
simo
2006-Mar-13 14:09 UTC
[Samba] samba4wins - all ok but how to use nmblookup from my PDC?
On Fri, 2006-03-10 at 09:07 -0500, Pablo Chamorro C. wrote:> I installed samba4wins on two of my Fedora Core 3 servers (from src rpm), > on one PDC (samba 3.0.21c) and on one standalone server without samba, in > order to test samba4wins. I think I managed to install and to setup > properly the software but it seems nmblookup is not working on the PDC > samba: > > [user]$ nmblookup '*' > querying * on 192.168.19.255 > name_query failed to find name *Are you there is no firewall software blocking answers to the request ?> >From any other linux, including the standalone machine nmblookup '*' > works. I followed the instructions given on samba4wins-1.0.1-HOWTO.txt. > > On the other side, I am having similar samba4wins records both for user > machines and for users! Is this ok? Please look below.Yes, workstations register the username with Netbios to be able, for example, to receive messages directed to a username. This is also why you should never name a workstation after the username, you may end up in conflicts. Netbios names can represent a number of things as they represent services not merely machines. In a busy network you should find user programs registering their own names sometimes too.> 2. in the linux without samba: eth0: 192.168.19.7 ("standalone") and for > samba4wins: 192.168.19.107 (standalone-wins) > > [globals] > netbios name = standalone-wins > workgroup = group > interfaces = 192.168.19.107 > bind interfaces only = yes > log level = 4 > nbtd:disable_broadcast = noIf this machine does not have samba, then you do not need to restirct samba4wins to an alias, you can just use the primary interface. The ip alias trick is used to let samba3 run it's own nmbd daemon on the same address of smbd. I'd make a network trace and see if the request goes out on the wire and if any answer returns. Simo. -- Simo Sorce Samba Team GPL Compliance Officer email: idra@samba.org http://samba.org