Quoting "Cirez Communications, inc." <[EMAIL PROTECTED]>:
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...
This may not give you any relevant info, especially if the DHCP server is awindows server in which case you then have to install pcap and ethereal just to
begin monitoring. For me this required a reboot of my 2k box which is notreally an option during the work day. Also, the misbehaving box may or may not be spewing any informative packets either. You are then waiting an hour to see
if you may or may not have any additional information. All the steps I outlined can be done in less than an hour. The fact that only a single machine is exibiting any symptoms is why I focused on that machine. The nature of the problem indicates a software issue (I havenever encountered any NICs that failed after some specific length of time after
every login). Best of luck with the problem. __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
pgp9tTTv3JebM.pgp
Description: PGP Digital Signature
_______________________________________________ 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
