[53566] in Hotline Meeting
case 198315: M37-332-4 Conflicting Mac.Address
daemon@ATHENA.MIT.EDU (computing-help@MIT.EDU)
Tue Jan 23 10:06:59 2001
From: computing-help@MIT.EDU
Mime-Version: 1.0
Message-Id: <p05010401b6934c5f1fea@[24.128.141.52]>
Date: Tue, 23 Jan 2001 10:06:52 -0500
To: "Louis A. Isgur" <larugsi@MIT.EDU>
Cc: computing-help@MIT.EDU, hotline@MIT.EDU, hardserv@MIT.EDU
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
If you want us to find the conflicting machine, our best bet is to
catch it in the act. Then we can try to trace which hub/switch port
it's on, and hopefully we'll know which physical location is wired to
that port.
Right now, I see a different MAC address (08002099ed8d) sitting on
18.78.0.55. Presumably this is the Athena workstation.
I'll poke through the router's arp cache and see if 0005029b9192
shows up under another IP address.
Chris Griffith
MIT Voice/Data Service Team
>Date: Mon, 22 Jan 2001 21:52:46 -0500
>To: computing-help@MIT.EDU
>From: "Louis A. Isgur" <larugsi@MIT.EDU>
>Cc: hotline@MIT.EDU, hardserv@MIT.EDU
>Subject: M37-332-4 Conflicting Mac.Address
>
>
>Hi all,
>You may or may not have received this the first time, but I will resend
>it again. Hotline/Casetracker encountered some mail problems this evening, and
>I still have not been copied on the mail.
>Anyways, over the past month, M37-332-4 has been called in many times as being
>down, and not allowing logins. This evening I have found the mac. address of
>(00:05:02:9B:91:92) as being the culprit trying to use the IP address of
>18.78.0.55. Please let hotline know if you are able to isolate the culprit, or
>if we are better off issuing another IP address to the system.
>Thanks,
>--Lou
