SAMBA again

[Roger Oberholtzer]

On Wed, 2005-11-23 at 09:29 -0800, Aaron Grewell wrote:
> > I have this setup. nmbd is running and I see that samba not only sends
> > my machine info to the wins server, it also broadcasts it to the
> > network. The wins server acknowledges my information. This without the
> > FQD name. But windows users still need to use it to get to me.
> > 
> > The problem I am refering to is resolving names of windows machines from
> > Linux (libresolv). I have 'hosts:  files dns' in my /etc/nsswitch.conf
> > file. I would think all would be in the local windows DNS. But I think
> > they are sloppy and only really maintain wins for internal machines. I
> > see a /lib/libnss_wins.so.2 file. Perhaps that could go on that line?
> 
> It sounds like WINS is screwy somehow.  Are you sure the Windows
> workstations have the correct default domain set?  They should be able
> to hit you via DNS, regardless of WINS issues.  You should be able to
> put WINS into the hosts line in nsswitch, but what sort of configuration
> it would require in order to work I don't know.  I've never used it that
> way.  This is a server, right?  Generally you shouldn't need to resolve
> the Windows workstations, as long as they can find you all should be
> well.

The whole name system here is odd. They use a NAT. Machines that are
externally available are not available internally by their externally
known address. This means that they have a local DNS that tells where
these machines are. So, I manage my own DNS for the opq.se domain, which
is these days behind their NAT. (We were bought out a bit back.)
Externally, the opq.se DNS works as expected. Internally, I have to tell
the IT guy what addresses are in my DNS so he can add them to the local
name system using their internal addresses. I would have thought that
the NAT would have handled this directly. But, that is not how it is
done.

One additional question: I have asked the IT guy here for a 'machine
account' in the active directory. He is looking in to it. The SAMBA docs
are a bit sketchy on this, but is the very act of the admin logging in
from my machine what it takes to create the machine account? The docs
mention many steps, but I think the assume that I know the relationship
between them. When it come to the MS part, this is a bad assumption.

-- 
Roger Oberholtzer
OPQ Systems AB