search for: name_query

...from 11/24/2001... user running NT 4.0 SP6a the problem: I have a user that cannot print - She can add the printer but can't print. log for that machine shows the following: ... normal looking connections to obtain drivers - all look OK - no complaints.. .. then this - libsmb/namequery.c:name_query(415) Got a positive name query response from 10.1.1.111 ( 10.8.40.97 ) lib/util_sock.c:open_socket_out(898) error connecting to 10.8.40.97:445 (Connection refused) libsmb/namequery.c:name_query(415) Got a positive name query response from 10.1.1.111 ( 10.8.40.97 ) lib/util_sock.c:open_socket_...

...I am hoping someone can help me.... I am trying to configure my samba...and the problem is the following: When I use nmblookup with -B option and Broadcast address it is impossible to find my samba server (named prova) that is: # nmblookup -B 10.254.14.127 prova querying prova on 10.254.14.127 name_query failed to find name prova If I do the same lookin up to another machine different from my samba server, then it is ok: # nmblookup -B 10.254.14.127 my_win_client querying my_win_client on 10.254.14.127 10.254.14.94 my_win_client<00> Would some body help me ????

...gister.php> Authname "xxx Account" AuthType Basic Auth_SMB_Server NL-WOE-BDC01 Auth_SMB_Server NL-AMV-BDC01 Auth_SMB_Domain xxx require valid-user </Files> logfile: [2002/10/07 14:02:01, 2] libsmb/namequery.c:name_query(421) Got a positive name query response from 10.16.127.65 ( 10.16.127.64 10.20.191.65 10.17.63.65 10.16.191.65 10.19.127.65 10.18.191.65 10.16.127.65 ) [2002/10/07 14:02:01, 2] libsmb/namequery.c:name_query(421) Got a positive name query response from 10.16.127.65 ( 10.16.191.65 ) [2002/10/07 1...

...as connect to a share while on the Linux server - "nmblookup -U 127.0.0.1 __SAMBA__" works fine, as does the same command with FIZZLEBOX - "nbtstat -n" on XP lists both STUDIO and FIZZLE - This is where it goes wrong: "nmblookup -B 10.0.1.255 fizzlebox" returns "name_query failed to find name fizzlebox"; same happens when querying with "studio" - "nbtstat -A 10.0.1.201" on XP returns "Host not found" Also on the Linux box: - All users and machines have been added, passworded, and smbpassworded - Read, write, execute permissions ha...

...mote browse sync = 10.10.10.1 wins support = yes security = user encrypt passwords = yes domain logons = Yes os level = 69 preferred master =no domain master = no ... ------------------------------- The BDC is unable to find the Domain Master Browser nmblookup -U venise -R 'DOMAIN#1B' ... name_query failed to find name domain#1b nmblookup -U BDC -S PDC name_query failed to find name PDC log.nmbd ------------------------------- [2008/11/14 11:55:51, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) find_domain_master_name_query_fail: Unable to find the Domain Master Brows...

Hi, While going through DIAGNOSIS.txt on my samba 2.2.2 server, I came across the following test results: Test 5: [root@NetServer samba]# nmblookup -B resaddr8.research.bio2.edu '*' querying * on 209.64.53.8 name_query failed to find name * This appears to be a partial failure? Test 6: Initially, I got: [root@NetServer samba]# nmblookup -d 2 '*' added interface ip=209.64.53.11 bcast=209.64.53.255 nmask=255.255.255.0 querying * on 209.64.53.255 name_query failed to find name * It was suggested in DIAG...

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 the IP address back, but it also said name_query failed. Is this wrong? Also, on Test #5, it returns absolutely nothing (using client name OR the IP address). Our nmbd daemon is running, too....

...uble 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 192.168.1.255 name_query failed to find name *. This was supposed to return "got a positive name query response" but didn't. Th...

Hi All, I am trying to set up samba simply as a standalone Primary Domain Controller, but unfortunatley - for the last three days at least, it just does not want to play! i cannot find a problem in my smb.conf file and to proove that it works, i can log into the samba server via the linux command line with smbclient. The problem is the windows machines, when to go to log into the domain, i get

...15:52:38, 3] printing/printing.c:start_background_queue(1386) start_background_queue: Starting background LPQ thread [2007/04/29 15:52:38, 2] smbd/server.c:open_sockets_smbd(384) [root@trailrunner samba]# tail /var/log/samba/nmbd.log [2007/04/29 15:48:56, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 10.20.30.52 on subnet 10.20.30.45 for name DJ14847<1d> [2007/04/29 15:49:23, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 10.20.30.52 on subnet 10.20.30.45 for name D...

...is is a samba problem or an NT feature, but it seems only to occur with samba boxes, so it could be samba's fault: The NT PDC (moritz) runs also the WINS server. It regularly forgets the IP addresses of our samba servers: # nmblookup -U moritz -R hni-gate querying hni-gate on 131.234.166.19 name_query failed to find name hni-gate I then just have to stop and start the nmbd on the samba server and everything is fine again. This happens about every two weeks or so. Has anybody experienced anything similar and has an idea about how to stop it? Thanx, Christopher -- =========================...

