similar to: Lightweight nmblookup

I'm using Debian Sid, and it seems like Iceweasel (aka Firefox) has been crashing a lot lately with "Bus Error" printed to stdout when it dies. I use mono/.net and python, so my C/C++ debugging skills are very lacking. I was able to capture the following using gdb on Iceweasel: Program received signal SIGBUS, Bus error. [Switching to Thread -1288709200 (LWP 28528)] 0xb1a98309 in

or not, using first dns and then WINS to lookup the name. I can get "ping" working, but everything else seems not to use the WINS lookup for addresses, which makes it less than useful. I followed the instructions in: "/etc/nsswitch.conf" in http://sunsite.dk/samba/docs/Samba-HOWTO-Collection.html#AEN297 , retrieved the samba source (-r SAMBA_2_2_RELEASE), "./configure ;

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)

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

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

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

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,

Hi All: When I usign nmblookup to query my domain controller, I got different = results: root@Latrell:# nmblookup -A ADDomain.com Looking up status of 169.254.211.91 No reply from 169.254.211.91 root@Latrell:# nmblookup -A ADDomain.com Looking up status of 172.23.26.204 WIN-2003 <00> - M <ACTIVE> WIN <00> -

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

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

Gerry, all: HELP! On mandriva, I compiled samba from source and got it running, but I cannot connect from windows. (see my post from earlier "[Samba] Compiling and Configuring Samba for Mandrival") I think this relates to the group/SID changes discussed in the release notes. However, I'm not smart enough to figure it out. The tarball compiled and installed fine. It

I have Ubuntu 14.04.LTS and some Windows 7 client, with for example IP 192.168.0.201. I run nmblookup from Samba4 4.1.14 built in my own (without changes at nmblookup) with the following parameter: *nmblookup -A 192.168.0.201* As there is defined at nmblookup, it query *<00> of specified IP. So, I see non constant answers: Sometimes for the first nmblookup run it shows answers where there

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

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 *

Hello list, The issue is as the topic says, following are details: the Samba server running as ADS member, NBT enabled on Windows machines, no WINS. Windows machines can find each other by 'nbtstat -a' but cannot find the Samba server. The Samba server can't find neither Windows machines nor itself by 'nmblookup -a <netbios-name>', error message is "could not open

Hi, I'm the author of lisa (http://lisa-home.sourceforge.net). Currently I'm trying to include netbios name lookup into my program and am using the sources from nmblookup. Can you please help me ? What is the meaning of these status flags and the status type or why can I find docs ? printf("%s <%x> - %s\n", cleanname, status[i].type, //