I have a Win2K system which I recently upgraded to dual-booting SuSE 9.1 Pro. In its Windows incarnation, the system serves as a print server for my home LAN. I'd like to be able to provide the same service when SuSE is running, but although the host name and the share name of the printer is the same in Win2K and Samba, I have to maintain duplicate printer definitions on the client machines.to be able to use the printer regardless of which OS is booted at a given time. Has anyone been able to define a printer share to both Windows and Samba so that it can be accessed transparently by client systems? Thanks in advance, Gordon Keehn
On Monday 20 September 2004 8:13 pm, Gordon Keehn wrote:
I have a Win2K system which I recently upgraded to dual-booting SuSE 9.1 Pro. In its Windows incarnation, the system serves as a print server for my home LAN. I'd like to be able to provide the same service when SuSE is running, but although the host name and the share name of the printer is the same in Win2K and Samba, I have to maintain duplicate printer definitions on the client machines.to be able to use the printer regardless of which OS is booted at a given time. Has anyone been able to define a printer share to both Windows and Samba so that it can be accessed transparently by client systems?
Never done quite this myself. I migrated a server from OS/2 to linux and had the equivalent of your setup, with duplicate printer definitions on clients, till I was confident that linux was doing th job. An issue, which might be relevant, is that under linux, I share out the printer as a raw queue, ie no printer driver on the server. Presumably you are consistent about the clients having the printer driver
Has anyone been able to define a printer share to both Windows and
Samba so that it can be accessed transparently by client systems? Thanks in advance, Gordon Keehn
I think you might be stuck doing it that way as Windows clients will see each one as a separate machine (even if the names are "identical"). Although, one possibly thing you could try is mapping the printer as a local device (net use lpt1: \\server\share) and then install the printer and tell it it's on local LPT1:... Not the most graceful thing to do, but might help you in the instance. Steve Kratz
On Monday 20 September 2004 02:13 pm, Gordon Keehn wrote:
I have a Win2K system which I recently upgraded to dual-booting SuSE 9.1 Pro. In its Windows incarnation, the system serves as a print server for my home LAN. I'd like to be able to provide the same service when SuSE is running, but although the host name and the share name of the printer is the same in Win2K and Samba, I have to maintain duplicate printer definitions on the client machines.to be able to use the printer regardless of which OS is booted at a given time. Has anyone been able to define a printer share to both Windows and Samba so that it can be accessed transparently by client systems? Thanks in advance, Gordon Keehn
It's been a couple of years, but yes, I did exactly what you are asking. Dual booting w2k and Red Hat something. If I recall, you just need to make sure that the machine name, workgroup, and print share name are the same in windows and linux(samba). Doug
participants (4)
-
Doug B
-
Gordon Keehn
-
Steve Kratz
-
Vince Littler