See at the end of the hour if the box has requested/acquired another lease and pay special attention to the sequence of request and response between the box and DHCP server... Point is, set a short-term lease and then view the logs. That will give you a clear idea 'bout what's going on... I hope this is simple/clear enough
On 8/24/05, Dave Watkins <[EMAIL PROTECTED]> wrote: > Doesn't the box request a renewal of the least at 1/2 lease intervals? > > Eg: a 1 hour lease would result in a request from the box to renew the > lease after 1/2 hour. If no renewal if received then the system will > request > another from the server after another 15 minutes. If it's still not renewed > then another request for a renewal is sent after 7.5 minutes....... > > This continues till the lease either expires or is renewed. > > I THINK this is correct. > > FWIW > > Dave > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf > Of Cirez Communications, inc. > Sent: Wednesday, August 24, 2005 6:40 PM > To: CLUG General > Subject: [clug-talk] Re: Help: Connectivity Loss at 6 Hours > > Tell the box to re-request another lease and set it for one > hour...Then from another box(or the gateway) watch the traffic. See if > the box does request another lease at the end of the hour and pay > special attention to the sequence of request and response between the > box and DHCP server... > This will give you a clearer idea of the nature of the problem, rather > than poking in the dark... > > On 8/24/05, Gustin Johnson <[EMAIL PROTECTED]> wrote: > > > > Quoting Cameron Nikitiuk <[EMAIL PROTECTED]>: > > > > > Here is an interesting one that I have been working on for a couple > > weeks. > > > > > > I have a user who seems to lose connectivity at exactly 6 hours from > > > the time she logs onto her system. SHe is the only one that I know > > > of in the company that this is happening to. Her e-mail application > > > is usually the first one to register an error, syaing that she can't > > > access the file on the network share. It also sometimes generates an > > > error with regards to an appointment or something like that. > > > > > > I have tried moving her to a different port on the switch. No dice. > > > Tried repairing the application..nothing. I have ruled out DHCP as > > > the lease expires 12 hours after the error would occur. Done system > > > maintenance on the station...nothing there, checked memory & temp > > > files nothing. Tried recreating her email profile at least twice. > > > > > > SHe stores at lot of historical information in her email app and we > > > have tried to clean that up as much as we can. ANy reoccuring > > > tasks/appointments were recreated and old ones deleted. > > > > > > Just really at a loss and have scoured the web for hours trying to > > > find a solution and not even so much as a hint. ANyone want to take > > > a shot in the dark and throw some ideas my way? > > > > > > > > When she is having problems try some of the folowing: > > > > route print > > and > > arp -a > > > > Compare the results to someone else with a working workstation. Compare > > the > > output with when she is working to when she is not. Also verify that the > > problem occurs 6 hours after logon and not simply at the same time every > > day. > > What about another user of the same computer? > > > > I would check to see if there is anything in her startup folder > > (actually check > > all the startup folders). In addition, the registry keys: HKLM -> > Software > > -> > > Microsoft -> Windows -> Current Version -> Run as well as HKCU -> > Software > > -> > > Microsoft -> Windows -> Current Version -> Run contain paths to programs > > that > > are executed at startup/logon. Verify each program listed (ie. are they > > supposed to be there). > > > > I would also check out rootkit revealer from sysinternals. They have a > ton > > of > > useful utils for troubleshooting that Other OS. One of my favorite utils > > is > > Process Explorer > > (http://www.sysinternals.com/Utilities/ProcessExplorer.html), > > it is similar to Task Manager but more useful... or more accurately, it > > _is_ > > useful. It will tell what files and dlls a particular process is > > touching/using. > > > > I would also try changing the network card and perhaps as a last resort > > re-imaging the workstation aka Format & Reinstall. > > Hope this helps, > > -- > > No trees were harmed in the transmission of this message, however a > > large number > > of electrons were seriously inconvenienced. > > > > > > > > > > --------------------------------------------------- > > This message was sent using Echostar Secure Webmail > > > > > > > > > -- > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= > -------------------Cirez Communications, inc.---------------- > ----------------------Juan Alberto Cirez--------------------- > -----------------------Senior Consultant--------------------- > [EMAIL PROTECTED] > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= > Sunny and Beautiful Vancouver, Canada. > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > > > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= -------------------Cirez Communications, inc.---------------- ----------------------Juan Alberto Cirez--------------------- -----------------------Senior Consultant--------------------- [EMAIL PROTECTED] =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Sunny and Beautiful Vancouver, Canada. =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
