Re: DHCP networking issue
From: tim gorman (tgorman2_at_cox.net)
Date: 06/23/04
- Next message: Cola.b: "Re: Does IBM REALLY support Linux?"
- Previous message: Anderson: "Re: weird root login"
- In reply to: Henry Meyerding: "DHCP networking issue"
- Next in thread: Arthur Hagen: "Re: DHCP networking issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 23 Jun 2004 12:17:23 -0500
Henry Meyerding wrote:
>
>
> Yesterday my client began to complain that Outlook could not connect to
> the Linux mailserver on the LAN to send and receive mail. At that point
> there were no configuration changes on the Linux server.
>
> I then did an online update and this did not repair the problem, but I did
> get an email about some DHCP firewall issue relating to iptables, which I
> don't use.
>
> The synptom is this: although the Windows XP machines are getting a DHCP
> lease and receive a valid IP address on the local LAN, they cannot resolve
> DNS all of a sudden.
>
> What do I need to check and how can I track this down and fix it?
>
> -------------
> dhcpd.conf
>
> ddns-update-style none;
>
> subnet 192.168.44.0 netmask 255.255.255.0 {
>
> option routers 192.168.44.1; option subnet-mask 255.255.255.0;
> option domain-name "holyinn.org";
> option domain-name-servers 199.181.164.2, 199.181.164.1;
> option time-offset -8; # Pacific Standard Time
> # option netbios-name-servers 192.168.1.1;
>
> range dynamic-bootp 192.168.44.10 192.168.44.254;
> default-lease-time 21600;
> max-lease-time 43200;
>
> # fixed address example
> #host fixed {
> # hardware ethernet 12:34:56:78:AB:CD; # fixed-address
> 10.0.0.2;
> #}
> }
>
> ------------
> typical dhcp log messages:
> Jun 22 17:53:45 stpeter dhcpd: DHCPREQUEST for 192.168.44.254 from
> 00:40:2b:4f:91:fb (St_Anthony) via eth0 Jun 22 17:53:45 stpeter dhcpd:
> DHCPACK on 192.168.44.254 to 00:40:2b:4f:91:fb (St_Anthony) via eth0 Jun
> 22 17:54:10 stpeter dhcpd: DHCPREQUEST for 192.168.44.254 from
> 00:40:2b:4f:91:fb (St_Anthony) via eth0 Jun 22 17:54:10 stpeter dhcpd:
> DHCPACK on 192.168.44.254 to 00:40:2b:4f:91:fb (St_Anthony) via eth0 Jun
> 22 17:59:57 stpeter dhcpd: DHCPREQUEST for 192.168.44.253 from
> 00:40:2b:4f:92:2c (ROSE) via eth0 Jun 22 17:59:57 stpeter dhcpd: DHCPACKon
> 192.168.44.253 to 00:40:2b:4f:92:2c (ROSE) via eth0 Jun 22 18:00:23
> stpeter dhcpd: DHCPRELEASE of 192.168.44.252 from 00:40:2b:4f:92:2c
> (ROSE)via eth0 (found) Jun 22 18:01:13 stpeter dhcpd: DHCPREQUEST for
> 192.168.44.253 from 00:40:2b:4f:92:2c (ROSE) via eth0 Jun 22 18:01:13
> stpeter dhcpd: DHCPACK on 192.168.44.253 to 00:40:2b:4f:92:2c (ROSE) via
> eth0 Jun 22 18:01:45 stpeter dhcpd: DHCPDISCOVER from 00:40:2b:4f:92:2c
> via eth0 Jun 22 18:01:45 stpeter dhcpd: Ping timeout: 1 Jun 22 18:01:46
> stpeter dhcpd: DHCPOFFER on 192.168.44.252 to 00:40:2b:4f:92:2c (ROSE) via
> eth0 Jun 22 18:01:46 stpeter dhcpd: DHCPREQUEST for 192.168.44.252
> (192.168.44.1) from 00:40:2b:4f:92:2c (ROSE) via eth0 Jun 22 18:01:46
> stpeter dhcpd: DHCPACK on 192.168.44.252 to 00:40:2b:4f:92:2c (ROSE) via
> eth0
>
> -----------------
> Log of messages when I tried to reconfigure DHCP with YAST:
> Jun 22 22:58:59 stpeter dhcpd: Internet Software Consortium DHCP Server
> V3.0.1rc12 Jun 22 22:58:59 stpeter dhcpd: Copyright 1995-2003 Internet
> Software Consortium. Jun 22 22:58:59 stpeter dhcpd: All rights reserved.
> Jun 22 22:58:59 stpeter dhcpd: For info, please visit
> http://www.isc.org/products/DHCP Jun 22 22:58:59 stpeter dhcpd:
> /var/lib/dhcp///etc/dhcpd.conf line 10: semicolon expected. Jun 22
> 22:58:59 stpeter dhcpd: authoritative 192. Jun 22 22:58:59 stpeter dhcpd:
> Jun 22 22:58:59 stpeter dhcpd: Configuration file errors encountered --
> exiting Jun 22 22:58:59 stpeter dhcpd:
> Jun 22 22:58:59 stpeter dhcpd: If you did not get this software from
> ftp.isc.org, please Jun 22 22:58:59 stpeter dhcpd: get the latest from
> ftp.isc.org and install that before Jun 22 22:58:59 stpeter dhcpd:
> requesting help. Jun 22 22:58:59 stpeter dhcpd: Jun 22 22:58:59 stpeter
> dhcpd: If you did get this software from ftp.isc.org and have not Jun 22
> 22:58:59 stpeter dhcpd: yet read the README, please read it before
> requesting help. Jun 22 22:58:59 stpeter dhcpd: If you intend to request
> help from the dhcp-server@isc.org Jun 22 22:58:59 stpeter dhcpd: mailing
> list, please read the section on the README about Jun 22 22:58:59 stpeter
> dhcpd: submitting bug reports and requests for help. Jun 22 22:58:59
> stpeter dhcpd: Jun 22 22:58:59 stpeter dhcpd: Please do not under any
> circumstances send requests for Jun 22 22:58:59 stpeter dhcpd: help
> directly to the authors of this software - please Jun 22 22:58:59 stpeter
> dhcpd: send them to the appropriate mailing list as described in Jun 22
> 22:58:59 stpeter dhcpd: the README file. Jun 22 22:58:59 stpeter dhcpd:
> Jun 22 22:58:59 stpeter dhcpd: exiting.
>
> I renamed dhcpd.conf created by yast as dhcpd.conf.yast and restored the
> original dhcpd.conf file copied above.
>
> Please cc my email address below in reply.
>
> Thanks,
Are you sure your named process is still running and working ok? Is it only
a problem with windows clients or with linux/unix clients also? Have you
tried a telnet to your dns server on port 53 to see if it answers? This
sounds a lot more like a dns server or routing problem than it does a dhcp
problem, especially if nothing in the configuration changed on the linux
server.
tim
- Next message: Cola.b: "Re: Does IBM REALLY support Linux?"
- Previous message: Anderson: "Re: weird root login"
- In reply to: Henry Meyerding: "DHCP networking issue"
- Next in thread: Arthur Hagen: "Re: DHCP networking issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
