Arch Linux

vit

Member

Registered: 2008-12-28

Posts: 79

NetBIOS name resolution problem.

Hi!
On my work we have heterogeneous environment with some machines running linux.
I have configured NetBIOS name resolution. And it works normally.
My computer has 2 network interfaces:
eth0 (10.1.*.*) - corporate network, dhclient configurable
tap0 - virtual for Vbox with static 192.168.0.1, configured usung rc.local:

tap=$(tunctl -b -g vboxusers)
ifconfig $tap 192.168.0.1 netmask 255.255.255.0

The traffic from tap0 is forwarded using iptables:

$  sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
TCPMSS     tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,RST,ACK/SYN TCPMSS clamp to PMTU
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination 
Chain TCP (0 references)
target     prot opt source               destination
Chain UDP (0 references)
target     prot opt source               destination 
Chain fw-interfaces (0 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
Chain fw-open (0 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             192.168.0.2         tcp dpt:13000
ACCEPT     udp  --  anywhere             192.168.0.2         udp dpt:13000
ACCEPT     tcp  --  anywhere             192.168.0.2         tcp dpt:14000
ACCEPT     udp  --  anywhere             192.168.0.2         udp dpt:14000

And I have running samba daemon for file sharing with windows.
smb.conf
The problem is:
When somebody tries to ping my PC by NetBIOS name (e.g. ping arch) they are getting the ip of tap0 (192.168.0.1).

We have wins server up and running in network.
nmblookup arch gives 10.1.*.*, but wbinfo -N arch gives 192.168.0.1. We have checked and restarted wins, cleaning it's cache. The problem has to be on client.

Last edited by vit (2011-03-30 09:59:17)