What are you using for a DHCP Server?
--- James E Harvey <[EMAIL PROTECTED]> wrote: > Sorry for the delay in my reply, Comcast has been > having problems with our > email... > > In regards to the dhcp, we've checked all the usual > problem areas, but can > find no obvious "mess ups". > > This all started about three weeks ago, prior to > that the dhcp has worked > fine from the beginning (a couple/few years). > > We can think of nothing we have done recently that > would be a cause. > > Could a "bad" switch or hub cause this issue. I > don't mean a "router". We > have 4 of 5 of them throughout the buildings, and I > was wondering if one > went "bad" would that be enough to screw up > dhcp????? > > > > James E Harvey > Hanover Shoe Farms, Inc. > M.I.S./Corresponding Officer > Off: 717-637-8931 > fax: 717-637-6766 > email: [EMAIL PROTECTED] > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Jim Dettman > Sent: Tuesday, May 15, 2007 3:49 PM > To: [email protected] > Subject: RE: [NF] Problematic DHCP > > > James, > > A 169. address is the auto configure address that > Windows uses when it > cannot get a address from a DHCP server. > > Two things: > > 1. Make sure you have enough free addresses in your > DHCP pool. > > 2. Make sure any static address is excluded from the > pool (ie. was a printer > or other piece of equipment added lately?). > > JimD > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of James E Harvey > Sent: Tuesday, May 15, 2007 11:26 AM > To: [EMAIL PROTECTED] > Subject: [NF] Problematic DHCP > > The last couple of weeks our users have been having > issues getting logged on > to our domain due to IP address not being assigned > properly (169 rather than > a 192) > > The system event log shows the following error > message with an Event ID of > 1002: > > "The IP address lease %1 for the network adapter > with MAC address %2 has > been denied by the DHCP server %3 (The DHCP server > sent a DHCPNACK > message)." > > We thought it was a rogue router with DHCP turned on > but it turns out that > wasn't the case. > > If we do the "repair" through the GUI, or ipconfig > /release&renew at the > command prompt we can usually get the user a valid > IP address and they're > good to go, until the next time they need to log on. > > We can't see where anything on the DHCP server that > appears obviously out of > norm... > > Any thoughts would be appreciated. > > TIA > > > James E Harvey > Hanover Shoe Farms, Inc. > M.I.S./Corresponding Officer > Off: 717-637-8931 > fax: 717-637-6766 > email: [EMAIL PROTECTED] > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
