I have three machines connected together on a tiny LAN. Like this:

A---B---C

A runs either Windows 95 or RHL 9.
B runs RHEL 3 ES with SAMBA on it.
C runs RHL 7.3 with a printer on it.

Until the latest major update to B (I got 180 packages) when A runs
Windows 95, Windows applications could print on C. After the update, they
cannot.

B can print on C just fine, so that hardware connection is OK.
When A runs RHL9 it can print on C just fine, so I infer that there is no
coincidental hardware problem.

Now among the 180 packages that were updated,
Samba, Samba-client, Samba-common, and Samba-swat were all updated to
3.0.6-2.3E.i386.rpm.

Any idea what changed in there to stop printing?
/etc/samba/smbpasswd is the only one that changed in that directory.
The part of samba that allows Windows on C to examine (some) files on B is
working; i.e., B is in the Network Neighborhood of C.

--
.~.  Jean-David Beyer           Registered Linux User 85642.
/V\                             Registered Machine   241939.
/( )\ Shrewsbury, New Jersey     http://counter.li.org
^^-^^ 00:35:00 up 11:18, 3 users, load average: 4.23, 4.17, 4.08

[ Post a follow-up to this message ]

Jean-David Beyer wrote:
> I have three machines connected together on a tiny LAN. Like this:
>
> A---B---C
>
> A runs either Windows 95 or RHL 9.
> B runs RHEL 3 ES with SAMBA on it.
> C runs RHL 7.3 with a printer on it.
>
> Until the latest major update to B (I got 180 packages) when A runs
> Windows 95, Windows applications could print on C. After the update,
> they cannot.
>
> B can print on C just fine, so that hardware connection is OK.
> When A runs RHL9 it can print on C just fine, so I infer that there is
> no coincidental hardware problem.
>
> Now among the 180 packages that were updated,
> Samba, Samba-client, Samba-common, and Samba-swat were all updated to
> 3.0.6-2.3E.i386.rpm.
>
> Any idea what changed in there to stop printing?
> /etc/samba/smbpasswd is the only one that changed in that directory.
> The part of samba that allows Windows on C to examine (some) files on B
> is working; i.e., B is in the Network Neighborhood of C.
>
Still no answer, but more data: Samba on machine B complains:

smbd/service.c:make_connection_snum(648)  touchw (192.168.2.2) connect to
service lp initially as user jdbeyer (uid=500, gid=500) (pid 11689)lpr:
unable to print file:
+client-error-document-format-not-supportedlpr: unable to print file:
client-error-document-format-not-supported : 1 Time(s)
smbd/service.c:make_connection_snum(648)  touchw (192.168.2.2) connect to
service lp initially as user jdbeyer (uid=500, gid=500) (pid 8821)lpr:
unable to print file: client-error-document-format-not-supported
+: 4 Time(s)
smbd/service.c:make_connection_snum(648)  touchw (192.168.2.2) connect to
service lp initially as user jdbeyer (uid=500, gid=500) (pid 8821)lpr:
unable to print file:
+client-error-document-format-not-supportedlpr: unable to print file:
client-error-document-format-not-supported : 1 Time(s)

That should be telling me something, but as the client (machine C, a.k.a.
touchw) has not been changed since the last time Red Hat issued updates
with up2date for RHL9, and since the Samba server machine (machine B) was
most recently updated yesterday, I very much doubt this is a problem with
the client.

--
.~.  Jean-David Beyer           Registered Linux User 85642.
/V\                             Registered Machine   241939.
/( )\ Shrewsbury, New Jersey     http://counter.li.org
^^-^^ 09:40:00 up 20:23, 4 users, load average: 4.23, 4.20, 4.15

[ Post a follow-up to this message ]