See name resolve order in man smb.conf
I would suggest bcast
although, lmhosts or wins is probably the proper way to handle the
situation.
(lmhosts would require creating and copying a file to each workstation
that needs to be kept up to date. wins requires each client to be
configured to connect to the wins server, but is easy to maintain
thereafter.)\
On Sun, 25 Nov 2001, Peter Pilsl wrote:
samba2.2.2
On a new server (192.168.11.75) the host/dns-name is
different from the netbios-name. host/dnsname is "server2" and
netbiosname is "server". There is another host (192.168.0.1) in the
network that has dnsname "server" ...
nameresolution on systemlevel is done via dns only (no hosts-entries)
Now I have to discover that nameresolving brings unexpected
difficulties. Some names are resolved "false" and other take very long
amount of time.
if I try to query the list of servershares the command
fails cause smbclient seems to resolve via dns first and gets a
different IP for the name "server" via DNS ...
$/usr/local/samba/bin/smbclient -L //server -U peter
INFO: Debug class all level = 5 (pid 29237 from pid 29237)
pm_process() returned Yes
added interface ip=127.0.0.1 bcast=255.255.255.255 nmask=0.0.0.0
added interface ip=192.168.11.75 bcast=192.168.11.255 nmask=255.255.255.0
error connecting to 192.168.0.1:139 (No route to host)
Connection to server failed
imho the "correct" resolve for the netbios-name "server"
would have been
192.168.0.2, which is the address of machine with dnsname=server2 and
netbiosname "server".
If I try from a different client (that has no dns) I can query the
list of servershares, but it takes up to 10 seconds ...
#/usr/local/samba/bin/smbclient -L //server -U peter
added interface ip=192.168.11.100 bcast=192.168.11.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.0.0.255 nmask=255.255.255.0
Password:
If I add the correct IP-adress using the -I switch of smbclient all my
problems vanishes. I guess the equivalent of the -I switch on win-side
is a proper entry in lmhosts, but I really dont want to do this on all
our clients.
I know that its a very bad idea to mixup netbios and dns-names, but
Ido some servermigrating here and until all the stuff is finished,
this seems the best solution. (I migrate step by step : fileserver,
mailserver ...)
How can I avoid this name-confusion ? Would winns help me out of my
miserable situation ? (I dont think so ...)
the relevant parameters in smb.conf are :
bind interfaces only = yes
interfaces = 127.0.0.1/32 192.168.11.0/24
netbios name = server
name resolve order = host
wins proxy = no
wins support = no
thnx,
peter
--
mag. peter pilsl
phone: +43 676 3574035
fax : +43 676 3546512
email: pilsl@goldfisch.at
sms : pilsl@max.mail.at
pgp-key available
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba