<br><font size=2 face="sans-serif">Hi,</font>
<br><font size=2 face="sans-serif"> I'm not sure if the situations
are exactly the same but I had the same issue a few weeks ago. MACs
and LINUX obtained IPs with no problem but XP machines failed. We
have Cisco gear and I was using DHCP-relay. The solution to my problem
(and hopefully yours) was provided by David Hankins. He advised
the following;</font>
<br>
<br><font size=2 face="sans-serif">'</font><tt><font size=2>first thing
to check; do you have 'ip broadcast-address' configured<br>
on the first Cisco with the ip-helper set up?<br>
<br>
Windows boxes, when they receive broadcasts, are very conservative in<br>
what they receive; it MUST be sent to 255.255.255.255 as dictated in<br>
rfc2131, and cisco relays in this configuration will use the<br>
configured broadcast address instead.</font></tt><font size=2 face="sans-serif">'</font>
<br>
<br><font size=2 face="sans-serif">In my case I had config'd an 'ip broadcast-address'
statement on the router port. This meant that the response went back
to 1.2.3.4.255 rather than 255.255.255.255</font>
<br>
<br><font size=2 face="sans-serif">MACs and LINUX are happy seeing either
response but Windows (as David pointed out) absolutely needs to see a broadcast
to 255.255.255.255</font>
<br>
<br>
<br><font size=2 face="sans-serif">.........hope this helps (with thanks
to David again)..........................J</font>
<br>
<br><font size=2 face="sans-serif">James Savage
York University <br>
Senior Communications Tech. 108 Steacie Building<br>
jsavage@yorku.ca
4700 Keele Street<br>
ph: 416-736-2100 ext. 22605 Toronto,
Ontario<br>
fax: 416-736-5701
M3J 1P3, CANADA
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Jeff Sumner"
<Jeff.Sumner@nationalcity.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: dhcp-users-bounce@isc.org</font>
<p><font size=1 face="sans-serif">04/11/2008 12:04 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
dhcp-users@isc.org</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">dhcp-users@isc.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Linux clients working, XP not.</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Folks,<br>
<br>
Can someone point me to any documentation for troubleshooting why Linux<br>
clients would work with a particular configuration from an implementation
of<br>
ISC DHCP but XP clients won't?<br>
<br>
I see packets coming in and going out of the DHCP server via a sniffer,
but<br>
the XP clients won't send an ACK, where the Linux boxes will.<br>
<br>
The XP clients don't get addresses.<br>
<br>
I'm poking around Google, and see several instances of folks having problems<br>
with this, but no fixes are listed- the threads just die off. It seems
that<br>
sometimes XP reboots fix the trouble, but that's not helping here. Again,<br>
Linux guests work fine, to the point of DDNS working extremely well.<br>
<br>
Someone brought an XP workstation into the lab and suddenly, we have a<br>
troubleshooting opportunity!<br>
<br>
Server versions tried are DHCP3.1.1rc1, 3.1.0 and 3.0.6. Host is AIX 5.1
and<br>
built with GCC.<br>
<br>
Network is private, 192.168.0. Many options defined, but nothing seems
to<br>
get the XP boxes to ACK.<br>
<br>
<br>
<br>
J<br>
<br>
<br>
-------------------------------------------------------------------------------------------<br>
***National City made the following annotations<br>
-------------------------------------------------------------------------------------------<br>
This communication is a confidential and proprietary business communication.
<br>
It is intended solely for the use of the designated recipient(s). If
this<br>
communication is received in error, please contact the sender and delete
<br>
this communication.<br>
===========================================================================================<br>
<br>
</font></tt>
<br>