Hi!

http://www.netadmintools.com/art258.html

I tried to use this tutorial but all the buttons are grayed out when I go to the advanced tab.

I have write access to \\server\print$. I am connected with the user Denis and I CAN see the home directory for the username (it's called denis).

Basically I want to put all the windows drivers for my printer on the Linux server so when Windows users come to my house it's point and click.

Can anyone help me with this?

Thanks,

David

Suse 9.0.

#Line from /etc/passwd:
denis:x:504:71::/home/denis:/bin/bash
#Line from /etc/Group:
users:x:100:denis
ntadmin:x:71:



My smb.conf:
[global]
workgroup = tux-net
os level = 2
time server = Yes
unix extensions = Yes
encrypt passwords = Yes
map to guest = Bad User
printing = CUPS
printcap name = CUPS
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
wins support = No
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
#I added this next line because it said not to use share level security
security = user
[homes]
comment = Home Directories
valid users = %S
browseable = No
read only = No
create mask = 0640
directory mask = 0750
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = @ntadmin
create mask = 0664
directory mask = 0775
printer admin = @ntadmin

[public]
path = /home/public

Samba 2.2.8a

I cheated..


to the print$ I added:

writeable = yes

I changed denis to userid 0 and group 0

I added @root to all the lines that have @ntadmin.

I was able to get it done.

There is probably a better way though...

David

I can't do anything now, it says exception every time I try and access the printers properties, and I print from another application it crashes.

I stopped samba, went and deleted ntdrivers.ndl, ntprinters.ndl etc...

Restarted windows machine,

Started SMB service.

Back to square one....

No more errors on windows machine, but drivers are still not loaded. For anyone else experiencing this, in my research I found that the Samba site says the issue was resolved in samba 3.0.0

David