Discussion:
LAN with OS/2 and Windows nodes
(too old to reply)
Fred Blau
2007-11-29 23:40:28 UTC
Permalink
My OS/2 desktop and laptop machines connect by cable through a Linksys
WRT54G router using netbios with no problems. (My laptop can also
connect by wi-fi, but this is not quite as error-free.) However, my
wife wants to add her new WinXP laptop to the LAN, and she would like to
use the printer which is presently attached by USB to my desktop
machine. I have the following questions.

1. Do I need to switch protocols from netbios to netbeui? If so, is
there any downside to this? If not, what has to be done on/to the WinXP
machine?

2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?

3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?

4. If a print server is a good approach, any recommendations for
specific brands and or models?

5. Have I missed anything important?
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Bob Eager
2007-11-30 00:31:05 UTC
Permalink
Post by Fred Blau
1. Do I need to switch protocols from netbios to netbeui? If so, is
there any downside to this? If not, what has to be done on/to the WinXP
machine?
Bit of mixed terminology there. Using the names of the drivers (which is
not strictly the correct term, but is unambiguous here):

NETBEUI - straight NETBIOS (what it's called in the MPTS setup)
TCPBEUI - NETBIOS over TCP/IP (what MPTS calls it)

You can use either, but these days it's best to use TCPBEUI, as NETBEUI
is no lobger officially supported by Windows. Also, if you need to
communicate with a UNIX box (or an imitation such as Linux) running
Samba, you'll need TCPBEUI. Also, you can route TCPBEUI and youi can't
route NETBEUI.

If you really want to use NETBEUI, fire up Help in WinXP and type in
NETBEUI. You'll get the necessary instructions about files to add. Then
configure normally.
Post by Fred Blau
2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?
Yes, pretty much. You need a driver for it on the client machine,
though. In fact, if you have WinXP Pro you can do it more neatly (IMHO)
by using SLPR on the OS/2 end, and a UNIX style network port (LPR) on
WinXP.
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
Fred Blau
2007-11-30 19:11:35 UTC
Permalink
Post by Bob Eager
Post by Fred Blau
1. Do I need to switch protocols from netbios to netbeui? If so, is
there any downside to this? If not, what has to be done on/to the WinXP
machine?
Bit of mixed terminology there. Using the names of the drivers (which is
NETBEUI - straight NETBIOS (what it's called in the MPTS setup)
TCPBEUI - NETBIOS over TCP/IP (what MPTS calls it)
You can use either, but these days it's best to use TCPBEUI, as NETBEUI
is no lobger officially supported by Windows. Also, if you need to
communicate with a UNIX box (or an imitation such as Linux) running
Samba, you'll need TCPBEUI. Also, you can route TCPBEUI and youi can't
route NETBEUI.
Thanks, Bob. I just spent several hours switching to NETBIOS OVER
TCP/IP on my desktop machine. (IBM did not make it easy for the
novice.) It seems to be working, but I am not sure I did it right.
Presently I have on logical adapter0 TCP/IP and NETBIOS OVER TCP/IP, but
I also have straight NETBIOS on logical adapter1. I have just one
physical adapter. Should I have both NETBIOS and NETBIOS OVER TCP/IP?
I thought that I would be exchange one protocol for the other.

My next step is to work on my OS/2 laptop, which should be similar to
the desktop other than that it also has a wi-fi adapter. Then the WinXP
laptop, which also has a wi-fi adapter.

I still have some questions about using the printer, but I will ask them
later.

Thanks again for your help.
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Bob Eager
2007-11-30 19:52:35 UTC
Permalink
Post by Fred Blau
Post by Bob Eager
Post by Fred Blau
1. Do I need to switch protocols from netbios to netbeui? If so, is
there any downside to this? If not, what has to be done on/to the WinXP
machine?
Bit of mixed terminology there. Using the names of the drivers (which is
NETBEUI - straight NETBIOS (what it's called in the MPTS setup)
TCPBEUI - NETBIOS over TCP/IP (what MPTS calls it)
You can use either, but these days it's best to use TCPBEUI, as NETBEUI
is no lobger officially supported by Windows. Also, if you need to
communicate with a UNIX box (or an imitation such as Linux) running
Samba, you'll need TCPBEUI. Also, you can route TCPBEUI and youi can't
route NETBEUI.
Thanks, Bob. I just spent several hours switching to NETBIOS OVER
TCP/IP on my desktop machine. (IBM did not make it easy for the
novice.) It seems to be working, but I am not sure I did it right.
Presently I have on logical adapter0 TCP/IP and NETBIOS OVER TCP/IP, but
I also have straight NETBIOS on logical adapter1. I have just one
physical adapter. Should I have both NETBIOS and NETBIOS OVER TCP/IP?
I thought that I would be exchange one protocol for the other.
I would just change them over, unless you need both for backwards
compatibility.
Fred Blau
2007-11-30 20:01:17 UTC
Permalink
Post by Bob Eager
Post by Fred Blau
Post by Bob Eager
Post by Fred Blau
1. Do I need to switch protocols from netbios to netbeui? If so, is
there any downside to this? If not, what has to be done on/to the WinXP
machine?
Bit of mixed terminology there. Using the names of the drivers (which is
NETBEUI - straight NETBIOS (what it's called in the MPTS setup)
TCPBEUI - NETBIOS over TCP/IP (what MPTS calls it)
You can use either, but these days it's best to use TCPBEUI, as NETBEUI
is no lobger officially supported by Windows. Also, if you need to
communicate with a UNIX box (or an imitation such as Linux) running
Samba, you'll need TCPBEUI. Also, you can route TCPBEUI and youi can't
route NETBEUI.
Thanks, Bob. I just spent several hours switching to NETBIOS OVER
TCP/IP on my desktop machine. (IBM did not make it easy for the
novice.) It seems to be working, but I am not sure I did it right.
Presently I have on logical adapter0 TCP/IP and NETBIOS OVER TCP/IP, but
I also have straight NETBIOS on logical adapter1. I have just one
physical adapter. Should I have both NETBIOS and NETBIOS OVER TCP/IP?
I thought that I would be exchange one protocol for the other.
I would just change them over, unless you need both for backwards
compatibility.
I don't need backwards compatibility. So guess you mean that I can
simplify my setup by getting rid of straight NETBIOS (which is what I
thought in the first place) and having no reference to logical adapter1
(aka NET2 in ibmlan.ini). I suppose there are some lines in config.sys
that can be deleted, but I'm not sure which ones. I'll try some
guesses.
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Bob Eager
2007-11-30 20:28:58 UTC
Permalink
Post by Fred Blau
Post by Bob Eager
Post by Fred Blau
Post by Bob Eager
Post by Fred Blau
1. Do I need to switch protocols from netbios to netbeui? If so, is
there any downside to this? If not, what has to be done on/to the WinXP
machine?
Bit of mixed terminology there. Using the names of the drivers (which is
NETBEUI - straight NETBIOS (what it's called in the MPTS setup)
TCPBEUI - NETBIOS over TCP/IP (what MPTS calls it)
You can use either, but these days it's best to use TCPBEUI, as NETBEUI
is no lobger officially supported by Windows. Also, if you need to
communicate with a UNIX box (or an imitation such as Linux) running
Samba, you'll need TCPBEUI. Also, you can route TCPBEUI and youi can't
route NETBEUI.
Thanks, Bob. I just spent several hours switching to NETBIOS OVER
TCP/IP on my desktop machine. (IBM did not make it easy for the
novice.) It seems to be working, but I am not sure I did it right.
Presently I have on logical adapter0 TCP/IP and NETBIOS OVER TCP/IP, but
I also have straight NETBIOS on logical adapter1. I have just one
physical adapter. Should I have both NETBIOS and NETBIOS OVER TCP/IP?
I thought that I would be exchange one protocol for the other.
I would just change them over, unless you need both for backwards
compatibility.
I don't need backwards compatibility. So guess you mean that I can
simplify my setup by getting rid of straight NETBIOS (which is what I
thought in the first place) and having no reference to logical adapter1
(aka NET2 in ibmlan.ini). I suppose there are some lines in config.sys
that can be deleted, but I'm not sure which ones. I'll try some
guesses.
Yes, that's right. If you use MPTS Configuration to do it, it'll remove
the stuff in CONFIG.SYS. You also need to remove the relevant line in
IBMLAN.INI, as you say.
Philip Nienhuis
2007-12-01 22:09:29 UTC
Permalink
<snip>
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
Quite a few printer servers talk plain, TCP/IP, NETBEUI and IPX/SPX and
perhaps even more protocols.
Just TCP/IP would be enough to use a printer server.

Just to illustrate that: I have a HP170 X printer server here in my home
LAN. It is run using just plain TCP/IP.
I found that it got hung due to using the old HP JetAdmin (v.3.42) stuff
on the Windows side (probably due to some Windows hotfixes as it used to
work OK in the past) - I use a plain TCP/IP printer port now.
On the OS/2 (ECS) side JetAdmin works better; though I use SLPR nowadays.

Philip
Fred Blau
2007-12-03 20:01:29 UTC
Permalink
Post by Philip Nienhuis
<snip>
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
Quite a few printer servers talk plain, TCP/IP, NETBEUI and IPX/SPX and
perhaps even more protocols.
Just TCP/IP would be enough to use a printer server.
Thanks, Philip. That would be perfect for me. After Bob Eager's
explanations, I have now switched my LAN from straight NETBIOS to
NETBIOS OVER TCP/IP. (The PEER by wi-fi is still not functional, but it
was never very good on my system. Since PEER works by cable, I can copy
files over the LAN just fine.)
Post by Philip Nienhuis
Just to illustrate that: I have a HP170 X printer server here in my home
LAN. It is run using just plain TCP/IP.
I found that it got hung due to using the old HP JetAdmin (v.3.42) stuff
on the Windows side (probably due to some Windows hotfixes as it used to
work OK in the past) - I use a plain TCP/IP printer port now.
I don't understand. What is a plain TCP/IP printer port?
Post by Philip Nienhuis
On the OS/2 (ECS) side JetAdmin works better; though I use SLPR nowadays.
Since my printer is a USB printer, I believe SLPR is of no use to me.
And it seems that your experience with the HP printer server is not
good.
Post by Philip Nienhuis
Philip
Does anyone here have good experience with a USB printer server?
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Philip Nienhuis
2007-12-04 22:20:10 UTC
Permalink
Post by Fred Blau
Post by Philip Nienhuis
<snip>
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
Quite a few printer servers talk plain, TCP/IP, NETBEUI and IPX/SPX and
perhaps even more protocols.
Just TCP/IP would be enough to use a printer server.
Thanks, Philip. That would be perfect for me. After Bob Eager's
explanations, I have now switched my LAN from straight NETBIOS to
NETBIOS OVER TCP/IP. (The PEER by wi-fi is still not functional, but it
was never very good on my system. Since PEER works by cable, I can copy
files over the LAN just fine.)
The "NetBIOS over...." wouldn't be in the way I guess.
Post by Fred Blau
Post by Philip Nienhuis
Just to illustrate that: I have a HP170 X printer server here in my home
LAN. It is run using just plain TCP/IP.
I found that it got hung due to using the old HP JetAdmin (v.3.42) stuff
on the Windows side (probably due to some Windows hotfixes as it used to
work OK in the past) - I use a plain TCP/IP printer port now.
I don't understand. What is a plain TCP/IP printer port?
Something you enter in the printer object in the Ports tab on your OS/2
box featuring the word "TCP/IP". It is analogous to an LPT1 or so port -
be it that it connects to a LAN (address) rather than a physical 25-pin
connector. At the moment of writing I use WinXP, I have too little time
to boot into OS/2 to check how it looks like there in detail, sorry.
On WinXP it is just called a "Standard TCPIP port".
On Linux I use CUPS, there's a TCP/JetDirect port (JetDirect = HP
parlance) on tcp/ip port 9100 (confusing! a printer port vs a TCP/IP
port number).

FYI: a printer server has a LAN address (TCP/IP adress, NETBIOS name,
whatever) on the LAN side, and a physical connection at the printer side
(parallel, serial? or USB).
Post by Fred Blau
Post by Philip Nienhuis
On the OS/2 (ECS) side JetAdmin works better; though I use SLPR nowadays.
Since my printer is a USB printer, I believe SLPR is of no use to me.
And it seems that your experience with the HP printer server is not
good.
Post by Philip Nienhuis
Philip
Does anyone here have good experience with a USB printer server?
I had one, an el cheapo thing. We always shut off power from our home
LAN when we don't use it. The cheap printer server always printed a
status page after powering up, which I considered a waste of paper. So I
dumped the server a while ago, after I found out that my HP 170X
parallel printer server wasn't broken but just needed no more JetDirect
drivers.

BTW: USB refers to the physical connection between printer and printer
server. That could just be a parallel port too, for that matter. What
counts is that at the LAN side it has a TCP/IP address (or
NETBEUI/NetBIOS name, or IPX/SPX address).

P.
Fred Blau
2007-12-03 19:39:15 UTC
Permalink
<snip>
Post by Bob Eager
Post by Fred Blau
2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?
Yes, pretty much. You need a driver for it on the client machine,
though. In fact, if you have WinXP Pro you can do it more neatly (IMHO)
by using SLPR on the OS/2 end, and a UNIX style network port (LPR) on
WinXP.
In my original post I omitted stating that my printer is a USB device (a
Canon Pixma i5200 inkjet), for which there is presently no OS/2 driver
as far as I know. (I am hoping that Paul Smedley's efforts on TOPS will
change that in the near future.) So, painful as it is, I have to reboot
to Windows in order to print. Fortunately, I don't need to do this very
often. However, my wife's attitude is nearly opposite, as she doesn't
feel comfortable saving a document in any form other than print.
Therefore I would like the printer to be available (on the LAM) to her
WinXP laptop without my having to reboot. I am not familiar with SLPR,
but from the name I suppose it is not relevant to a USB printer. I
guess the same is the case for a "UNIX style network port (LPR)".

Therefore, with that clarification, my question #2 above remains.
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Peter Brown
2007-12-03 20:50:50 UTC
Permalink
Hi Fred
Post by Philip Nienhuis
<snip>
Post by Bob Eager
Post by Fred Blau
2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?
Yes, pretty much. You need a driver for it on the client machine,
though. In fact, if you have WinXP Pro you can do it more neatly (IMHO)
by using SLPR on the OS/2 end, and a UNIX style network port (LPR) on
WinXP.
In my original post I omitted stating that my printer is a USB device (a
Canon Pixma i5200 inkjet), for which there is presently no OS/2 driver
as far as I know. (I am hoping that Paul Smedley's efforts on TOPS will
change that in the near future.)
I think you mean CUPS in the above :-)


So, painful as it is, I have to reboot
Post by Philip Nienhuis
to Windows in order to print. Fortunately, I don't need to do this very
often. However, my wife's attitude is nearly opposite, as she doesn't
feel comfortable saving a document in any form other than print.
Therefore I would like the printer to be available (on the LAM) to her
WinXP laptop without my having to reboot. I am not familiar with SLPR,
but from the name I suppose it is not relevant to a USB printer. I
guess the same is the case for a "UNIX style network port (LPR)".
Therefore, with that clarification, my question #2 above remains.
2 options:

1] Share the printer - but as you only have Windows drivers for the
printer that will only work when your system (system that printer is
shared from) is booted to Windows.

2] You have already looked at a bit:-
Post by Philip Nienhuis
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
The advantage of using a print server is that the printer is available
to the lan all the time that it is powered on. That may not always be
the case when a printer is Shared; the system hosting the share may be
unavailable (powered off) so printing cannot happen.

If you get hold of a print server with a USB port you can use SLPR to
connect to the printer from eCS (when CUPS is ready) - not sure what
Windows would use but there will probably be some drivers supplied with
the print server that work the same as slpr ie a tcpip connection.

Regards

Pete
Fred Blau
2007-12-04 01:33:42 UTC
Permalink
Hi Pete,

On Mon, 3 Dec 2007 20:50:50 UTC, Peter Brown
Post by Peter Brown
Hi Fred
Post by Philip Nienhuis
<snip>
Post by Bob Eager
Post by Fred Blau
2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?
Yes, pretty much. You need a driver for it on the client machine,
though. In fact, if you have WinXP Pro you can do it more neatly (IMHO)
by using SLPR on the OS/2 end, and a UNIX style network port (LPR) on
WinXP.
In my original post I omitted stating that my printer is a USB device (a
Canon Pixma i5200 inkjet), for which there is presently no OS/2 driver
as far as I know. (I am hoping that Paul Smedley's efforts on TOPS will
change that in the near future.)
I think you mean CUPS in the above :-)
Definitely. (At least I remembered the last 2 characters correctly.)
Post by Peter Brown
Post by Philip Nienhuis
So, painful as it is, I have to reboot
to Windows in order to print. Fortunately, I don't need to do this very
often. However, my wife's attitude is nearly opposite, as she doesn't
feel comfortable saving a document in any form other than print.
Therefore I would like the printer to be available (on the LAM) to her
WinXP laptop without my having to reboot. I am not familiar with SLPR,
but from the name I suppose it is not relevant to a USB printer. I
guess the same is the case for a "UNIX style network port (LPR)".
Therefore, with that clarification, my question #2 above remains.
1] Share the printer - but as you only have Windows drivers for the
printer that will only work when your system (system that printer is
shared from) is booted to Windows.
2] You have already looked at a bit:-
Post by Philip Nienhuis
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
The advantage of using a print server is that the printer is available
to the lan all the time that it is powered on. That may not always be
the case when a printer is Shared; the system hosting the share may be
unavailable (powered off) so printing cannot happen.
If you get hold of a print server with a USB port you can use SLPR to
connect to the printer from eCS (when CUPS is ready) - not sure what
Windows would use but there will probably be some drivers supplied with
the print server that work the same as slpr ie a tcpip connection.
Regards
Pete
It seems that I am several months, even years, behind others on this
problem. I just came across a thread on an eComStation newsgroup,
initiated by Stan Goodman I think, that deals with SLPR and a print
server. (Stan, are you there? Did you get your system working?) So I
will look further on the Web. But perhaps you, or anyone here, could
tell me where to get SLPR, so that I can find out a bit more about its
features and limitations.

Regards,
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Peter Brown
2007-12-04 16:33:15 UTC
Permalink
Hi Fred
Post by Fred Blau
Hi Pete,
On Mon, 3 Dec 2007 20:50:50 UTC, Peter Brown
Post by Peter Brown
Hi Fred
Post by Philip Nienhuis
<snip>
Post by Bob Eager
Post by Fred Blau
2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?
Yes, pretty much. You need a driver for it on the client machine,
though. In fact, if you have WinXP Pro you can do it more neatly (IMHO)
by using SLPR on the OS/2 end, and a UNIX style network port (LPR) on
WinXP.
In my original post I omitted stating that my printer is a USB device (a
Canon Pixma i5200 inkjet), for which there is presently no OS/2 driver
as far as I know. (I am hoping that Paul Smedley's efforts on TOPS will
change that in the near future.)
I think you mean CUPS in the above :-)
Definitely. (At least I remembered the last 2 characters correctly.)
Post by Peter Brown
Post by Philip Nienhuis
So, painful as it is, I have to reboot
to Windows in order to print. Fortunately, I don't need to do this very
often. However, my wife's attitude is nearly opposite, as she doesn't
feel comfortable saving a document in any form other than print.
Therefore I would like the printer to be available (on the LAM) to her
WinXP laptop without my having to reboot. I am not familiar with SLPR,
but from the name I suppose it is not relevant to a USB printer. I
guess the same is the case for a "UNIX style network port (LPR)".
Therefore, with that clarification, my question #2 above remains.
1] Share the printer - but as you only have Windows drivers for the
printer that will only work when your system (system that printer is
shared from) is booted to Windows.
2] You have already looked at a bit:-
Post by Philip Nienhuis
Post by Bob Eager
Post by Fred Blau
3. I believe an alternative to attaching the printer to my OS/2 machine
would be to buy a print server and connect it to the router. Is this
approach OS-neutral? That is, does a print server depend on OS-specific
drivers? Would I be able to print from any machine on the LAN?
Should do, but that print server will talk either TCPBEUI or UNIX LPR.
The OS/2 machine is just as good.
The advantage of using a print server is that the printer is available
to the lan all the time that it is powered on. That may not always be
the case when a printer is Shared; the system hosting the share may be
unavailable (powered off) so printing cannot happen.
If you get hold of a print server with a USB port you can use SLPR to
connect to the printer from eCS (when CUPS is ready) - not sure what
Windows would use but there will probably be some drivers supplied with
the print server that work the same as slpr ie a tcpip connection.
Regards
Pete
It seems that I am several months, even years, behind others on this
problem. I just came across a thread on an eComStation newsgroup,
initiated by Stan Goodman I think, that deals with SLPR and a print
server. (Stan, are you there? Did you get your system working?) So I
will look further on the Web. But perhaps you, or anyone here, could
tell me where to get SLPR, so that I can find out a bit more about its
features and limitations.
Regards,
I downloaded my copy of slpr from ecomstation; login and search for slpr.

