I have NEVER been able to get nmbd to work in anything even remotely
approximating a usable fashion.
All I want it to do is DNS lookups.
I can't even get it to do that reliably. It looks in some cases like it
isn't even sending a response back to the querying clients.
When I do a request that fails, I get this:
---
nmb packet from 192.55.114.4(3175) header: id=8172 opcode=Query(0)
response=No
header: flags: bcast=Yes rec_avail=No rec_des=Yes trunc=No auth=No
header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
question: q_name=GAMMA(0) q_type=32 q_class=1
Name query from 192.55.114.4 for name GAMMA<0x0>
Found DNS cache entry GAMMA(0)
---
Nothing gets sent back.
When I query a name that works, I get this:
---
12/11/1997 21:59:27 received a packet of len 50 from (192.55.114.4) port 3309
nmb packet from 192.55.114.4(3309) header: id=8214 opcode=Query(0)
response=No
header: flags: bcast=Yes rec_avail=No rec_des=Yes trunc=No auth=No
header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
question: q_name=DELTA(0) q_type=32 q_class=1
Name query from 192.55.114.4 for name DELTA<0x0>
OK 192.55.114.3
replying netbios packet: nmb_query DELTA(0) 192.55.114.4
nmb packet from 192.55.114.4(3309) header: id=8214 opcode=Query(0)
response=Yes
header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=DELTA(0) rr_type=32 rr_class=1 ttl=42840
answers 0 char D..7r. hex 4400C0377203
nmb packet from 192.55.114.4(3309) header: id=8214 opcode=Query(0)
response=Yes
header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=DELTA(0) rr_type=32 rr_class=1 ttl=42840
answers 0 char D..7r. hex 4400C0377203
12/11/1997 21:59:27 sending a packet of len 62 to (192.55.114.4) on port 3309
---
Could someone explain how to get this working?
At the VERY LEAST I want people on Windows 95 boxes to be able to map a
drive by typing in the name directly.
If that can be gotten to work, then showing up in browse lists would be nice.
------------
On a side note, what is the proper way to configure nmbd so that it will
be as authoritative as possible, but is on a network that we don't
necessarily have control over someone else starting up another nmbd with
a completely arbitrary configuration?
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216
On Thu, 11 Dec 1997, Nathan Neulinger wrote:> > I have NEVER been able to get nmbd to work in anything even remotely > approximating a usable fashion. > > All I want it to do is DNS lookups. > > I can't even get it to do that reliably. It looks in some cases like it > isn't even sending a response back to the querying clients. > > When I do a request that fails, I get this: > > --- > nmb packet from 192.55.114.4(3175) header: id=8172 opcode=Query(0) > response=No > header: flags: bcast=Yes rec_avail=No rec_des=Yes trunc=No auth=No > header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0 > question: q_name=GAMMA(0) q_type=32 q_class=1 > Name query from 192.55.114.4 for name GAMMA<0x0> > Found DNS cache entry GAMMA(0) > --- > > Nothing gets sent back. >Hi, Are the reverse mappings in your dns correct and complete? Have you got the stops in the right places in the forward lookup? Have got any stops in the wrong places in the forward lookup? Try sending a SIGUSR1 to named to put it debug mode, and then look in the debug output. Send named a SIGINT and inspect the namedb dump. While in debug, send SIGHUP and check the debug output for errors found when reloading. Don't forget to SIGUSR2 named to take it out of debug mode! --- Peter Blake ppb@hft.co.uk ppb@baloo.tcp.co.uk
On Thu, 11 Dec 1997, Nathan Neulinger wrote:> > I have NEVER been able to get nmbd to work in anything even remotely > approximating a usable fashion. > > All I want it to do is DNS lookups. > > I can't even get it to do that reliably. It looks in some cases like it > isn't even sending a response back to the querying clients.If all you want to do is lookup a machine name or IP address, I have some alpha code that will do that from a unix box (I use HP). You are welcome to it. It works in our environment, we are running DHCP and WINS but not DNS on the PC side. It should work even better if you are running DNS on the PC side. Jeff Foster jfoste@wgc.woodward.com