...box) to point to the IP address of my Samba server. When I do a nmblookup -R -U <IP address of WINS server> <name of my PC> on my Samba server I get this reponse; querying pc1 on 10.1.1.251 wins_srv_died(): Could not mark WINS server 10.1.1.251 down. Address not found in server list. name_query failed to find name pc1 However, if I use the same command a query the Samba server I get this reponse; querying felix on 10.1.1.251 10.1.1.251 felix<00> Why isn't my Samba server storing the NetBIOS name of my PC? BTW, I am using Samba 2.2.7 supply by RH on a RH 7.3 box. Martin Stac...

...y nmblookup doesn't give an answer when looking up accross subnets. I increased the log level on the bdc to 4, hoping it might reveal something useful. pdc:/ # nmblookup pdc querying pdc on 192.168.0.255 192.168.0.3 pdc<00> pdc:/ # nmblookup bdc querying bdc on 192.168.0.255 name_query failed to find name bdc pdc:/ # smbclient -L pdc success, all services, shares and workstations are listed bdc:/ # nmblookup bdc debug_lookup_classname(nmbd): Unknown class added interface ip=192.168.2.3 bcast=192.168.2.255 nmask=255.255.255.0 querying bdc on 192.168.2.255 Got a pos...

...a is set to be a WINS server and LINDA points to it. lmhosts set to the above IPs. Using DIAGNOSIS.txt, I can get to TEST 5, where by I get the following: gateway# nmblookup -B LINDA '*' Added interface ip=192.168.1.3 bcast=192.168.1.255 nmask=255.255.255.0 Sending queries to 192.168.1.7 name_query failed to find name * TEST 4 shows Samba running: gateway# nmblookup -B SERVER __SAMBA__ Added interface ip=192.168.1.3 bcast=192.168.1.255 nmask=255.255.255.0 Sending queries to 0.0.0.0 Got a positive name query response from 127.0.0.1 ( 192.168.1.3 ) 192.168.1.3 __SAMBA__<00> TEST 8 also...

Hello. I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. Samba can't find its hostname via nmblookup: $ nmblookup -B 192.168.1.255 frontier querying frontier on 192.168.1.255 name_query failed to find name frontier If I query Samba via unicast, it answers OK: $ nmblookup -U frontier frontier querying frontier on 192.168.1.31 192.168.1.31 frontier<00> Also, Samba cannot find domain's master, but I suspect it can't become the master because of this nmblookup failure....

...:50, 0] param/loadparm.c:lp_do_parameter(3056) Ignoring unknown parameter "domain admin group" [2004/04/03 15:26:50, 2] lib/interface.c:add_interface(79) added interface ip=192.168.0.4 bcast=192.168.0.255 nmask=255.255.255.0 travis password: [2004/04/03 15:26:52, 2] libsmb/namequery.c:name_query(484) Got a positive name query response from 127.0.0.1 ( 192.168.0.4 ) [2004/04/03 15:26:52, 1] utils/net_ads.c:ads_startup(181) ads_connect: Connection refused [2004/04/03 15:26:52, 2] libsmb/namequery.c:name_query(484) Got a positive name query response from 127.0.0.1 ( 192.168.0.4 ) [2004/...

...bcast=10.1.255.255 nmask=255.255.0.0 error connecting to 10.1.45.12:139 (Connection refused) Error connecting to 10.1.45.12 (Connection refused) Connection to fk0000-msi-srv failed using nmblookup, send anything ..., found this error. $ nmblookup -B 10.1.45.12 '*' querying * on 10.1.45.12 name_query failed to find name * either using IP address or server_name give same error above. Using 'ping' both machine have no problem at all, either pinging itself or from other machine. If I turn to the documentation 'Using Samba' found at file:/usr/share/swat/using_samba/ch09_02.html#...

...not samba i.e. #> ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms #> nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave....

...1.CORP 1.1.1.2 DOM1.CORP But the previuos command gives error again. Even if I run nmblookup querying the servers or the domain, i get errors: DOM2-S1$ nmblookup -R -U localhost 'DOM1.CORP' added interface ip=1.1.2.1 bcast=1.1.2.255 nmask=255.255.255.0 querying DOM1.CORP on 127.0.0.1 name_query failed to find name DOM1.CORP Is this the right way to stablish the relationship? How should I add the entries to the lmhosts file? Regards and thanks in advance.

...he DIAGNOSTICS.txt and failed at test 8 with the error: System error 53 has occurred. The network path was not found. test 9 with the error: System error 59 has occurred. An unexpected network error occurred. test 10 with the error: querying delta on 12.20.194.255 querying delta on 12.20.194.255 name_query failed to find name delta#1d Test 11: cant browse I know this is sone kind of network issue, but i fail to see where... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com