name resolution across subnet bounderies
Andreas Schuldei
andreas at schuldei.org
Mon Nov 5 06:29:04 GMT 2001
I do get problems with name resolution accross subnet bounderies.
I have a working and wins server and to demonstrate the problem I
paste the debug output of
mount /smbhome/
opts: uid=1000
opts: gid=1000
mount.smbfs started (version 2.2.2debian-2)
added interface ip=192.168.6.2 bcast=192.168.6.255 nmask=255.255.255.0
resolve_lmhosts: Attempting lmhosts lookup for name Tri-st-s001<0x20>
startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory
resolve_hosts: Attempting host lookup for name Tri-st-s001<0x20>
resolve_wins: Attempting wins lookup for name Tri-st-s001<0x20>
resolve_wins: WINS server == <192.168.4.3>
bind succeeded on port 0
wins_srv_died(): WINS server 192.168.4.3 appears to be down.
name_resolve_bcast: Attempting broadcast lookup for name Tri-st-s001<0x20>
bind succeeded on port 0
4869: Connection to Tri-st-s001 failed
SMB connection failed
this problem goes away with a /etc/samba/lmhosts, which holds
exactly the same data for Tri-st-s001. With that I get:
mount /smbhome/
opts: uid=1000
opts: gid=1000
mount.smbfs started (version 2.2.2debian-2)
added interface ip=192.168.6.2 bcast=192.168.6.255 nmask=255.255.255.0
resolve_lmhosts: Attempting lmhosts lookup for name Tri-st-s001<0x20>
getlmhostsent: lmhost entry: 192.168.4.2 TRI-ST-S001
Connecting to 192.168.4.2 at port 139
4873: session request ok
4873: session setup ok
4873: tconx ok
smbfs: failed to load nls 'cp437'
I have the same problem when I try to get winbindd (or for that
case wbinfo -t) info in the 192.168.6.X (client-) subnet from
192.168.4.X (server-) subnet.
there I get from winbind:
[ 3870]: check machine account
resolve_lmhosts: Attempting lmhosts lookup for name TRITECH<0x1b>
getlmhostsent: lmhost entry: 192.168.4.2 TRI-ST-S001
resolve_wins: Attempting wins lookup for name TRITECH<0x1b>
resolve_wins: WINS server == <192.168.4.3>
bind succeeded on port 0
wins_srv_died(): WINS server 192.168.4.3 appears to be down.
name_resolve_bcast: Attempting broadcast lookup for name TRITECH<0x1b>
bind succeeded on port 0
could not find domain controller for domain TRITECH
this is my smb.conf:
[global]
printing = cups
printcap name = /etc/printcap
load printers = yes
guest account = nobody
invalid users = root
security = domain
workgroup = TRITECH
server string = %h server (Samba %v)
syslog only = no
syslog = 0;
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096 SO_RCVBUF=4096
encrypt passwords = yes
wins support = no
wins server = 192.168.4.3
enhanced browsing = yes
remote browse sync = 192.168.4.11
name resolve order = lmhosts host wins bcast
dns proxy = no
preserve case = yes
short preserve case = yes
unix password sync = false
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
message command = for u in $(who | cut -f1 -d\ | sort -u); do { echo 'WinPopup message from %f ...'; echo ''; cat %s;} | write "$u"; done; rm %s
max log size = 1000
winbind separator = +
winbind uid = 10000-20000
winbind gid = 10000-20000
winbind cache time = 10 ;3600
winbind enum users = yes
winbind enum groups = yes
template homedir = /home/%D/%U
template shell = /bin/bash
password server= *
[homes]
comment = Home Directories
browseable = no
read only = yes
create mask = 0700
directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /tmp
printable = yes
public = no
writable = no
create mode = 0700
What really bothers me is the winbind problem. What do I need to do to fix it?
More information about the samba
mailing list