That did the trick.. A rogue DHCP server is exactly my problem, and stopping it is outside of my control for the time being. This is all just a temporary setup, so this will work just fine.<br><br>Thanks all for the help!
<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">You can also put a setting in
dhclient.conf to ignore DHCP
replies from specific ip addresses. Again this isn't
ideal.</font></span></div><div dir="ltr" align="left"><span></span> </div><div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"> reject
ip-address;</font></span></div><div> </div><span><font color="#0000ff" face="Arial" size="2"> The reject statement
causes the DHCP client to reject offers
from</font></span><br><span><font color="#0000ff" face="Arial" size="2"> servers who use the
specified address as a server identifier.
This</font></span><br><span><font color="#0000ff" face="Arial" size="2"> can be used to avoid being
configured by rogue or misconfigured
dhcp</font></span><br><span><font color="#0000ff" face="Arial" size="2"> servers, although
it should be a last resort - better to track
down</font></span><br><span><font color="#0000ff" face="Arial" size="2"> the bad DHCP server and fix
it.</font></span><br></blockquote>