Printing from OS/2-SAMBA on network printer on NT-Server

[Lüko Willms]

I replaced IBM's TCPBEUI and PEER.EXE by SAMBA, I can access the
shared drives on my NT server, but I can't print anymore on the shared
printer attached to the NT server's LPT1.

What can I do to reestablish my printing possibilities?

In the OS/2 SAMBA, I can configure the local printers on my OS/2
system to be reachable as shared network printers from the Windows
stations in my LAN, but I can't see a way not the other way round.


Cheers,
L.W.

[Alex Taylor]

Post by Lüko Willms
I replaced IBM's TCPBEUI and PEER.EXE by SAMBA, I can access the
shared drives on my NT server, but I can't print anymore on the shared
printer attached to the NT server's LPT1.
What can I do to reestablish my printing possibilities?
In the OS/2 SAMBA, I can configure the local printers on my OS/2
system to be reachable as shared network printers from the Windows
stations in my LAN, but I can't see a way not the other way round.

Samba for OS/2 doesn't include a port driver for accessing network
printers yet (last I checked).

You can supposedly print from the command line using the 'smbspool' command.
Once you have that working, you can in theory use the 'eRedMan' port driver
to print to a pipe that redirects to smbspool.

From a post in the NetLabs Samba-user group:
------------------------------------------------------------------------
From: Herwig Bauernfeind <***@...>
Subject: Re: Creating a Samba port driver
Newsgroups: gmane.org.netlabs.samba.user
Date: 2007-09-11 14:13:18 GMT
...

Post by Lüko Willms
So what I'm thinking is: why not do the same thing to support
SMB/CIFS printing? Just take virtually the same driver, except
call SMBSPOOL with the correct parameters (instead of LPR), and
the Samba code in SMBSPOOL should take care of the rest.

Well, currently eRedMan can be used to do that: It creates a pipe as a
printer port, picks up the file and passes it to any program configured
to handle it.

http://members.aon.at/herwig.bauernfeind/eredman/eredman091.zip
Not as elegant, but by and large works well (as long as you don't feed
it with thousands of jobs).
------------------------------------------------------------------------

[Lüko Willms]

Am Thu, 15 Jan 2009 13:50:02 UTC, schrieb "Alex Taylor"
<***@reply.to.address> auf comp.os.os2.misc :

arigatoo for your reply.

Post by Alex Taylor

Post by Lüko Willms
In the OS/2 SAMBA, I can configure the local printers on my OS/2
system to be reachable as shared network printers from the Windows
stations in my LAN, but I can't see a way not the other way round.

Samba for OS/2 doesn't include a port driver for accessing network
printers yet (last I checked).

OK, I suspected that, but wasn't sure.

Post by Alex Taylor
You can supposedly print from the command line using the 'smbspool' command.
Once you have that working, you can in theory use the 'eRedMan' port driver
to print to a pipe that redirects to smbspool.

Hm. Maybe it is simpler to use LPR/LPD.

OK, I found the SMBSPOOL.EXE in the Samba directory. I found eRedMan
on the Web. Maybe I should look into that.

BTW, there is also a SMBPRINT.EXE, but calling it with a -? or /? it
tells me only that there is a "Invalid (non existent) print queue
specified in smb.conf: ''". I'm not sure how to set that up either. I
guess that is for _incoming_ printing, right? I have problems with
that, too.


Cheers,
L.W.

-- -----------------------------------------------------
Jetzt die 30-Stunden-Woche einführen bei vollem Lohnausgleich!

Post by Alex Taylor
<http://www.sockandawe.com> das online Buschuh-Spiel

[Alex Taylor]

Post by Lüko Willms

Post by Alex Taylor
You can supposedly print from the command line using the 'smbspool' command.
Once you have that working, you can in theory use the 'eRedMan' port
driver to print to a pipe that redirects to smbspool.

Hm. Maybe it is simpler to use LPR/LPD.

If it works for your environment, I would imagine it almost certainly is
(SLPR, in particular).

Post by Lüko Willms
BTW, there is also a SMBPRINT.EXE, but calling it with a -? or /? it
tells me only that there is a "Invalid (non existent) print queue
specified in smb.conf: ''". I'm not sure how to set that up either. I
guess that is for _incoming_ printing, right? I have problems with
that, too.

I don't know, sorry. I'm not really an expert on how Samba fits together.

[Herwig Bauernfeind]

