RE: [e-smith-devinfo] RE: BIND9 (was Re: [e-smith-devinfo] DHCP Server Problem??)
-Original Message- From: Filippo Carletti [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 05, 2001 12:46 PM Subject: Re: [e-smith-devinfo] RE: BIND9 (was Re: [e-smith-devinfo] DHCP Server Problem??) I've worked a bit with perl scripts from Stephen Carville (http://www.heronforge.net/~stephen/DHCP-DNS/dhcp-dns.html) and I've those almost working on e-smith. A cron job compares every minute its saved copy of dhcp leases with the original (/var/lib/dhcp/dhcpd.leases) and sends updates to dns. A perl program needs to be updated to sort hostname to lease time. If there is interest, I could work a little bit more on that and release a preliminary rpm. Stephen was kind enough to suggest using dhcpd 3 even if in late beta, but I did not try. So far I've been feeling like I'm the only one with any interest :-) Stephen's was one of the solutions I looked at. Right now I'm considering whether this approach (cron script, etc) would be better, or if I should give BIND9/DHCPD3 a try. I'm leaning toward the latter as I try to avoid customization whenever possible. I realize updating e-smith to BIND9/DHCPD3 is a customization of sorts, but overall the solution would be less of a hack than adding cron scripts, etc. Until I've had a chance to experiment with the new DNS/DHCP solutions, I think I'll hold off on a scripted alternative. Scott -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Sorry to re-hash this everyone, but we just lost another workstation (that makes 3 so far). They just can't get an IP address from the DHCP server. What files are required to reinstall the DHCP server? Is this recommended? Trev. -Original Message- From: John Powell [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 10:14 AM To: Trevor Ouellette; Graeme Robinson; John Powell Cc: E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? So, could the problem be with the DHCPD server? DHCP was working for a few months without any problems, now it stops recognizing NEW machines introduced to the system. I doubt it, but would rule nothing out. Going by your logs, the client is the one dropping the ball. To make it clearer, the normal init sequence looks like this: C: DHCPDISCOVER (client asking for IP) S: DHCPOFFER (server dishing out an IP) C: DHCPREQUEST (client accepting the offerred IP) S: DHCPACK (server finalizing the process) From your logs, the process gets through to the OFFER, which means it recognizes the client and is offering an IP. The client is not accepting it for some reason, not even NAKing it, which suggests either the client doesn't see the response, or is choking on it for some reason. It does not sound like a server problem. Even if the server is offering up junk, the client should NAK it. For one client computer... it worked the day before, the next day (poof), no IP address designation... strange. That is, indeed, strange. Is it possible to get a sniffer like trace of this in action? Ethereal is a fine choice, or any other product with a decent decoded output. You might also want to check out www.isc.com (makers of the DHCP server in e-smith) or a google search and see if they have some hints on known problems with Wintel clients. I don't know of any (ISC's server is generally solid as a rock). JP -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Trevor Ouellette [EMAIL PROTECTED] said: What files are required to reinstall the DHCP server? e-smith 4.12 uses: Server = dhcp-2.0-12.i386.rpm Client = dhcpcd-1.3.18pl8-6.i386.rpm Is this recommended? Don't know? Would be nice to solve why it is failing for you. I see the latest release available for both client/server is 3.0rc12. After appropriate testing in a non-production environment to make sure it works with e-smith, maybe an upgrade is in order? -- Darrell May DMC NETSOURCED.COM http://netsourced.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Yes, I really would like to know what's going on... I'm replacing the server to see if anything changes. Trev. -Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 04, 2001 10:45 AM To: Trevor Ouellette; E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? Trevor Ouellette [EMAIL PROTECTED] said: What files are required to reinstall the DHCP server? e-smith 4.12 uses: Server = dhcp-2.0-12.i386.rpm Client = dhcpcd-1.3.18pl8-6.i386.rpm Is this recommended? Don't know? Would be nice to solve why it is failing for you. I see the latest release available for both client/server is 3.0rc12. After appropriate testing in a non-production environment to make sure it works with e-smith, maybe an upgrade is in order? -- Darrell May DMC NETSOURCED.COM http://netsourced.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
What type of clients are you running? I recently found mention in the ISC FAQ on DHCP of a bug in the Win95 DHCP client that can cause a network to run out of IP addresses. Check their site for details (http://www.isc.org/products/DHCP/). Look in the FAQs for abandoned leases. This might not be the same problem you are having, but it sounds similar and might be worth checking. Scott -Original Message- From: Trevor Ouellette [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 04, 2001 11:57 AM To: E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? Sorry to re-hash this everyone, but we just lost another workstation (that makes 3 so far). They just can't get an IP address from the DHCP server. What files are required to reinstall the DHCP server? Is this recommended? Trev. -Original Message- From: John Powell [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 10:14 AM To: Trevor Ouellette; Graeme Robinson; John Powell Cc: E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? So, could the problem be with the DHCPD server? DHCP was working for a few months without any problems, now it stops recognizing NEW machines introduced to the system. I doubt it, but would rule nothing out. Going by your logs, the client is the one dropping the ball. To make it clearer, the normal init sequence looks like this: C: DHCPDISCOVER (client asking for IP) S: DHCPOFFER (server dishing out an IP) C: DHCPREQUEST (client accepting the offerred IP) S: DHCPACK (server finalizing the process) From your logs, the process gets through to the OFFER, which means it recognizes the client and is offering an IP. The client is not accepting it for some reason, not even NAKing it, which suggests either the client doesn't see the response, or is choking on it for some reason. It does not sound like a server problem. Even if the server is offering up junk, the client should NAK it. For one client computer... it worked the day before, the next day (poof), no IP address designation... strange. That is, indeed, strange. Is it possible to get a sniffer like trace of this in action? Ethereal is a fine choice, or any other product with a decent decoded output. You might also want to check out www.isc.com (makers of the DHCP server in e-smith) or a google search and see if they have some hints on known problems with Wintel clients. I don't know of any (ISC's server is generally solid as a rock). JP -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
-Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 04, 2001 12:45 PM Subject: RE: [e-smith-devinfo] DHCP Server Problem?? [snip] e-smith 4.12 uses: Server = dhcp-2.0-12.i386.rpm Client = dhcpcd-1.3.18pl8-6.i386.rpm [snip] I see the latest release available for both client/server is 3.0rc12. After appropriate testing in a non-production environment to make sure it works with e-smith, maybe an upgrade is in order? This, along with an update to bind-9.x, would also solve my DHCP/DNS issue of the client-hostname from DHCP not being registered with DNS. I know e-smith are looking at djbdns for future releases, but as bind9 is supposed to be a drop-in replacement for bind8, maybe it is worth looking at updating both. Scott -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Thanks for all the suggestions. I just got a private email from E-Smith/Mitel about DHCP. And I feel that the devlist is NOT the place for posting my DHCP server problems. Apologies all around. Trev. -Original Message- From: Smith, Jeffery S (Scott) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 04, 2001 11:09 AM To: '[EMAIL PROTECTED]'; E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? -Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 04, 2001 12:45 PM Subject: RE: [e-smith-devinfo] DHCP Server Problem?? [snip] e-smith 4.12 uses: Server = dhcp-2.0-12.i386.rpm Client = dhcpcd-1.3.18pl8-6.i386.rpm [snip] I see the latest release available for both client/server is 3.0rc12. After appropriate testing in a non-production environment to make sure it works with e-smith, maybe an upgrade is in order? This, along with an update to bind-9.x, would also solve my DHCP/DNS issue of the client-hostname from DHCP not being registered with DNS. I know e-smith are looking at djbdns for future releases, but as bind9 is supposed to be a drop-in replacement for bind8, maybe it is worth looking at updating both. Scott -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] BIND9 (was Re: [e-smith-devinfo] DHCP Server Problem??)
On Tue, Sep 04, 2001 at 01:08:49PM -0400, Smith, Jeffery S (Scott) [EMAIL PROTECTED] wrote: [...] This, along with an update to bind-9.x, would also solve my DHCP/DNS issue of the client-hostname from DHCP not being registered with DNS. FYI (and not solving your problem), if you assign static DHCP leases through the Hostnames and Addresses panel, this is not an issue. Dynamic updates from DHCP need to be looked at in more detail, as the BIND files are generated, so the dynamic updates may be lost. I know e-smith are looking at djbdns for future releases, but as bind9 is supposed to be a drop-in replacement for bind8, maybe it is worth looking at updating both. Emphasis on supposed to be :-) BIND9 is definitely pickier about config file syntax - I don't think we should have issues with the syntax of our BIND files, but BIND9 may pick us up on something. Thanks, Gordon -- Gordon Rowell[EMAIL PROTECTED] VP Engineering Network Server Solutions Group http://www.e-smith.com Mitel Networks Corporation http://www.mitel.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
[e-smith-devinfo] RE: BIND9 (was Re: [e-smith-devinfo] DHCP Server Problem??)
-Original Message- From: Gordon Rowell Sent: 9/4/2001 9:35 PM Subject: BIND9 (was Re: [e-smith-devinfo] DHCP Server Problem??) FYI (and not solving your problem), if you assign static DHCP leases through the Hostnames and Addresses panel, this is not an issue. And that is what I'm doing. I'm just trying to find a way to do it automagically, as that is the (almost?) always the better choice :-) Dynamic updates from DHCP need to be looked at in more detail, as the BIND files are generated, so the dynamic updates may be lost. Yes, I've been considering what one would do about active leases and their DNS, in the case an e-smith event is triggered that would rebuild named.conf. I suppose you could force the DHCP interface to re-run against a null file. Most of the solutions I've seen compare the current dhcp.leases to a ddns.leases file, the latter of which is a snapshot copy of dhcp.leases the last time the ddns update was run. By emptying the ddns.leases file, you'd force it to rebuild the DNS entries. I know e-smith are looking at djbdns for future releases, but as bind9 is supposed to be a drop-in replacement for bind8, maybe it is worth looking at updating both. Emphasis on supposed to be :-) Yeah, supposed to be :-) And the world was supposed to be flat! BIND9 is definitely pickier about config file syntax - I don't think we should have issues with the syntax of our BIND files, but BIND9 may pick us up on something. I take it from the lack of comment that there is not so much concern about DHCP v3.x? BIND9 may be pickier, but by all accounts (okay, about 45 minutes of web research) it is faster and more stable and more secure than BIND8. That's all opinion, though, I've not seen anyone offer up any real evidence in support of that. Maybe the test is to load them up and give it a whirl. I'm hoping to have a spare system available in the next couple of weeks. Unless someone else jumps on this before then, I may test it out when I have the spare available. Scott -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] DHCP Server Problem??
At 03:01 AM 30/08/2001 -0500, John Powell wrote: Sorry for the wishy-washy answer, but I am 99% sure your issue lies in this area (broadcast vs. unicast of the DHCPOFFER) and this might help you get pointed in the right direction. doesn't seem wishy washy to me John. I've experienced similar problems with some ageing powermacs on a 4.1.2 network. The problem has been side-stepped by giving them fixed IP addresses as you suggest but we also concluded (in the absence of other evidence) the clients pcs were not rewnewing their addresses correctly, either by not coping with NAC or ACK correctly. Interestingly they worked ok under the earlier redhat5.2 version of samba. The wintel boxes on the net have no dhcp problems (which is why we could confidently assign fixed IPs as a workaround). We did try to fix the problem by adding host entries assigning IPs by the MAC (Media Access Controller unique number) addresses of the macs \pun but I guess for the same reason that they made a hash of dynamic dhcp, dhcp hostnaming got simillar errors - ip conflict messages. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] DHCP Server Problem??
The problem might lay with the macintosh. I believe that system 8.5 fixed numerous bugs with 'Open Transport' (the networking software) and many DHCP issues fixed. Try updating your system softwaer or even better, upgrade to a nweer version such as 8.6 or OS9. James - Original Message - From: Graeme Robinson [EMAIL PROTECTED] To: John Powell [EMAIL PROTECTED]; Trevor Ouellette [EMAIL PROTECTED]; E-Smith Devinfo [EMAIL PROTECTED] Sent: Thursday, August 30, 2001 7:32 PM Subject: Re: [e-smith-devinfo] DHCP Server Problem?? At 03:01 AM 30/08/2001 -0500, John Powell wrote: Sorry for the wishy-washy answer, but I am 99% sure your issue lies in this area (broadcast vs. unicast of the DHCPOFFER) and this might help you get pointed in the right direction. doesn't seem wishy washy to me John. I've experienced similar problems with some ageing powermacs on a 4.1.2 network. The problem has been side-stepped by giving them fixed IP addresses as you suggest but we also concluded (in the absence of other evidence) the clients pcs were not rewnewing their addresses correctly, either by not coping with NAC or ACK correctly. Interestingly they worked ok under the earlier redhat5.2 version of samba. The wintel boxes on the net have no dhcp problems (which is why we could confidently assign fixed IPs as a workaround). We did try to fix the problem by adding host entries assigning IPs by the MAC (Media Access Controller unique number) addresses of the macs \pun but I guess for the same reason that they made a hash of dynamic dhcp, dhcp hostnaming got simillar errors - ip conflict messages. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Hi John, Your answer was not wishy-washy at all. Thanks for your input. One client was a computer brought in from another office. The other client computer is an older computer that just had it's hard drive replaced... that's when it couldn't get an IP address. I've double and triplechecked the settings and I just can't figure it out. We have even tried different cables (from a known-good workstation cable). Does anyone know how to uninstall and reinstall the DHCPD component? I've upgraded the server, to no avail. Thanks, Trev. -Original Message- From: John Powell [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 2:01 AM To: Trevor Ouellette; E-Smith Devinfo Subject: Re: [e-smith-devinfo] DHCP Server Problem?? Trevor, Is there something different about the 2 new machines (not a common OS, etc.)? I can tell you this, the broken clients are not seeing the responses from the server. the DHCPOFFER is the server responding, the client is supposed to accept the offer (and generate a DHCPREQUEST) or reject the offer (DHCPNAK), but obviously is not. The issue is likely to be with how the DHCPOFFER is addressed. Some servers broadcast the DHCPOFFER, some unicast it to the mac address of the requester. I believe the ISC server is a bit unique and broadcasts it (may be the other way around, I would need to sniff a connection to figure that out). I would need to read the RFC for the specifics, but I believe a client is supposed to accept either method, and it is likely your problem is your clients on the 2 broken machines are not accepting the method ISC uses. The simplest fix, of course, is to assign static IPs. The more complex is to see if there is updated DHCP software for your client. Sorry for the wishy-washy answer, but I am 99% sure your issue lies in this area (broadcast vs. unicast of the DHCPOFFER) and this might help you get pointed in the right direction. Hope this helps, JP --On Wednesday, August 29, 2001 7:48 PM -0600 Trevor Ouellette [EMAIL PROTECTED] wrote: I have a problem with 2 computers that have been introduced to the LAN. The ES server does not provide them with an IP address. It's not a physical network problem (they can see each other and was tested with working network cable, etc.). Here's the strange part... they request an IP address, but never receive one from the ES server. It even shows up in the logs. When I cd /etc/dhcpcd, I get a blinking dhcpc file. Is this normal? Could the DHCP Daemon have something to do with the problem? If you would like more logs, printouts, etc. please just ask... When I do a /etc/rc.d/init.d/dhcpd restart I get: /etc/rc.d/init.d/dhcpd restart Shutting down dhcpd: [ OK ] Starting dhcpd: SIOCADDRT: File exists [ OK ] Below is a SNIP from my log on a server that updates properly: Aug 29 13:36:59 normal dhcpd: DHCPDISCOVER from 00:00:b4:be:ee:c6 via eth0 Aug 29 13:37:00 normal dhcpd: DHCPOFFER on 192.168.1.65 to 00:00:b4:be:ee:c6 via eth0 Aug 29 13:37:00 normal dhcpd: DHCPREQUEST for 192.168.1.65 from 00:00:b4:be:ee:c6 via eth0 Aug 29 13:37:00 normal dhcpd: DHCPACK on 192.168.1.65 to 00:00:b4:be:ee:c6 via eth0 This is from the server that isn't providing proper DHCP IP addresses: Aug 29 19:32:34 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:35 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:40 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:40 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:46 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:46 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:52 broken dhcpd: DHCPDISCOVER from 00:40:d0:0a:ee:11 via eth0 Aug 29 19:32:52 broken dhcpd: DHCPOFFER on 192.168.1.104 to 00:40:d0:0a:ee:11 via eth0 Notice how they never get the DHCPREQUEST and DHCPACK for the addresses? Trev. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Hi Graeme, So, could the problem be with the DHCPD server? DHCP was working for a few months without any problems, now it stops recognizing NEW machines introduced to the system. The reason I'm bringing this up here, is to just see if this is isolated or if there may be a real issue to look at. For one client computer... it worked the day before, the next day (poof), no IP address designation... strange. Trev. -Original Message- From: Graeme Robinson [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 3:33 AM To: John Powell; Trevor Ouellette; E-Smith Devinfo Subject: Re: [e-smith-devinfo] DHCP Server Problem?? doesn't seem wishy washy to me John. I've experienced similar problems with some ageing powermacs on a 4.1.2 network. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Just for the record, one is a Windows ME system and the other is a Windows 98 computer. Trev. -Original Message- From: John Powell [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 2:01 AM To: Trevor Ouellette; E-Smith Devinfo Subject: Re: [e-smith-devinfo] DHCP Server Problem?? Trevor, Is there something different about the 2 new machines (not a common OS, etc.)? I can tell you this, the broken clients are not seeing the responses from the server. the DHCPOFFER is the server responding, the client is supposed to accept the offer (and generate a DHCPREQUEST) or reject the offer (DHCPNAK), but obviously is not. The issue is likely to be with how the DHCPOFFER is addressed. Some servers broadcast the DHCPOFFER, some unicast it to the mac address of the requester. I believe the ISC server is a bit unique and broadcasts it (may be the other way around, I would need to sniff a connection to figure that out). I would need to read the RFC for the specifics, but I believe a client is supposed to accept either method, and it is likely your problem is your clients on the 2 broken machines are not accepting the method ISC -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Trevor Ouellette [EMAIL PROTECTED] said: Just for the record, one is a Windows ME system and the other is a Windows 98 computer. Trev. Hi Trevor, I have one question to ask. Did these two workstations ever have a manually set IP address in operation? If they did then my guess is there are some lingering registry entries that are screwing things up for you. If DHCP is working for all other workstations and simply not for these two, I'd suggest the problem _appears_ workstation related. To isolate and determine where the fault is try these two suggestions: Temporarily replace the hard drive and load a fresh copy of WinME/98. Test DHCP and if it works, then it most likely is a WinME/98 registry error. Knowing this your choices would be to dive into the registry and clean things up or simply backup data, reformat and reinstall. To confirm the server is at fault a good test would be to connect the two workstation up to any DHCP capable device (another server, cheap firewall like a DLINK-701) and see if they pick up DHCP from this new server/device. If they do, maybe the server is at fault. If they don't it still points to a workstation fault. Hope this helps. -- Darrell May DMC NETSOURCED.COM http://netsourced.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
Thanks Darrell, Regarding your question, 1. The Windows 98 machine had a DHCP address and was working perfectly for a month. The next day, it's not resolving DHCP. It can communicate fine on the network with one other machine, so it's not physical. 2. The Windows ME machine just had it's hard drive replaced due to a crash... guess what, no DHCP IP address. That's why I'm starting to wonder... I will give your suggestions a try today, Darrell. Trev. -Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 9:22 AM To: Trevor Ouellette; E-Smith Devinfo Subject: RE: [e-smith-devinfo] DHCP Server Problem?? Trevor Ouellette [EMAIL PROTECTED] said: Just for the record, one is a Windows ME system and the other is a Windows 98 computer. Trev. Hi Trevor, I have one question to ask. Did these two workstations ever have a manually set IP address in operation? If they did then my guess is there are some lingering registry entries that are screwing things up for you. -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] DHCP Server Problem??
So, could the problem be with the DHCPD server? DHCP was working for a few months without any problems, now it stops recognizing NEW machines introduced to the system. I doubt it, but would rule nothing out. Going by your logs, the client is the one dropping the ball. To make it clearer, the normal init sequence looks like this: C: DHCPDISCOVER (client asking for IP) S: DHCPOFFER (server dishing out an IP) C: DHCPREQUEST (client accepting the offerred IP) S: DHCPACK (server finalizing the process) From your logs, the process gets through to the OFFER, which means it recognizes the client and is offering an IP. The client is not accepting it for some reason, not even NAKing it, which suggests either the client doesn't see the response, or is choking on it for some reason. It does not sound like a server problem. Even if the server is offering up junk, the client should NAK it. For one client computer... it worked the day before, the next day (poof), no IP address designation... strange. That is, indeed, strange. Is it possible to get a sniffer like trace of this in action? Ethereal is a fine choice, or any other product with a decent decoded output. You might also want to check out www.isc.com (makers of the DHCP server in e-smith) or a google search and see if they have some hints on known problems with Wintel clients. I don't know of any (ISC's server is generally solid as a rock). JP -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] DHCP Server Problem??
http://www.isc.org/ml-archives/dhcp-server/1999/07/msg00412.html http://www.isc.org/ml-archives/dhcp-server/1999/07/msg00422.html This is from the isc.org list and they are having a similar problem Yes, but that is on a 2 year old beta rev of 2.0 code and that particular problem seemed to have been solved in later beta code (all back in mid-1999). I guess it is easy enough to try out their suggestion of removing the subnet declaration (in /etc/dhcpd.conf), restart dhcpd, have the 2 machines retry dhcp (and fail), then rebuild the conf file using e-smith's expand-template command and restart dhcpd again. I don't think that will buy you much, but it can't hurt to try (stranger things have happened). I really do think you are going to want to get a sniff of this. Taking a close look at the DHCPDISCOVER and DHCPOFFER packets will likely provide some vital clues. If you hurry (I am out of the country for a week starting this Saturday) I would be glad to take a peek at them if you wish. BTW, though I do not think it is the issue, are you sure you are not out of addresses? Though I don't think the server would even respond if it is out of leases, I am not 100% sure of that. I hacked up a perl script I found (just changed the paths to match e-smith's) and it is available at http://www.jrp2.net/clease.pl , the code is documented and has lots of options, but if you run it with -d -s it shows useful info. Warning, it also shows expired leases and does not differentiate them. The lease file itself is pretty self-explanatory (/var/lib/dhcp/dhcpd.leases), but this script makes it a bit easier if you have a lot of entries. JP -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