Not sure where to locate a copy if you do not have eCS... guess you
could send me an email if you cannot find a copy :-)

I use slpr with my SMC router; the router has a print server built in
with an lpt port for hooking up a printer. The router has an ip address
192.1682.1, the lpt port is LPT1.

To use slpr as the printer port it is simply a case of installing slpr,
selecting it as the printer output port (in printer properties) and
filling in the port details including the above address, 192.1682.1,
for LPD server and port name, LPT1, for LPD printer. I leave the
Performance options unchecked for my Canon iP4000.

Hope the above is of use :-)

Pete
Fred Blau
2007-12-05 22:05:40 UTC
Permalink
Hi Pete,

On Tue, 4 Dec 2007 16:33:15 UTC, Peter Brown
<losepeteSPAM-ME-***@ntlworld.com> wrote:

<snip>
Post by Peter Brown
I downloaded my copy of slpr from ecomstation; login and search for slpr.
Not sure where to locate a copy if you do not have eCS... guess you
could send me an email if you cannot find a copy :-)
Thanks. I keep writing OS/2, but what I have is eCS v1.1 (a form of
OS/2 in the opinion of _nearly_ everyone, as you know). So I grabbed it
from where you did.
Post by Peter Brown
I use slpr with my SMC router; the router has a print server built in
with an lpt port for hooking up a printer. The router has an ip address
192.1682.1, the lpt port is LPT1.
To use slpr as the printer port it is simply a case of installing slpr,
selecting it as the printer output port (in printer properties) and
filling in the port details including the above address, 192.1682.1,
for LPD server and port name, LPT1, for LPD printer. I leave the
Performance options unchecked for my Canon iP4000.
I installed SLPR on my desktop machine (I do not have a print server).
I then took the Canon Pixma iP5200 off the USB printer port and
connected it to SLPR. (It is not clear to me that this makes any
sense.) I assigned an IP address to it, but I was unable to ping it.
Post by Peter Brown
Hope the above is of use :-)
It's certainly a good start. But I decided to switch over to Windows
for the moment, so that my wife can print from her laptop to the iP5200.
I now have that working, although not without some minor blemishes that
I would like to fix. (My laptop won't return pings from the other 2
computers, but I can ping from it to the others. The other 2 ping both
ways.) Back to OS/2 tomorrow.
Post by Peter Brown
Pete
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Fred Blau
2007-12-05 21:27:32 UTC
Permalink
Bob,
Post by Bob Eager
Post by Fred Blau
2. Is it possible to access the printer attached to my OS/2 machine from
the WinXP machine? That is, is the OS of the machine with the printer
transparent to the printer driver on the WinXP machine?
Yes, pretty much. You need a driver for it on the client machine,
though. In fact, if you have WinXP Pro you can do it more neatly (IMHO)
by using SLPR on the OS/2 end, and a UNIX style network port (LPR) on
WinXP.
My printer is connected to my OS/2 desktop machine by USB. I have
installed SLPR and assigned an IP address that is within the 192.168..
range of my LAN. But WinXP Pro on my laptop (my wife's only has WinXP
Home) cannot see the printer, cannot ping it either. Is the USB
connection incompatible with SLPR when there is no print server in the
system?

