I don't understand, dhcpd should just use the address of the NIC. How does it know "the address is already in use"? Perhaps there is more that one dhcpd running on the box. What does the log file say? What does the output from ifconfig say? What does your dhcpd.conf file say? Bill > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Mike Rambo > Sent: Thursday, October 19, 2000 4:37 PM > To: [EMAIL PROTECTED] > Subject: Re: [expert] syslog restarts and other wierdness > > > Jim Holthaus wrote: > > > > > > On Thu, 19 Oct 2000, Mike Rambo wrote: > > > the box refused to start the dhcp server daemon > > > with the error that it couldn't bind to the IP address > because it was > > > already in use. There is and was nothing else on the > same IP address as > > > the server but the only way I found to resolve that > problem was to put > > > the server on a different IP address. That's a wierd one > I've never > > > seen before. > > > > There was probably another computer on the subnet with the > same IP address. > > That was my first thought. We ended up getting a new hub out > of the van > and hooking the server up to that hub on the table which went > nowhere. > Rebooting the server yielded the same results - dhcpd still found the > address already in use. We then put the server back into the building > network and reset the IP address. After a reboot dhcpd > worked fine. We > pinged the original IP. Nothing was there. I don't know > what this was > but it definitely appeared to be something in the server itself to me. > > > > > > Now this morning I'm starting to get more complaints that > the access > > > problem has returned to some degree. Only a few > computers in the school > > > can access one of the important programs. > > > > Start by looking at what's changed since the system last > worked. Did you > > accidentally break something while trying to fix things > yesterday? Do all > > of the clients know the new address of the server? After > that, start working on > > network troubleshooting. Make sure your underlying > communications between the > > server and clients works. Once you are confident of this, > look at software > > specific problems like record locking. > > The only thing we changed was the server IP address. It appears the > last day the server really worked right was three (now four) > days ago. > At least that was when the complaints started and it > coincided with when > the log files started to show syslog restarts every 15 seconds or so. > We haven't changed anything on the server for almost a month and even > then the work was only to install some new software (math blaster or > something) in a shared folder. I'll look into the underlying network > when I next get out there - we did have a switch go down a couple of > weeks ago in another building. Possibility I guess. > > Thanks for the response. > > > -- > Mike Rambo > [EMAIL PROTECTED] > >
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
