With the dhcpd server there is the ability to pass several parameters to a
requesting client when it seeks to lease an address.
I have noticed that my dhcpd server is passing some parameter or other to
a Windows client that is telling the latter to resolve netbios using dns,
which is causing the client to try to resolve some pretty unreasonable
names.
Which of the dhcpd.conf settings is likely to be causing this, or better
still which setting would prevent it.
My dhcpd.conf is below. The WINS server at .74 is working OK, but the
client keeps trying to resolve netbios names with .66 et al, which I don't
want.
When I look on the Windows client in winipcfg I see that the NETBIOS
Resolution uses DNS box is ticked, and that is not from any setting on the
Windows client, so somehow its coming from the dhcp parameters. Could it
be that Windows is assuming that because it has been told about some dns
name servers then it is entitled to assume that it can use them for
netbios resolution. Why would I not be surprised if that was the case
(8-(
option domain-name "lannet.com.au";
option domain-name-servers 203.41.237.66, 139.130.4.4, 139.130.4.5;
option netbios-name-servers 203.41.237.74;
option netbios-dd-server 203.41.237.74;
get-lease-hostnames off;
max-lease-time 10800;
default-lease-time 7200;
server-name "janus.lannet.com.au";
# A pseudo definition to keep dhcpd quiet about the eth0 interface
subnet 203.41.237.64 netmask 255.255.255.252 {
option broadcast-address 203.41.237.67;
}
# LANNet workstations
subnet 203.41.237.80 netmask 255.255.255.240 {
range 203.41.237.82 203.41.237.94;
option routers 203.41.237.81;
option broadcast-address 203.41.237.95;
}
--
Howard.
______________________________________________________
LANNet Computing Associates <http://www.lannet.com.au>
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
