search for: __samba__

...le to authenticate with the NT server, > and the log files start that:password server NT-PASSWORD-SERVER > rejected the password NT Password did not match ! Defaulting to Lanman > > > BUT this is the strange output: > > jaws:1:[samba-1.9.18p8/bin]:[455]% ./nmblookup -B gdps __SAMBA__ > Sending queries to 0.0.0.0 > 139.121.37.229 __SAMBA__<00> > 139.121.37.225 __SAMBA__<00> > 139.121.37.229 __SAMBA__<00> > 139.121.37.237 __SAMBA__<00> > 10.8.0.17 __SAMBA__<00> > 10.8.0.4 __SAMBA__<00> > 10.8.0.17 __SAMBA__<00> &gt...

...Disk Home Directories Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] Server Comment --------- ------- Workgroup Master --------- ------- RABNETWORK BEASTIE 4) works: *nmblookup -B BIGSERVER __SAMBA__ amanda@beastie:~$ nmblookup -B BEASTIE __SAMBA__ querying __SAMBA__ on 127.0.0.1 192.168.1.102 __SAMBA__<00> *5) fails:* nmblookup -B ACLIENT '*'** amanda@beastie:~$ nmblookup -B presta '*' querying * on 0.0.0.0 1...

...=[Samba 3.4.7-0.50.fc11] Server Comment --------- ------- COPPERFISH E3000 STEVE Steve's Samba Server Version 3.4.7-0.50.fc11 Workgroup Master --------- ------- WORKGROUP COPPERFISH $ nmblookup -B steve __SAMBA__ querying __SAMBA__ on 127.0.0.1 192.168.1.120 __SAMBA__<00> $ nmblookup -B Kellie-PC '*' querying * on 192.168.1.122 name_query failed to find name * I suspect that this is some kind of permissions problem on the Win7 box but the fact that the E3000 router is showing up as the workg...

Hi list. I'm new to this list, so please bear with me. I've got samba 2.2.8a on Solaris 9 (SPARC). I've run all the tests. testparm runs fine. Other tests: # nmblookup -B stage __SAMBA__ querying __SAMBA__ on 192.168.18.25 192.168.18.25 __SAMBA__<00> # # nmblookup -B 192.168.1.9 '*' querying * on 192.168.1.9 192.168.1.9 *<00> # # nmblookup -d 2 '*' added interface ip=192.168.18.25 bcast=192.168.23.255 nmask=255.255.248.0 querying * on 192.168.23.255 Got...

...AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am ADMIN_SEC and I'm trying to connect to W98 PASTOR $ nmblookup -B ADMIN_SEC __SAMBA__ querying __SAMBA__ on 127.0.0.1 192.168.1.100 __SAMBA__<00> $ nmblookup -B PASTOR '*'. querying *. on 208.69.32.137 name_query failed to find name *. Then I tried: $ nmblookup -d 2 '*'. added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0 querying *. on 1...

...cat /etc/xinetd.d/netbios-ns service netbios-ns { socket_type = dgram protocol = udp wait = yes user = root server = nmbd disable = no } Test 4: ================================================================= from //DS # nmblookup -B DS __SAMBA__ querying __SAMBA__ on 192.168.10.68 192.168.10.68 __SAMBA__<00> from //IW # nmblookup -B DS __SAMBA__ querying __SAMBA__ on 192.168.10.68 name_query failed to find name __SAMBA__<00> Test 5: ================================================================= from //DS # nmblookup -B MS...

...Admin MSOFFICE Disk C$ Disk Default share Server Comment --------- ------- Workgroup Master --------- ------- ************************************************************************** test4: nmblookup -B torvalds __SAMBA__ querying __SAMBA__ on 192.168.100.3 192.168.100.3 __SAMBA__<00> ************************************************************************** test5: nmblookup -B pubert '*' querying __SAMBA__ on 192.168.100.3 192.168.100.3 __SAMBA__<00> ****************************************...

