If you are at least getting smbclient to work, you are almost there!

Now the problem is how Cups' filters treat the remote winblows printer.

Cups tries to run thru the Linux/Unix style printer filters which feed
GIMP/GHOSTSCRIPT or some other ratherizer. The problem is that the
rasterizer rarely puts out information that is compatible with the
winblows printers...

Your first step should be to set up the Winblows printer as a text mode
printer and try printing plain text to it from Linux/Cups.

Make sure that you can get plain text to print FIRST!

If you can this far, you can start searching for Winblows compatible
Linux/Cups filters in the driver database.

Additional printer control init sequences may differ between CUPS and
Winblows which is another problem...

-JMS

-----Original Message-----
From: Guilherme Cirne [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, August 15, 2001 12:04 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [newbie] Network Printer on Win98


At 23:08 14/08/01 -0400, you wrote:

>Before you go as far as MOUNTING a remote share or utilizing a remote 
>printer under Samba you should test to make sure that your Linux 
>machine is able to LOG IN to the winblows machine...
>
>Try
>
>"smbclient -L machine -U user"
>
>Where "machine" is the name of the Winblows machine and "user" name you

>are CURRENTLY using on your Winblows machine to log into the network...
>
>You should see something like this
>
># smbclient -L whopper -U admin
>added interface ip=10.0.0.1 bcast=10.0.0.255 nmask=255.255.255.0
>
>Password:
>
>
>
>         Sharename      Type      Comment
>
>         ---------      ----      -------
>
>         CDROM          Disk
>
>         E              Disk
>
>         D              Disk
>
>         C              Disk
>
>         IPC$           IPC       Remote Inter Process Communication
>
>
>
>         Server               Comment
>
>         ---------            -------
>
>
>
>         Workgroup            Master
>
>         ---------            -------
>
>#
>
>Notice that it prompted for a WINDOWS password, then displayed the 
>shares...
>
>If this does not work for you, you either have SAMBA configured 
>incorrectly (did you set up your Linux box to act as a SAMBA server 
>yet? The samba client uses the settings from the /etc/smb.conf or 
>/etc/samba/smb.conf files for the server!) or the username and password

>pairs you are giving are not recognized by Winblows.
>
>Once you have something similar to the above displaying, use the 
>accepted login to set up your remote Winblows printing.
>
>One step at a time makes things easier to debug.
>
>-JMS

At first I couldn't connect to the windows machine using samba. I would
get 
a connection failed error. After I re-installed LM 8.0 from scratch
(since 
I have some time on my hands I can afford to do this) the first thing I 
tested was smbclient and I successfully connected to the windows
machine.

So I setup the printer and sent a test page to it. It would start
printing 
fine but would stop for no reason at the beginning of the page. I tried 
setting the printer up both through Mandrake Control Center and Cups. At

least I'm moving forward!

Guilherme Cirne
[EMAIL PROTECTED]


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://wwww.mandrakestore.com

Reply via email to