Windows clients can't access Mepis printer until Samba is restarted
Posts: 101
I posted this query to MepisLovers previously, but unfortunately am no further forward. 
My LAN setup is:
* Old PC running MepisLite 3.3.2-1 RC (just!), acting as a file and (HP) printer server
* Mepis 6.0 clients, using CUPS for printing
* Win 2000 and Win 98SE clients, with appropriate Windows printer drivers installed locally
File shares can be found by all clients, and the Mepis 6.0 clients can print fine.
But the Windows clients cannot see (eg in Windows Explorer) or print to the printer until Samba is restarted on the server (using /etc/init.d/samba restart). Then they print as expected.
There are some similar problems mentioned in the forums, but no clear solutions. Also, I've tweaked various parameters in the smb.conf file to no avail.
Anyone got any ideas to bring the printer automatically to the attention of Windows?!
Is your Samba server set-up
Posts: 1634
Is your Samba server set-up to be the local master for the windoze-side of the networking environment?
My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.
Some info from log files and smb.conf
Posts: 101
No, I don't think so. But I did find that on the server, after reboot, /var/log/daemon.log showed:
Nov 26 11:30:20 localhost smbd[2567]: [2006/11/26 11:30:20, 0] printing/print_cups.c:cups_cache_reload(85)
Nov 26 11:30:20 localhost smbd[2567]: Unable to connect to CUPS server localhost - Connection refused
And on one of my MEPIS 6.0 client machines, the corresponding log showed entries like this every 10 minutes or so:
Nov 26 14:19:58 localhost nmbd[3327]: [2006/11/26 14:19:58, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(353)
Nov 26 14:19:58 localhost nmbd[3327]: find_domain_master_name_query_fail:
Nov 26 14:19:58 localhost nmbd[3327]: Unable to find the Domain Master Browser name MEPIS<1b> for the workgroup MEPIS.
On this client machine, I discovered that smb.conf contained:
wins support = yes
so I've now set that to NO instead.
Here's some extracts from smb.conf on the MEPISLite server:
;*******************section global*****************
[global]
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
printing = cups
workgroup = mepis
server string = %h server (Samba %v)
hosts allow = 192.168.0. 192.168.1. 192.168.2. 192.168.79. 127.
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=4096 SO_RCVBUF=4096
passdb backend = tdbsam guest
dns proxy = no
max log size = 1000
security = share
restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto
;*******************section printers*****************
[printers]
comment = All Printers
path = /tmp
browseable = no
printable = yes
guest ok = yes
create mask = 0700
print command = lpr -P %p -o raw %s -r
Changes:
Posts: 1634
domain master = yes
preferred master = yes
browseable = yes
My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.
Sorry, no effect
Posts: 101
@EnigmaOne:
Unfortunately, making these changes seems to have made no effect after rebooting the machines involved.
However, I did find this post:
http://www.experts-exchange.com/Operating_Systems/Linux/Linux_Printing/Q_21924195.html
which seems to indicate that an update of cupsys might be necessary...
Samba has to be running to
Posts: 165
Samba has to be running to share the printer with Windows andl linux machines. The alternative would be to buy a print server and then share the printer using it's ip address.
A Day Without M$ Windoze is a Great Day Indeed !!!
Registered as user #425372 with the Linux Counter,
http://counter.li.org.