Patrick,

> Check your RESLVCNF.NET.SYS (or /etc/resolv.conf) file.
> In our file, I only put a nameserver entry with the IP address of our
> DNS server. Adding a domain or search entry in that file on our
> system produces the same output that you receive from the
> smbclient command.
>
> Why? I'll be happy to know...

Samba requires DNS, and for an HP3000 to use DNS, it requires an entry into
the RESLVCNF.NET.SYS (which is linked to /etc/resolv.conf in the HFS
filespace).

Additionally, if your DNS server is remote (such as that your ISP provides
DNS, or it is several hops away via routers), then you could experience this
message because it's not being resolved fast enough.

I experienced this on our servers here until I placed BIND/SYSLOG on one of
the HP3000 which runs Samba (and additionally, put DNS up on an NT server as
a secondary) and all of that cleared right up.

DNS on NT goes up quickly for a single domain if you are not resolving every
PC - just servers, and if you know vi or have a visual editor that can edit
Unix formatted files (QEDIT for Windows or PFE), then BIND is not that bad
to deal with either.  You just need to work with the sample config files to
create your own.

I would suggest that if local DNS is up and running, then this message
should go away.

This is one of the biggest causes of problems with Samba.  It's also one of
the areas that many HP3000 shops are not familiar with handling, because
MPE's really never needed DNS until now -- with the inclusion of the many
internet tools that are coming out.

Best Regards,
Joe Geiser