|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] DHCP and winXP clients
|
I don't know anything about the "repair" function in WinXP. I do run a
similar setup to yours (using OpenBSD to provide the network services to
various machines incl. WinXP) and seem to have no problems getting WinXP
machines to pick up an IP and keep it. I do have options like DNS being
doled out by the dhcp server, but that shouldn't matter.
Why are the clients using this 'repair' function in the first place? It
would seem to me, once assigned, the process of obtaining an IP should
be transparent and the users shouldn't be futzing around with the IP
settings. Anyway...
If you go to a WinXP command prompt and type 'ipconfig release', then
'ipconfig renew', do you get an address? That's usually the very most I
might have to do, and even that is on the rare occasion I didn't pick an
IP up during boot.
You might also want to set your dchp lease option to a longer time
interval than a couple days if you are on a small LAN with few machines.
Good luck,
Dave
On Wed, 2003-10-29 at 17:19, Stephen Gran wrote:
> Hello all,
>
> I am having a problem with a small LAN. The basic setup is a linux
> (Debian woody) box that connects via pppoe to the isp, and then does
> some basic filtering, NAT, print sharing, dns, and so forth for the LAN.
> The LAN is all WinXP at this point (6 or so boxes).
>
> Recently I switched the LAN to DHCP from static addresses, as some users
> kept complaining that the 'repair' function in WinXP didn't repair
> anything, but in fact made things worse. From what I can gather, the
> 'repair' thing essentially releases any dhcp lease, flushes the arp
> cache, tries to renew a lease, and then sends a bunch of netbios
> discover packets about.
>
> Now that I have installed dhcp3-server, when a users hits 'repair', I
> see this:
> Oct 29 17:08:58 free dhcpd: DHCPRELEASE of 192.168.0.100 from 00:30:ab:1b:52:71 via eth1 (not found)
> Oct 29 17:10:00 free dhcpd: DHCPREQUEST for 192.168.0.100 from 00:30:ab:1b:52:71 via eth1
> Oct 29 17:10:00 free dhcpd: DHCPACK on 192.168.0.100 to 00:30:ab:1b:52:71 via eth1
> Oct 29 17:10:07 free dhcpd: DHCPDISCOVER from 00:30:ab:1b:52:71 via eth1
> Oct 29 17:10:07 free dhcpd: DHCPOFFER on 192.168.0.100 to 00:30:ab:1b:52:71 via eth1
> Oct 29 17:10:07 free dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from 00:30:ab:1b:52:71 via eth1
> Oct 29 17:10:07 free dhcpd: DHCPACK on 192.168.0.100 to 00:30:ab:1b:52:71 via eth1
>
> and no lease gets written to /var/lib/dhcp3/dhcpd.leases. On the client
> side, they see 'error flushing the arp cache', but they get a new
> address. The only out of the ordinary thing I did was give a couple of
> addresses fixed-address lines in dhcp.conf - they get the same errors as
> everyone else, though.
>
> The DHCPRELEASE (not found) message is esay enough to guess - there's no
> entry in the leases file to release. Anybody seen anything like this
> before? I would say that it's a client side problem, except that it's
> consistent, and it happens to all of them. I don't know dhcp that well,
> but I thought it was a pretty transparent thing - you shouldn't have to
> do much to get it going.
>
> Is this going to be a situation where I have to allow dhcp to update
> dns? I had hoped to stay away from that.
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|