Samba and Lmhosts: HELP NEEDED

[Bob Dusek]

The "remote announce" and "remote browse sync" should allow a samba
server to communicate its information to another samba server.  

You could use this functionality, it seems, with the notion of a central
WINS server.  When you specify your WINS configuration, you can specify
more than one WINS server.  Configure all of your "local" WINS servers
to "remote announce" themselves to the central server.  Then, configure
all of your clients to use the central WINS server first.  If that
server is down or they cannot connect to it, then they should fall back
to the secondary WINS server, which you could configure to be the local
WINS server (e.g. server2 for site2).

The remote announce command(s) might look like this..

remote announce = 135.91.10.51/CDomain
remote browse sync = 135.91.10.51

135.91.10.51 should be the ip address of your central WINS server and
"CDomain" should be the domain name of the domain that your central WINS
server lives in.

I've not actually done this on a large scale.  But, I have used the
remote announce and remote browse sync directives before and they do
work (between Samba WINS servers).   

best of luck,

Bob

werner maes wrote:
> 
>   Hello,
> 
> I would like to use an lmhosts file to solve the following problem:
> 
> At our university we have different sites with Samba servers. They all
> serve as domain logon servers (and WINS-servers) for several
> domains. People from one departement log on to the Samba server of their
> domain. The problem occurs when
> they go (fysically) to another site where they would like to log on and
> obtain their shares from their homesite.
> 
> Therefore I wanted to make an general lmhosts file which has the Netbios
> names of all the logon servers for
> all the domains. This file would be placed on each logon server in
> /etc/lmhosts. On all the logon servers I would
> also have "name resolve order = lmhosts wins bcast".
> 
> Example lmhosts file:
> 
> a.b.c.d    server1#20 (domain logon server for site1)
> a.b.c.d    domain1#1b
> e.f.g.h    server2#20 (domain logon server for site2)
> e.f.g.h    domain2#1b
> 
> The windows clients (win98) are configured according to the specific site.
> Network Neigbourhood: Enable Wins-resolution, wins-server = server1 for
> clients in site1
> 
>     wins-server = server 2 for clients in site 2
> 
> So a user wants to logon to server2 but who is fysically in site1 (where
> the clients refer to the wins-server of site1).
> He fills in his userid and password and types in his domain (in the
> Client for Microsoft Networks) and tries to logon. THIS FAILS
> Error ==>No domain server was available to validate your password.
> 
> TEST: If we change the configuration of the Windows client in site1:
> wins-server = wins-server of site2. Then it is possible to logon
> from site1 to the server in site2. The logon script is being executed.
> This seems evident because the logon server2 is found in the
> WINS database.
> 
> My question:
> What's wrong with my lmhosts file? Why is the logon server not found? Or
> other configuration settings?
> I also tried adding "a.b.c.d    domain1#1c" to the lmhosts file but this
> did not help either.
> 
> Any information would be greatly appricated,
> 
> Werner Maes
> LUDIT-KULeuven

--

Saint Joseph's College --  bobd at saintjoe.edu | http://www.saintjoe.edu
-----------------------------------------------------------------------
Administrative Computing Center, Bob Dusek...  219-866-6371

"Always the dullness of the fool is the whetstone of the wits."

		-- William Shakespeare, "As You Like It"