DHCP Problem with WIndows XP clients

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.

They also suddenly grew an MS Home workgroup.

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-(E-Mail Removed)
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,
--
Henry Meyerding
(E-Mail Removed)
360-793-1564
360-665-0730

Henry Meyerding <(E-Mail Removed)> 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.

....

> 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

This looks like the DHCPOFFER is not recognized by the client. Try
adding

route add -host 255.255.255.255 dev eth0

on the server. Read Section 4.1.2 of the DHCP-HOWTO for why.

Note: This may be way off-base; I just had an occasion yesterday to
learn a little about DHCP on Linux and have no experience whatever
configuring or using it.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/

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.
>
> They also suddenly grew an MS Home workgroup.
>
> 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-(E-Mail Removed)
> 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,

DHCP with Windows XP is painful. The whole release/renew thing is
behaving badly.

You client might try to right-click the connection properties in Windows
and select "Repair".

As for the DNS I often noticed the issue with XP workstations using
DHCP. Most of the time I ended up setting the DNS manually in logon scripts.

--
LucM

Visit your friends
> www.gnu.org
> www.greenpeace.org

>
> DHCP with Windows XP is painful. The whole release/renew thing is
> behaving badly.
>
> You client might try to right-click the connection properties in Windows
> and select "Repair".
>
> As for the DNS I often noticed the issue with XP workstations using
> DHCP. Most of the time I ended up setting the DNS manually in logon scripts.

Curouser and curiouser...
When I set up the Windows clients without DHCP, configuring the network
manually it does the same things....

I can ping an address. I cannot open a web page from a server I can ping.
I cannot collect mail from the mailserver on the LAN. I am at head
banging stage. Do I need to reinstall Windows on the client machines?

Windows clients are being scanned for viruses, but so far...

Anyone have any suggestions?

Gail Dimock wrote:

>>DHCP with Windows XP is painful. The whole release/renew thing is
>>behaving badly.
>>
>>You client might try to right-click the connection properties in Windows
>>and select "Repair".
>>
>>As for the DNS I often noticed the issue with XP workstations using
>>DHCP. Most of the time I ended up setting the DNS manually in logon scripts.
>
>
> Curouser and curiouser...
> When I set up the Windows clients without DHCP, configuring the network
> manually it does the same things....
>
> I can ping an address. I cannot open a web page from a server I can ping.
> I cannot collect mail from the mailserver on the LAN. I am at head
> banging stage. Do I need to reinstall Windows on the client machines?
>
> Windows clients are being scanned for viruses, but so far...
>
> Anyone have any suggestions?

Do you actually ping the server by its name (not IP) on the Windows
machines? If so, do you get an answer coming from the good IP?

If you run nslookup with the name of the server, do you get the good IP?

Otherwise, this might be a hosts file issue, which could be caused by
adware/spyware.
Have a look in the file c:\windows\system32\drivers\etc\hosts and see if
there are unusual entries (other than localhost).

What happens if you type the server IP in Internet Explorer (instead of
the hostname)? Do you get something? Otherwise check the proxy settings
in the internet connection properties.

--
LucM

Visit your friends
> www.gnu.org
> www.greenpeace.org

how do you ping? ip? what distro are you using in linux server?

can you ping that windows client from server?

did you configure samba on the server?

raqueeb hassan
congo (drc)

On Wed, 23 Jun 2004 23:05:33 -0400, LucM wrote:

See replies
>
> Do you actually ping the server by its name (not IP) on the Windows
> machines? If so, do you get an answer coming from the good IP?
>
I can ping either by IP or name. UDP works fine.
Here's an interesting symptom: I can open http://goomba.com (which
consists of 2 words) but although it says its connecting, it never
actually displays web content for any pages under that address (like
http://goomba.com/Poetry).

Outlook doesn't work. It pulls the mail off the /var/spool/mail mail
queue but never completes and diaplays it. When you close Outlook and
wait a while, the mail returns to the mail queue.

Samba is configures and is running, but Windows can't connect to it.

> If you run nslookup with the name of the server, do you get the good IP?
>
> Otherwise, this might be a hosts file issue, which could be caused by
> adware/spyware.
> Have a look in the file c:\windows\system32\drivers\etc\hosts and see if
> there are unusual entries (other than localhost).
>
Thanks, I'll look at these.

> What happens if you type the server IP in Internet Explorer (instead of
> the hostname)? Do you get something? Otherwise check the proxy settings
> in the internet connection properties.

No difference. It almost seems like it is refusing to return packets
larger then n to the Windows box. Weird.

--
Henry Meyerding
(E-Mail Removed)
360-793-1564
360-665-0730

On Thu, 24 Jun 2004 14:55:50 -0700, Raqueeb Hassan wrote:

> how do you ping? ip? what distro are you using in linux server?
>
ping either by name or IP, same result. UDP works.
Linux is SuSE 9.0

> can you ping that windows client from server?

Yes I can no problem with UDP apparently.
>
> did you configure samba on the server?

Yes I did, and it worked formerly. Now you see the samba server
and can select the home or shared location, at which point the
windows machine goes into hourglass mode...

>
> raqueeb hassan
> congo (drc)

--
Henry Meyerding
(E-Mail Removed)
360-793-1564
360-665-0730