What is a "UNIX style network port"? Is it not available in or for
WinXP Home?
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Bob Eager
2007-12-05 22:43:49 UTC
Permalink
Post by Fred Blau
What is a "UNIX style network port"? Is it not available in or for
WinXP Home?
I'm talking about a port that 'talks' the UNIX LPR protocol (which is
what SLPR does).

WinXP Home doesn't have it. WinXP Pro does, but you need to install the
port driver. Contact me offline if you can't find how to do it - I'll
need to find my notes.
Fred Blau
2007-12-20 11:52:08 UTC
Permalink
Follow-up to my original post and its thread (with thanks to all who
Post by Fred Blau
My OS/2 desktop and laptop machines connect by cable through a Linksys
WRT54G router using netbios with no problems. (My laptop can also
connect by wi-fi, but this is not quite as error-free.) However, my
wife wants to add her new WinXP laptop to the LAN, and she would like to
use the printer which is presently attached by USB to my desktop
machine....
I bought a print server with a USB-2.0 port (TrendNet TE100-P1U),
connected the printer (Canon Pixma iP5200) to it, and added it to my
LAN. I configured the print server (once, using my browser) and the
printer (on each computer running under Windows, using the CD supplied
with the print server).

Now I can print from each computer if it is running Windows. In
particular, my wife can print from her laptop by wi-fi, even if my
desktop machine is off or is running OS/2 (the usual state). So the
biggest problem is now resolved, although I am not quite sure that
bi-directionality is fully implemented through the print server.

I still cannot print from OS/2, as there is no OS/2 driver for the
iP5200. Since I do not print often, this is only a minor hassle. I do
still hope that CUPS (and SlPR, which I never did get properly
installed) will eventually take care of this limitation.
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Loading...