You might want to download a free sniffer and try to see what's going on. Also, look at nbt and netstats (included in windows 2000).
JH -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James E Harvey Sent: Thursday, May 17, 2007 7:18 AM To: 'ProFox Email List' Subject: RE: [NF] Problematic DHCP Not that I can tell Jack. I even took a flashlight over to the barn area and was climbing up in the loft to follow wires just to make sure that wasn't the case. If someone has done that I can't seem to find it... We do have about 5 "switches" on the system to areas where it didn't make sense to run many Ethernet cables, but these are just the switches you buy at Staples for $100.00 bucks, a step above an old fashioned "hub". 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 Jack Skelley Sent: Wednesday, May 16, 2007 5:09 PM To: [email protected] Subject: Re: [NF] Problematic DHCP James: I've been following this thread. Has someone on the network brought their own router and plugged it into your network and using it like a switch with DHCP turned on? Regards, Jack Skelley James E Harvey wrote: > DHCP is being done by the file server, and yes we've rebooted it several > times, but to no avail :( > > > > 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 Michael Madigan > Sent: Wednesday, May 16, 2007 2:27 PM > To: ProFox Email List > Subject: Re: [NF] Problematic DHCP > > Have you rebooted the server lately? > > > > > > --- Richard Kaye <[EMAIL PROTECTED]> wrote: > > >>It's been too long since I managed one of those. >>Usually, when this kind >>of behavior happened, restarting the DHCP service >>cleared it up. Check >>the MSKB for info on how to check the health of the >>DHCP database. >> >>James E Harvey wrote: >> >>>DHCP is provided by our file server, Win2000 >> >>Server. It is suppose to be >> >>>the only one on the networked doing this. >>> >>>We have an Exchange on a different box, same OS, >> >>but it isn't handing out IP >> >>>addresses. >>> >>>I haven't tried the start/stop option, but will do >> >>that this evening. >> >>>How would I tell if the database was corrupt? >>> >>> >>> >>>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 Richard Kaye >>>Sent: Wednesday, May 16, 2007 2:03 PM >>>To: [email protected] >>>Subject: Re: [NF] Problematic DHCP >>> >>>A few thoughts... >>> >>>Assuming the DHCP service is being provided by >> >>Windows ( I don't think >> >>>you've said), have you tried stopping and >> >>restarting the DHCP service? >> >>>Also, the database for the Windows DHCP service is >> >>subject to >> >>>corruption. IIRC it uses the Jet engine. Do you >> >>have more than one >> >>>Windows DHCP server on your network? If so, are >> >>they each set to supply >> >>>addresses in a unique range? >>> >>>James E Harvey 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????? >> >>>> >>>> >>> >>> >> >>-- >>Richard Kaye >>Vice President >>Artfact/RFC Systems >>Voice: 617.219.1038 >>Fax: 617.219.1001 >> >>For the fastest response time, please send your >>support >>queries to: >> >>Technical Support - [EMAIL PROTECTED] >>Australian Support - [EMAIL PROTECTED] >>Internet Support - [EMAIL PROTECTED] >>All Other Requests - [EMAIL PROTECTED] >> >> > > --------------------------------------------------------- > >>This message has been checked for viruses before >>sending. >> > > --------------------------------------------------------- > >> >> >>_______________________________________________ >>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. >> > > > > [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]@shelbynet.com ** 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.
