Date: Fri, 11 Feb 2000 12:34:16 +0000 From: Nik Clayton <nik@freebsd.org> To: questions@freebsd.org, stable@freebsd.org Subject: FreeBSD 3.4, Samba, HP LaserJet 5N, delays, reboots Message-ID: <20000211123416.A92889@catkin.nothing-going-on.org>
next in thread | raw e-mail | index | archive | help
Hi folks,
[x-posted to -stable, I explain why below]
God knows where the problem is in this particular set up, I'm hoping this
rings a bell with someone.
I've got a FreeBSD 3.4 machine running Samba 2.0.6, right out of the
ports tree. This machine is the PDC for 5 Windows 98 machines, and
things work well -- log ins, file sharing, and so forth.
There's also an HP LaserJet 5N on this network, and the Windows machines
need to print to it.
I've got it set up and connected to the network (i.e., it's *not*
connected by a parallel connection to any of the other machines) and
an /etc/printcap entry on the FreeBSD machine which simply forwards all
jobs to the LPD on the printer (i.e., with an 'rm=' entry). With a
'[printers]' section in smb.conf, this just works. Windows 98 machines
can print to it, jobs appear in the spooler, jobs can be cancelled, and so on.
The FreeBSD and Windows machines all have 100MB NICs, the printer has a
10MB NIC, and they're connected using a NetGear 16 port hub.
However, there's one snag. As soon as there's more than one print job
in the queue (either 2 or more jobs from one machine, or 2 or more jobs
from multiple machines) the applications that are printing on each host
hang (hourglass, unresponsive to input) until the print jobs have gone
through. The Windows 98 hosts have the most up to date drivers from HP.
I've not seen this before.
Thinking that the LPD on the printer might not be up to snuff, I tried
connecting to the printer directly to the FreeBSD machine, and using a
'raw' printcap entry just to pass jobs down the parallel port untouched.
After restarting everything, I tried printing from a Windows machine.
Boom. The FreeBSD machine spontaneously reboots, with no console messages,
and nothing in the log. I try it again, just to be sure, and the same
thing happens.
I've x-posted this to -stable because I've got dim memories of someone
else reporting similar problems in the past fortnight or so. But with
the mailing list search engines being down I can't go back to check.
FWIW, I've done similar setups, with with Epson stylus printers connected
to a FreeBSD -stable machine, and printing through Samba, and haven't
seen anything like this.
At this point I'm pretty much clutching at straws. It could be a
FreeBSD lpd / HP lpd interaction problem; it might be a Windows 98
problem; it might be a 100MB/10MB problem. . .
And I'm concerned that printing from Windows to FreeBSD can cause FreeBSD
to reboot.
I've done the usual deja.com/google.com/hp.com searches, and haven't
turned up anything concrete.
Any ideas?
N
--
If you want to imagine the future, imagine a tennis shoe stamping
on a penguin's face forever.
--- with apologies to George Orwell
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000211123416.A92889>