From: "Phil Burness" <[EMAIL PROTECTED]>
On Tuesday 23 January 2007 14:34, Eberhard Roloff wrote:
Phil Burness wrote:
>
> Here is the response from the suggestion above:
>
> mymachine:~ # smbclient -U
> [EMAIL PROTECTED] -L BSMITH2 Password:
> example2 session setup failed: NT_STATUS_LOGON_FAILURE
>
> Phil
Phil,
I'll throw a 3rd thing at you. Let's get back to basics shall we. Before
you can hope to print via smb, you need to make sure you have a working
samba configuration. If you don't have samba configured correctly that can
cause many smb printing headaches. A simple global section for your
/etc/samba/smb.conf can be:
[global]
use sendfile = No
workgroup = rb_law
server string = Samba %v
printcap name = cups
load printers = yes
printing = cups
show add printer wizard = No
log file = /var/log/samba/log.%m
max log size = 50
time server = yes
hosts allow = 192.168.7. 192.168.6. 127. 66.76.63.120
map to guest = bad user
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
local master = no
os level = 50
name resolve order = wins lmhosts bcast
wins server = 192.168.7.15
dns proxy = no
Of course adjust the values accordingly. Primarily you need to make
sure you have the use sendfile = No and your workgroup configured correctly.
Make the changes and don't forget to issue, as root, rcsmb restart. If you
changed your workgroup also issue the rcnmb restart. Also, check the
version of samba you have installed. If you have 3.0.23c installed that is
unpatched, you may be seeing the results of the SID/GID mapping problem that
happened in that release for simple setups. Samba.org has the SuSE binaries
for 3.0.23d.
Believe it or not, You really can print from linux to windows. I just
set up another Suse 10 to WinXP printer just to make sure.....
--
David C. Rankin, J.D., P.E.
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankinlawfirm.com
--
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
