samba - Apr 2005 - KDE-Print almost working, directory shares working good.

Hi all,

I've been reading quite a few of the posts to this mailing list, and I'm
afraid that my question is going to look very noobish, but as I am one,
that's to be expected, so apologies in advance for my post getting caught
up in more serious samba queries.

I have two PCs, one a workstation (biggeek.supermail.dyndns.org,
192.168.1.100), and the other a general server machine
(littlegeek.supermail.dyndns.org 192.168.1.101).

Littlegeek is running samba-3.0.10-1.fc3 on Fedora Core 3 naturally, with
samba-swat-3.0.10-1.fc3 in there too.

Biggeek is on Slackware 10.1.

I am trying to print documents from biggeek to littlegeek. I have set up
KDE-Print on biggeek to find the print server on littlegeek, which is has
done ok as far as I can tell.

In Konqueror, I can connect to littlegeek via the LISA LAN manager and
browse, copy, paste and delete until I'm blue in the face. No problems
there.

My stumbling block is getting littlegeek to actually do something with the
print jobs I'm sending it.

Before I waffle on too much more, here's my smb.conf from littlegeek
(I've
set SWAT to allow logins from my workstation, biggeek, 192.168.1.100) :

# Samba config file created using SWAT
# from 192.168.1.100 (192.168.1.100)
# Date: 2005/04/09 23:44:52

# Global parameters
[global]
	workgroup = BUNGE
	netbios name = LGEEK
	server string = Samba Server
	map to guest = Bad User
	username map = /etc/samba/smbusers
	log file = /var/log/samba/%m.log
	max log size = 50
	server signing = auto
	socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
	preferred master = No
	domain master = No
	dns proxy = No
	wins support = Yes
	ldap ssl = no
	idmap uid = 16777216-33554431
	idmap gid = 16777216-33554431
	guest ok = Yes
	cups options = raw

[homes]
	comment = Home Directories
	read only = No
	hosts allow = 192.168.1.100
	browseable = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	printable = Yes
	printer name = lp0
	browseable = No

[pete]
	path = /home/pete
	valid users = pete
	read only = No
	hosts allow = 192.168.1.100

[lp0]
	comment = lp0
	path = /var/spool/samba
	printer admin = root
	read only = No
	printable = Yes
	printer name = lp0
	oplocks = No
	share modes = No


My printer, which is connected to the parallel port of littlegeek, is an
Epson Stylus Color 740. CUPS is set up ok as far as I know, and I can
print a test page locally no problem.

When I open up a file on biggeek (workstation), and click PRINT, making
sure lp0 is selected, the job does seem to go to littlegeek, as in the
Print Manager section of Konqueror (see link below), the print job shows
up ok, with any subsequent jobs queued.

But that's it.

Nothing else happens.

I am a bit embarrassed about this as using SWAT is supposed to make
adminstering Samba a breeze, but I'm still unfortunately stuck.

I can't work out why the jobs are being sent to the samba server on
littlegeek, but nothing is being done with them.

If it helps, here are a couple of screenshots of what is happening :

1) The queue list on KDE Print Manager :

http://homepage.ntlworld.com/alternative.carpark/biggeek_print_manager.png

2) Some information about the printer I'm sending to :

http://homepage.ntlworld.com/alternative.carpark/kde_print_info.png


I don't know what other information to provide, so please let me know what
I've missed out.

Thanks for your time everyone.

Regards,

Pete.

P.S. Sorry if the links don't work for you, they do here. :/

On Saturday 09 April 2005 07:15 pm, Pete wrote:
> But that's it.
>
> Nothing else happens.
>
> I am a bit embarrassed about this as using SWAT is supposed to make
> adminstering Samba a breeze, but I'm still unfortunately stuck.
>
> I can't work out why the jobs are being sent to the samba server on
> littlegeek, but nothing is being done with them.
>
> If it helps, here are a couple of screenshots of what is happening :
>
> 1) The queue list on KDE Print Manager :
>
> http://homepage.ntlworld.com/alternative.carpark/biggeek_print_manager.png
>
> 2) Some information about the printer I'm sending to :
>
> http://homepage.ntlworld.com/alternative.carpark/kde_print_info.png
There's no reason to involve Samba in this process. CUPS should handle this 
pretty much on its own. If you point your browser to 
http://biggeek:631/printers/ do you see the printers on littlegeek (the same 
as http://littlegeek:631/printers/)? All printers should be seen from both 
systems if CUPS is set up correctly.