02-09-04 08:36 AM
"John Doe" <uce@ftc.gov> wrote in message news:<GutRb.13164$F86.1430403@twister.southeas
t.rr.com>...
> If not already installed then install samba. Then you should be able vi t
he
> file "/etc/samba/smb.conf" and it will explain what you trying to do and
> shows examples too. If you still need help then as Alex said RTFM then po
st
> if your still in trouble.
>
> Bryan
>
An alternative that I use with no problems
Setup: Three machines, One WinXP, One Win98SE one Fedora Linux
All PCs Wireless Lan to router / ADSL (NEtGear equipment)
Linux machine detected the NEtGear wireless LAN card and driver
successfully at install.
Printer is Kyocera laser - but that's not important.
D-Link DP-101 print server plugs into printer parallel port and
ethernet to NetGear router on the other side.
DLink is "lpd" device that all PCs "point to" - WinXP has native
support for lpr/lpd (I think), lpr is installed on Win98 from Dlink
CD-Rom; and after fiddling with CUPS and various settings Linux
supports (of course lpr/lpd)
So... the printer is shared between all machines but does not require
a dedicated, or always powered on PC to be "reached". It is always
active on the network using its own dedicated IP address.
Pros: Physically a very neat solution. The Dlink sits unobserved
behind the printer and the only cabling is a CAT5/UTP back to the
router. I think there are wireless versions of this kind of device.
No problems with printer drivers for complex pages of graphics and
text.
Data transmission to Dlink much faster than printer can match - so no
bottle-neck
Cons: A small buffer for data on the Dlink - relies on the printer
being powered on to effectively "keep the print flowing". I would
think a PC with Samba or lpd and a reasonable print spool space on
disk would be able to accept several concurrent print requests and
allow more sophisticated (complex) print management.
HTH
Clive, UK
[ Post a follow-up to this message ]
|