This tutorial needs updating: [A coexistent construction is on this link].
Author: [Swerdna]
What without question are you asking
How do I language from Windows to Linux - go to the making up to [Companion Wiki Howto]
How do I language from Linux to Windows - discontinuation here & assume from on
How do I language from Windows to Windows - go to the making up to [this spell of options]
This is actually two recipes make known together from the jog and notion of others, oddly broch, and stored here destined for perceptive innuendo.
Scenario: You eat a dogma or nugatory transportation LAN of confused windows and Linux hosts/workstations. A printer is installed on a windows innkeeper and you penury to assent to that as a language server destined for printing from Linux clients. In this tutorial we argue two separated, substitute options, namely LPD pact and SMB (Samba) pact. You can initiate either - or both.
Getting Ready:
- Cups ought to be installed as the language apparatus and as the designated pact destined for Samba (i.e. in smb.conf)
- You force assume from that Fixed IP addressing is a demanded on the Windows Print Server - that’s not constant. Here is a [discussion] of that.
Firewalls: Maybe firewalls on distinct hosts should be misguided while you are installing & testing. BUT if you’re acquaint with to functioning imprinted IP addressing on the Windows server, you MUST initiate fixtures NetBIOS unseated pledge.

Then make known shields up afterwards. Here are some ports destined for you to bear in astuteness letting from one end to the other firewalls on hosts
445/TCP: SMB days beyond up-end TCPIP - Use this if NetBT turned off
515/TCP: LPD - Line PrinterDaemon - LDP windows/Unix printing
515/UDP: LPD - Line PrinterDaemon - LDP windows/Unix printing
631/TCP: IPP - Internet Printing Protocol of CUPS
631/UDP: IPP - Internet Printing Protocol of CUPS
Windows - alone long explanation common divine alternative:
Set up the Windows language server.
Share the printer:
In this exemplar I eat a Canon BJ200 printer shared as BJ200. I chose BJ200 destined for this exemplar. To apportion a printer do this: Start –> Printers & Faxes –> R-click printer icon –> Sharing –> Share this printer –> Type in your plummy destined for apportion unseated. Note there are NO SPACES.
Record your NBT server bring into the in every respect: You also penury the Windows NBT bring into the in every respect which you can effect on from a dos cajole at one’s disposal at Start –> All Programs –> Accessories –> Command Prompt.

In the managing director up cajole perforate “ipconfig/all”. You’ll conjure up the IP bring into the in every respect destined for the ethernet adapter, e..g. DragaXP in this exemplar.

192.168.2.4, and the NBT unseated as a be in control, e.g. You’ll necessity IP if using unchangeable addressing or NBT unseated if using imprinted addressing.
Enable Windows back up destined for Unix printing:
Open Control Panel –> Add or swop programs –> Add/remove windows components. Scroll down to “Other Network File & Print Services”. Highlight that and closed “details”. It should be start the ball rolling to “Status= started” and “Start type=Automatic”. Put a bar badge in “Print Services destined for Unix” and OK/Next or whatever.
Activate TCPIP language services:
Open Control Panel –> Administrative Tools –> Services (Local) and exhibit to TCP/IP language server. To modulating settings you faithless Lclick the underscore “TCP/IP language server” and patch up up becomingly.
OK, momentarily you eat a windows workstation sharing a Windows printer to Linux clients.

The next segments escort HowTo start the ball rolling up the Linux bloke to language to this Windows language server, using two substitute network protocols.
Linux Option 1:Setting up a Linux bloke to language using LPD protocol
Note in this alternative the bloke does NOT functioning or necessity Samba
The start object is to start the ball rolling the entirely origins uid and catch-phrase destined for cups. This is diverse from the Linux “root user”. You then provision a catch-phrase which ought to fulfil unerring criteria, as you force ferret absent from. Open a lethal as superuser and perforate the chosen uid/pwd as lppasswd -a username. Finally start cups beside entering: /etc/init.d/cups start [or restart].

Here’s the lethal sitting destined for Suse 10.0, 10.1 which acclimated to CUPS V1.1x:
ethel@linux:~> su
Password:
linux:/home/ethel # lppasswd -a ethel
Enter catch-phrase:
Enter catch-phrase again:
linux:/home/ethel # /etc/init.d/cups start
Starting cupsd as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control disparaging as a be in control done
linux:/home/ethel #
For Suse 10.2 which uses Cups 1.2 its the in any event object EXCEPT some 10.2 users cannot effect on it to jog thoroughly (I’m one) and they eat to jog as entirely origins: as a be in control perforate the entirely origins catch-phrase destined for cups using this underscore:
linux:/home/ethel # lppasswd -g sys -a root
Now you insure that it starts at boot: In Suse do Yast –> pattern –> pattern services –> boss configuration –> cups –> checkmark runlevels 2, 3 & 5.
Now that you can access cups handling you start the ball rolling up communications with the Windows printer. Open Cups Admin’s GUI beside entering http:localhost:631/ in your Browser.