That's what I currently do, but I don't want to have to do it.
I want to just plug the machine in wherever, and have it work.
Looking at the dhcpd source, there's a long comment that explains
what's supposed to happen with DHCPREQUESTs, and it basically
says that the DHCP protocol prohibits the server from NAKing
a DHCPREQUEST with an unknown address. However, the client is
supposed to eventually give up and try a DHCPDISCOVER. The NT
client doesn't do this, which seems to mean it's broken. I'm
considering adding a command-line switch to dhcpd to make it
NAK these requests so that NT clients can get addresses
in this situation, but I don't want to do it if there's already
some accepted way of achieving the goal.
Thanks,
-- Joe
smn wrote:
>
> With NT, dromp into a cmd shell and type "ipconfig /release" which will
> release the 10.1.0/24 subnet. Then you can try an "ipconfig /renew" to
> get your local subnet.
>
> I do the same thing with my work laptop, so here's my dhcpd.conf:
> subnet 192.168.10.0 netmask 255.255.255.0 {
> range 192.168.10.3 192.168.10.20;
> option subnet-mask 255.255.255.0 ;
> option broadcast-address 192.168.10.255 ;
> option routers 192.168.10.1;
> option domain-name-servers dns.1.ip.here, dns.2.ip.here, 192.168.10.1;
> option domain-name "yourdomain.here.ok";
> }
>
> See how this works for you.
>
> - Scott
>
> Joe Knapka wrote:
> >
> > Hi everyone,
> >
> > I just set up a DHCP server on my firewall so I could bring
> > my (NT) laptop home from work and not have to reconfigure
> > the network card with a static IP. I'm running the ISC
> > DHCPD.
> >
> > The problem is, at work the DHCP server there assigns an
> > address from a 10.1.0/24 subnet. Then I bring the machine
> > home, boot it on my 192.168.81/24 subnet, and it tries
> > to renew its lease on the 10.1.0.xxx address. Since my
> > DHCPD doesn't know anything about that address, it ignores
> > the DHCPREQUEST, and the laptop never sends a DHCPDISCOVER,
> > so it never gets a valid address on my subnet. I've read
> > all the documentation that came with the server, but it's
> > not clear to me how to deal with this. Any ideas? (I
> > can manually release the address from the NT machine,
> > and it then acquires a nice shiny 192.168.81 address, but
> > the whole point of this was to not have to mess with
> > the client configuration all the time...)
> >
> > (As an aside, does anyone know if it's possible to make
> > an NT machine acquire nameserver and gateway addresses
> > via DHCP?)
> >
> > Thanks,
> >
> > -- Joe
> >
> > *** Joe Knapka ***
>
> --
> Never do Windows again with | Scott M. Nolde
> Linux! No streaks, haze or | ">smnoldelinux@mediaone.net
> glaze! |
> 10:30am up 1 day, 15:15, 1 user, load average: 1.00, 1.00, 1.00
> --
> To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.
-- Joe Knapka
* What happens when a mysterious force meets an inscrutable object?
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.