Cold weather & printers

[Mike Reinehr]

On Thursday 08 December 2005 10:02 am, Vu Pham wrote:
> > -----Original Message-----
> > From: linux-users-bounces at linux-sxs.org
> > [mailto:linux-users-bounces at linux-sxs.org] On Behalf Of Mike Reinehr
> > Sent: Thursday, December 08, 2005 9:18 AM
> > To: linux-users at linux-sxs.org
> > Subject: Re: Cold weather & printers
> >
> > On Thursday 08 December 2005 08:10 am, Vu Pham wrote:
> > > > -----Original Message-----
> > > > From: linux-users-bounces at linux-sxs.org
> > > > [mailto:linux-users-bounces at linux-sxs.org] On Behalf Of Net Llama!
> > > > Sent: Tuesday, December 06, 2005 2:59 PM
> > > > To: Linux tips and tricks
> > > > Subject: Re: Cold weather & printers
> > > >
> > > > On Tue, 6 Dec 2005, Vu Pham wrote:
> > > > > Can the cold weather have anything to do with the
> >
> > printer problem ?
> >
> > > > Most definitely.  Keep in mind that printers need to warm up when
> > > > first powered on.
> > >
> > > It is. This morning it is around 30 F again, and I just got a call
> > > about the same problem.
> > >
> > > Vu
> >
> > 	Vu,
> >
> > Is this a laser printer, and, is it programmed to go into an
> > energy saving mode after a period of inactivity. If so,
> > perhaps disabling the energy saving mode, might help.
>
> Yes, I tried it but it doesn't help.
>
> The tcpdump outsput shows the packets are so cold that they are corrupted
> <g>. You can see below that the printer sent the Reset back to the server.
>
> [root at pepper root]# tcpdump -n -i eth1 host 192.168.248.65
> tcpdump: listening on eth1
> 10:06:43.810021 192.168.248.65.jetdirect > 192.168.249.22.48318: R 0:0(0)
> win 5840
> 10:07:01.804723 192.168.249.22.48318 > 192.168.248.65.jetdirect: S
> 869779140:869779140(0) win 5840 <mss 1460,sackOK,timestamp 726552935
> 0,nop,wscale 0> (DF)
> 10:07:31.807759 192.168.248.65.jetdirect > 192.168.249.22.48318: R 0:0(0)
> win 5840
> 10:09:07.814764 192.168.249.22.48321 > 192.168.248.65.jetdirect: S
> 1102104625:1102104625(0) win 5840 <mss 1460,sackOK,timestamp 726565536
> 0,nop,wscale 0> (DF)
> 10:09:10.814712 192.168.249.22.48321 > 192.168.248.65.jetdirect: S
> 1102104625:1102104625(0) win 5840 <mss 1460,sackOK,timestamp 726565836
> 0,nop,wscale 0> (DF)
> 10:09:16.814714 192.168.249.22.48321 > 192.168.248.65.jetdirect: S
> 1102104625:1102104625(0) win 5840 <mss 1460,sackOK,timestamp 726566436
> 0,nop,wscale 0> (DF)
> 10:09:28.814718 192.168.249.22.48321 > 192.168.248.65.jetdirect: S
> 1102104625:1102104625(0) win 5840 <mss 1460,sackOK,timestamp 726567636
> 0,nop,wscale 0> (DF)
> 10:09:37.816752 192.168.248.65.jetdirect > 192.168.249.22.48321: R 0:0(0)
> win 5840
>
> I thought the temperature could only affect the mechanics part, not the
> eletronics.
>
> Vu

	I don't have any experience with tcpdump so I'm not sure what the above dump 
should be telling me, but within normal extremes I would agree. But this 
still could be a mechanical problem. At these low temperatures, perhaps, the 
Jetdirect circuit card is not making good contact within it's slot. You could 
try unplugging it, cleaning all the contacts well and re-seating it. 
Likewise, any other mechanical connections of electronic components in the 
printer.

	Hey, if you can not locate a heater near the printer you always could wrap it 
in a blanket! ;-)

Cheers!

cmr

-- 
Debian 'Sarge': Registered Linux User #241964

"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC