PC rebooted, still wants to print. Help?

PROBLEM:

I've got a workstation and a firewall/hub/print server that works with
lpr commands sent against it. The print server no longer has a printer
on it. I previously, mistakingly, sent an lpr request against it while
writing a program that needed to print. Now, every so many minutes in
my event log, I get this MAC error that someone has already broken
down for me as my computer trying to print. This continues even if I
turn my workstation off and back on again. How do I stop this job? I
don't see how. Everything I look at is empty.

Mike

BACKGROUND:

From: Moe Trin ((E-Mail Removed))
Subject: Re: Strange Mac Errors in System Log on RH9

Newsgroups: comp.os.linux.redhat
Date: 2004-09-06 13:06:57 PST

In article <(E-Mail Removed) >, Google
Mike
wrote:
>I've got RH9. I'm seeing some strange MAC errors over and over in my
>system log. What could I have done to my system to cause this?

Good question. Maybe nothing.

>Sep 5 18:10:53 mylinux kernel: IN=eth0 OUT=
>MAC=00:01:03:d6:4f:03:00:c0:49:d4:6e:c5:08:00

00:01:03:d6:4f:03 Destination hardware address
00:c0:49:d4:6e:c5 Source hardware address
08:00 Ethernet datagram

[compton ~]$ etherwhois 00:01:03
00-01-03 (hex) 3COM CORPORATION
000103 (base 16) 3COM CORPORATION
5400 Bayfront Plaza - MS: 4220
Santa Clara CA 95052
UNITED STATES
[compton ~]$ etherwhois 00:c0:49
00-C0-49 (hex) U.S. ROBOTICS, INC.
00C049 (base 16) U.S. ROBOTICS, INC.
8100 NORTH MCCORMICK BLVD.
SKOKIE IL 60076-2999

00C049 US Robotics Total Control (tm) NETServer Card
[compton ~]$

> SRC=192.168.100.1
>DST=192.168.100.12 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=56848
PROTO=TCP

yada, yada, yada

>SPT=515 DPT=810

[compton ~]$ grep 515 /etc/services
printer 515/tcp spooler # BSD lpd(8)
[compton ~]$

Print spooler sending, but 810... from
http://www.iana.org/assignments/port-numbers

fcp-udp 810/tcp FCP
fcp-udp 810/udp FCP Datagram
# Paul Whittemore <(E-Mail Removed)>

Now, I have no idea why the box with the 3Com card (192.168.100.12)
wants to talk from port 810. You might be able to use 'lsof' or
'fuser'
on that system to find out what process is using that port. The
acronym
'FCP' or company 'softarc' doesn't ring a bell.

>WINDOW=0 RES=0x00 ACK RST URGP=0

That's a FOAD message - TCP windoze size to zero (don't talk to me),
ACK
(yeah, I heard you), "RST" = "go away kid, you bother me".

So - in translation, something on the box with the 3Com wants to send
something to the line printer it thinks is running on the box with the
NETServer card (192.168.100.1). That box isn't running a printer
daemon,
or doesn't want 192.168.100.12 printing, and is telling it to go away.

Solution: find out why 192.168.100.12 wants to print _OR_ find out
why
192.168.100.1 doesn't want to hear that crap.

Old guy

In article <(E-Mail Removed) >, Google Mike wrote:

>I've got a workstation and a firewall/hub/print server that works with
>lpr commands sent against it. The print server no longer has a printer
>on it. I previously, mistakingly, sent an lpr request against it while
>writing a program that needed to print.

Did you try the 'lsof' or 'fuser' to see what daemon it was that was
trying to send the packet?

>This continues even if I turn my workstation off and back on again. How
>do I stop this job?

[compton ~]$ apropos lpr
lpr (1) - off line print
lprm (1) - remove jobs from the line printer spooling queue
[compton ~]$

The job is in a queue _somewhere_ (if you used 'lpr', there is an 'lpq'
that you can run as the same user), and killing the power doesn't alter
that.

>I don't see how. Everything I look at is empty.

Depends on how you set up the printer system. Usually, the spool is
located below /var/spool/, but lprm (or it's CUPS equivalent) is the
best way to clean up the mess.

Old guy