.../12/09 22:36:31, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name *<20> with first IP 192.168.0.4 ttl=0 nb_flags= 0 to subnet 192.168.0.4 [2006/12/09 22:36:31, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name __SAMBA__<20> with first IP 192.168.0.4 ttl=0 nb_flags= 0 to subnet 192.168.0.4 [2006/12/09 22:36:31, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 192.168.0.4 ttl=0 nb_flags= 0 to subnet 192.168.0.4 [2006/12/09 22:36:31,...

Hi, I've a got kind of weird problem using nmbd. At least, I think is is weird because this problem isn't dealt with in any documentation. I got my nmbd up and running, when I issue the command 'nmblookup -U 10.0.0.1 __SAMBA__' (my IP is 10.0.0.1/255.0.0.0) I get a correct response: 'querying __SAMBA__ on 10.0.0.1 10.0.0.1 __SAMBA__<00>' But when I use a broadcast query, it doesn't work: 'nmblookup [-B 10.255.255.255] -d 10 __SAMBA': 'Initialising global parameters params.c:pm_proce...

...e done I've done ;-). The Workgroup name is SYSTEM the samba server is daemon with IP 192.168.1.1 Where does the UNICAST_SUBNET come from? Why is a _SAMBA_ netbios name added where I've never configuered this? Thanks Tom log.nmb reads as follows: add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 192.168.1.1 ttl=0 nb_flags= 0 to subnet 192.168.1.1 [2001/03/11 16:18:01, 3] nmbd/nmbd_workgroupdb.c:initiate_myworkgroup_startup(244) initiate_myworkgroup_startup: preferred master startup for workgroup SYSTEM on subnet 192.168.1.1 [2001/03/11 16:18:01, 3] nmbd/nmbd_serve...

...10:05:19, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name *<20> with first IP 192.168.0.1 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2004/02/14 10:05:19, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name __SAMBA__<20> with first IP 192.168.0.1 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2004/02/14 10:05:19, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(236) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 192.168.0.1 ttl=0 nb_flags=60 to subnet WINS_SERVER_SUBNET [2004/02/1...

...go to multiple configurations, I cannot see the 'server2secured' shares. When I put an entry into my local hosts file for 'server2secured', I am able to obtain shares but it is the shares for 'server2' not for 'server2secured'! When doing 'nmblookup -B server2 __SAMBA__', I receive: Sending queries to 1.2.3.4 1.2.3.4 __SAMBA__<00> When doing 'nmblookup -B server2secured __SAMBA__', I receive: Sending queries to 0.0.0.0 1.2.3.4 __SAMBA__<00> When executing "smbclient '\\server2\share'", I receive the smb> pro...

I've got Samba 2.2.2 installed and running fine on one of our servers (RS/6000 AIX 4.3.3 and using NT authentication), however, when I do Test #4 (from docs/textdocs/DIAGNOSIS.txt) it looks like this: npssrv{root}#nmblookup -B npssrv _SAMBA_ querying _SAMBA_ on 173.148.200.113 name_query failed to find name _SAMBA_ The test said I should get back the IP address of our samba server. I got

...60 to subnet 192.168.1.200 [2003/08/28 09:51:04, 3] nmbd/nmbd_namelistdb.c:(236) add_name_to_subnet: Added netbios name *<20> with first IP 192.168.1.200 ttl=0 nb_flags =60 to subnet 192.168.1.200 [2003/08/28 09:51:04, 3] nmbd/nmbd_namelistdb.c:(236) add_name_to_subnet: Added netbios name __SAMBA__<20> with first IP 192.168.1.200 ttl=0 nb_flags=60 to subnet 192.168.1.200 [2003/08/28 09:51:04, 3] nmbd/nmbd_namelistdb.c:(236) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 192.168.1.200 ttl=0 nb_flags=60 to subnet 192.168.1.200 [2003/08/28 09:51:04, 0] lib/ut...

...ng as a WINS server (199.170.224.6 as specified as the 'wins server'). Anyone have any ideas? Do I need to have the WINS server be the domain master browser instead of Samba (BROWSING.txt seems to clearly indicate that Samba can be the Domain Master Browser). % nmblookup -d 5 -B lorax __SAMBA__ Initialising global parameters Processing configuration file "/usr/local/samba/lib/smb.conf" Processing section "[global]" doing parameter browseable = yes doing parameter domain logons = yes doing parameter guest account = nobody doing parameter load printers = yes doing parame...

...subunit output from samba4.blackbox.samba3dump WARNING: allowing empty subunit output from samba4.blackbox.upgrade PROVISIONING S3DC...CREATE TEST ENVIRONMENT IN './st/s3dc'...DONE STARTING NMBD...DONE STARTING WINBINDD...DONE STARTING SMBD...DONE delaying for nbt name registration querying __SAMBA__ on 127.0.0.2 127.0.0.2 __SAMBA__<00> 127.0.0.2 __SAMBA__<00> querying __SAMBA__ on 127.255.255.255 127.0.0.2 __SAMBA__<00> querying LOCALS3DC2 on 127.0.0.2 127.0.0.2 LOCALS3DC2<00> 127.0.0.2 LOCALS3DC2<00> wait for smbd Domain=[SAMBA-TEST] OS=[Unix] Server=[Samba 4.0.0...

.../09/02 14:24:37, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(250) add_name_to_subnet: Added netbios name *<20> with first IP 172.60.1.107 ttl=0 nb_flags= 0 to subnet 172.60.1.107 [1999/09/02 14:24:37, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(250) add_name_to_subnet: Added netbios name __SAMBA__<20> with first IP 172.60.1.107 ttl=0 nb_flags= 0 to subnet 172.60.1.107 [1999/09/02 14:24:37, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(250) add_name_to_subnet: Added netbios name __SAMBA__<00> with first IP 172.60.1.107 ttl=0 nb_flags= 0 to subnet 172.60.1.107 [1999/09/02 14:24:3...

...some test results and my smb.conf follows. Thanks in advance for the help! * nslookup and ping work in both directions * #smbclient //fileserver/test -U<user> Password: Domain=[OUR_ADM] OS=[Unix] Server=[Samba 3.0.8] smb: \> --> I can browse the share * #nmblookup -B fileserver1 __SAMBA__ added interface ip=155.2.196.251 bcast=152.2.255.255 nmask=255.255.0.0 querying __SAMBA__ on 127.0.0.1 Got a positive name query response from 127.0.0.1 ( 155.2.196.251 ) 155.2.196.251 __SAMBA__<00> * #nmblookup -B our219.our.xxx.com '*' added interface ip=155.2.196.251 bcast=155.2.2...

...] nmbd/nmbd_namelistdb.c:add_name_to_subnet(245) add_name_to_subnet: Added netbios name *<20> with first IP 192.168.0.2 ttl=0 nb_flags= 0 to subnet 192.168.0.2 [2003/01/22 20:55:37, 10] nmbd/nmbd_subnetdb.c:namelist_entry_compare(74) nmbd_subnetdb:namelist_entry_compare() 1 == memcmp( "__SAMBA__<20>", "*<20>", 88 ) [2003/01/22 20:55:37, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(245) add_name_to_subnet: Added netbios name __SAMBA__<20> with first IP 192.168.0.2 ttl=0 nb_flags= 0 to subnet 192.168.0.2 [2003/01/22 20:55:37, 10] nmbd/nmbd_subnetdb.c:nameli...

...Server Comment --------- ------- PURSE Samba Server Workgroup Master --------- ------- MYGROUP PURSE Test 4: seems OK [root@purse samba]# nmblookup -B PURSE __SAMBA__ querying __SAMBA__ on 192.168.1.10 192.168.1.10 __SAMBA__<00> Test 5: doesn't work [root@purse samba]# nmblookup -B FAX '*' querying * on 192.168.1.7 name_query failed to find name * Test 6: doesn't exactly work [root@purse samba]# nmblookup -d 2 '*...