search for: nmblookups

Newbie question. If I type nmblookup __some other machine__ I get the correct response from Samba. If I type nmblookup __mymachine__ then I get an error yhat it is not found. So if nmbd is not setup right, how do I fix it? --Dan Dan Huston Phone (602) 965-2420 Measurement, Statistics and Methodological Studies Fax (602) 965-0300 Psychology in Education

Hi folks, I find that nmblookup seems to be receiving responses to name queries, but ignoring them. Here's what's happening: # nmblookup somehost querying somehost on x.y.255.255 name_query failed to find name somehost But watching the transaction with ethereal on the local host, I see that: 1. nmblookup on local udp port nnnn (some random number above 1024) sends an nbns

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

I'm running Samba 1.9.18p8. If I use nmblookup to query the name of an NT server, as in nmblookup -A <ip address> then a packet trace shows an RPC reply coming back and nmblookup displays a list of names belonging to the NT server. If I try the same query on a Windows 95 machine, nmblookup only says Looking up status of <ip address> No status response (this is not unusual)

Hello, 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

I'm debugging my Samba setup using the "Troubleshooting Techniques" from Sam's Teach Yourself Samba in 24 Hours. Everything works fine up until the nmbd section. I am able to do the following correctly: nmblookup -U 127.0.0.1 __SAMBA__ nmblookup -U 127.0.0.1 POGO (the server) nmblookup -B 192.168.1.255 WIN-CLIENT (the client) but when I do nmblookup -B 192.168.1.255

hi! Sorry in advance if I am not on the right mailing-list and sorry if my question is cover somewhere is doc (I didn't find anything). The result from nmblookup (same result on all platform) for a given samba server isn't what I expect. The key part of my smb.conf is: [global] netbios name = ourserver2 netbios aliases = ourserverdev ourserverlab ourserver name

Hi Everyone, >From windows 2K, machine I could see Samba server but I can't get its share. I tried to follow the instruction given at http://samba.planetmirror.com/samba/ftp/docs/Samba24Hc13.pdf to resolve the problem. nmblookup -U 127.0.0.1 _SAMBA_ and nmblookup -B 10.10.255.255 real-samba-server-name fails for me but nmblookup -U 127.0.0.1 real-samba-server-name

I'm trying to use nmblookup to find the IP address of a Windows machine called "MARKETKA" (only with an accent over the 'E'). If I do a reverse lookup on the IP address, with debugging enabled, I can see that the hex code for the accented 'E' character is 0x90: $ nmblookup -d 4 -A 192.168.1.15 | grep MARK answers 0 char .MARK.TKA hex

Hi there, i have Samba 2.2.7a running on FreeBSD-STABLE 4.7. I set up a few things and smbd and nmbd start up at boot, i can browse the net. However, nmblookup can only find IPs by SMB-names, but not SMB-names by IPs. Here is an example output of the failed lookup: %nmblookup -d 3 210.104.1.133 Initialising global parameters params.c:pm_process() - Processing configuration file

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,

Hi, Some time ago, I wrote a small script based on some information on one of the Samba lists, which let me figure out which machine a user was logged in on. The script was this:- # smbfind: watch for someone to log in PATH=/bin:/usr/bin case $# in 0) echo 'Usage: smbfind <nt_login>' 1>&2; exit 1 esac nmblookup -S "${1}#03" | awk '/<00> - /{print

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email. Here's some test results and my smb.conf follows. Thanks in advance for the help! * nslookup and ping work in both directions * #smbclient //fileserver/test...

Hi, I hope you can help! I am having problems getting samba to share across a large private network. The problem looks a bit like the problem is in resolving the name to an IP but I can't work out why. The network is a private (10.) network, and the PC's connecting to it are named and identified through Wins. All the PC's are running Novell clients to connect although a large

Dear List, I hope someone could give me some explanation about above error/problem I got. I have 2 machines, one installed RH7.3 (IP ADDR. =10.1.45.12, host name = fk0000-msi-srv) and the other one, Mandrake8.2. (IP ADDR. = 10.1.45.13) Both machines use Samba 2.2.3a. At the RH7.3, I got following error if I connect from Mandrake8.2. $ smbclient -U% -L 10.1.45.12 added interface ip=10.1.45.13

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 *

Folks I've installed Centos6 and Samba. I noticed that the program "nmblookup" and a few other Samba related programs, documented in the RHEL6 guide, are not included in Centos6. A search using YUM also did not find "nmblookup", using the repositories: base, centosplus, contrib, cr, epel, extras, updates, virtualbox Has its functionality been moved elsewhere, or

Hi all... I need to make a few queries to WINS, but am unsure how to do so. 'nmblookup' will allow me to enter an IP address and get information about the machine name, domain, and username. I want to do the opposite...I would like to have a tool that will take a username and return the IP address. I know this information is stored in WINS somehow, and I am capable of writing some Perl

I have an XP Pro box on my LAN, and I'm trying to figure out why nmblookup '*' can't see it. I'm writing a script that finds all the shares on the LAN and mounts them, and it works great except for this one box. On another windows box, when I run "net view", the XP box is listed as I expect. On my linux box, when I run "nmblookup -A 192.168.0.111" it

When I have my iptables based firewall running, I cannot get nmblookup to locate any computers (Windows 98, Samba, Windows NT 4, or Windows XP) I require tight firewall settings, because college students can cause havoc on a network when its servers are not secure. I need a way to get nmblookup to work without disabling the firewall. The standard conntrack module does not work, because