Samba name resolution is slow

[omar_ita]

Dear all,

In my company I installed CentOS on a PC, enabling samba (smb+nmb). If I ping the linux box FROM windows, it takes around 15 seconds to resolve IP.

[ from Windows ]
C:\> ping linuxbox

[ ..... 10-15 seconds .... ]

Pinging linuxbox [192.168.100.3] with 32 bytes of data:

Reply from 192.168.100.3: bytes=32 time<1ms TTL=64
Reply from 192.168.100.3: bytes=32 time<1ms TTL=64

[ ..then scrolls smoothly ]

As you can see is not a network issue (I got a GigaLan), also latency is <1ms. If I ping directly the ip, the reply is immediate:

C:\> ping 192.168.100.3

Pinging 192.168.100.3 with 32 bytes of data:

Reply from 192.168.100.3: bytes=32 time<1ms TTL=64
Reply from 192.168.100.3: bytes=32 time<1ms TTL=64

I've tryed to trestart smb, nmb, disable firewall, no result. Obviously Windows machine can solve quickly any other network name.
The network is under a windows domain controller, but Linux machine is not.
Here comes rows from smb.conf that seem relevant to me:

workgroup = MYGROUP
local master = no
domain master = no
domain logons = no

What can I do to understand what's happening?
Thanks in advance ..

Mario.

[Roxoff]

Well the name resolution will not be handled by Samba, or by the Widnows domain. Your windwos box will be off asking for the DNS server to resolve names. If those IP addresses are not in your DNS servers map, then it'll go off and ask your secondary DNS machine. This all takes time. When you go direct to the IP address of course, there are no DNS lookups to carry out, so it's significantly quicker.

Check the zone config for your DNS server to be sure your linux machine is declared in that; if it's set up automatically when DHCP hands out addresses, make sure that whatever needs your linux box's IP address is looking at the right DNS servers and in the right order.