Post by Lüko Willms
Am Thu, 15 Jan 2009 13:50:02 UTC, schrieb "Alex Taylor"
arigatoo for your reply.

Post by Alex Taylor

Post by Lüko Willms
In the OS/2 SAMBA, I can configure the local printers on my OS/2
system to be reachable as shared network printers from the Windows
stations in my LAN, but I can't see a way not the other way round.

Samba for OS/2 doesn't include a port driver for accessing network
printers yet (last I checked).

OK, I suspected that, but wasn't sure.

Post by Alex Taylor
You can supposedly print from the command line using the 'smbspool' command.
Once you have that working, you can in theory use the 'eRedMan' port driver
to print to a pipe that redirects to smbspool.

Hm. Maybe it is simpler to use LPR/LPD.
OK, I found the SMBSPOOL.EXE in the Samba directory. I found eRedMan
on the Web. Maybe I should look into that.

Start eredman /setup:smb and it should do most steps automagically.

Post by Lüko Willms
BTW, there is also a SMBPRINT.EXE, but calling it with a -? or /? it
tells me only that there is a "Invalid (non existent) print queue
specified in smb.conf: ''". I'm not sure how to set that up either. I
guess that is for _incoming_ printing, right?

Yes.

Post by Lüko Willms
I have problems with that, too.

smbprint.exe is a bridge between the Samba server and the OS/2 printing
subsystem.

If you use sscc.exe (the Samba Installer/configurator) and create a
shared printer it will configure smbprint.exe automagically for you.

In order to add it manually, add the following line in the section of
you shared printer in smb.conf:

print command = x:\SAMBA\smbprint.exe "%s" "%p" "%J" "%c" "%z"


Please note that the general problem with using Samba as a printer
server is that printing is a situation which especially suffers from the
EAGAIN problem which is also the reason for
http://svn.netlabs.org/samba/ticket/69 and
http://svn.netlabs.org/samba/ticket/71 . It definitely does work but it
is really slow.

Kind regards,
Herwig

[Lüko Willms]

Am Tue, 27 Jan 2009 06:46:39 UTC, schrieb Herwig Bauernfeind

Post by Herwig Bauernfeind

Post by Lüko Willms

Post by Alex Taylor
You can supposedly print from the command line using the 'smbspool' command.
Once you have that working, you can in theory use the 'eRedMan' port driver
to print to a pipe that redirects to smbspool.

Hm. Maybe it is simpler to use LPR/LPD.
OK, I found the SMBSPOOL.EXE in the Samba directory. I found eRedMan
on the Web. Maybe I should look into that.

Start eredman /setup:smb and it should do most steps automagically.

Actually it didn't.

I finally tried it, but already at the first invocation with
"eRedman /MAKEOBJ" or "eRedMan /SETUP:ePDF" there was an error:

"Line 36 of Pipe_properties_Create in eRedMan.VRM:
Call PB_PipeSave_Click;

I managed to manually set up a pipe for ePDF, but when I try to send
a testpage, it tells me only that no printer is associated with that
pipe.

"eRedMan /setup:smb" results in nothing.

When I start eredman from OS/2-Commander, it only changes the
Commander window into a grey area.

Trübe Aussichten.


MfG,
L.W.

[Peter Brown]

Hi

Post by Lüko Willms
Am Tue, 27 Jan 2009 06:46:39 UTC, schrieb Herwig Bauernfeind

Post by Herwig Bauernfeind

Post by Lüko Willms

Post by Alex Taylor
You can supposedly print from the command line using the 'smbspool' command.
Once you have that working, you can in theory use the 'eRedMan' port driver
to print to a pipe that redirects to smbspool.

Hm. Maybe it is simpler to use LPR/LPD.
OK, I found the SMBSPOOL.EXE in the Samba directory. I found eRedMan
on the Web. Maybe I should look into that.

Start eredman /setup:smb and it should do most steps automagically.

Actually it didn't.
I finally tried it, but already at the first invocation with
Call PB_PipeSave_Click;
I managed to manually set up a pipe for ePDF, but when I try to send
a testpage, it tells me only that no printer is associated with that
pipe.
"eRedMan /setup:smb" results in nothing.
When I start eredman from OS/2-Commander, it only changes the
Commander window into a grey area.
Trübe Aussichten.
MfG,
L.W.

I saw something about a samba client printer port being available
recently...

Looks like this may help
http://members.aon.at/herwig.bauernfeind/samba/#SambaPortDriver

Regards

Pete