[46198] in Hotline Meeting
Re: Case 128784: HP Printer
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Thu Dec 17 13:17:26 1998
To: hotline@MIT.EDU
Cc: smyser@MIT.EDU, hesreq@MIT.EDU, tregan@MIT.EDU
Reply-To: hesreq@MIT.EDU
In-Reply-To: Your message of "Thu, 17 Dec 1998 09:08:26 EST."
<199812171408.JAA21087@team-usa.MIT.EDU>
Date: Thu, 17 Dec 1998 13:17:16 EST
From: Garry Zacheiss <zacheiss@MIT.EDU>
>> This problem surfaced in the BLT space as the customer tries to print
>> to CSR1 and nothing comes out. During troubleshooting I watched jobs
>> enter and leave the athena queue from SAP and from my athena account;
>> paper never printed according to the customer. I had her powercycle the
>> printer. Then I sent all the test jobs again -- still nothing prints.
>> CSR1 does ping. It refuses telnet connections, so I assume it has been
>> set up for bootp.
>>
>> Is there something that needs to be kicked in the bootp file perhaps?
>> The customer is teresa santiago at the Center for Space Research,
>> teresa@mit. The BLT case number is 128749.
>>
>> let me know if there's anything you can do.
I investigated this problem today and discovered that whatever
device is responding to the pings sent to csr1.mit.edu does not have the
Ethernet Hardware address we were given when csr1 was originally
configured for bootp. The hardware address we have is:
080009b6c11c
and the host currently up as csr1.mit.edu has hardware address:
000502ee4e00
I would imagine that one of two things is possible. Either the
IP address assigned to csr1 has been stolen, or else the printer's
network card was replaced with a different one, and that card was
manually configured to have the IP address of csr1. In either case,
csr1 isn't getting bootp configuration. If the printer has actually
been replaced with a newer one and the current hardware address is
correct, please let us know and we'll update our configuration for that
printer, which should fix the problem.
Garry Zacheiss
MIT I/S, Athena Server Operations
