Re: [Samba] Printer sharing with 64-bit Windows clients

2010-02-01 Thread Ryan Suarez
Jeremy Allison wrote: Ok, here's the deal. If you have 64-bit Windows clients at the moment you need to be using 3.3.10, not anything later. If you're using 32-bit Windows clients, you can use 3.4.5 or later. I'm going to write this up as a tech-note for the next 3.4.x release and for 3.5.0 and

Re: [Samba] Printer sharing with 64-bit Windows clients

2010-02-01 Thread Jeremy Allison
On Mon, Feb 01, 2010 at 12:53:12PM -0500, Ryan Suarez wrote: Jeremy Allison wrote: Ok, here's the deal. If you have 64-bit Windows clients at the moment you need to be using 3.3.10, not anything later. If you're using 32-bit Windows clients, you can use 3.4.5 or later. I'm going to write

Re: [Samba] Printer sharing with 64-bit Windows clients

2010-01-29 Thread Jeremy Allison
On Tue, Jan 26, 2010 at 12:44:22PM -0600, Daniel Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a problem accessing a CUPS/Samba shared printer on a Windows XP x64 Professional system (WinNT5.2 kernel). It seems from my searching that this is a problem affecting only

[Samba] Printer sharing with 64-bit Windows clients

2010-01-26 Thread Daniel Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a problem accessing a CUPS/Samba shared printer on a Windows XP x64 Professional system (WinNT5.2 kernel). It seems from my searching that this is a problem affecting only 64-bit Windows clients, but perhaps not all 64-bit Windows clients.

[Samba] Printer sharing and LDAP traffic

2008-01-09 Thread Thom Savage
Hello list, My linux server is using Samba to share cups printers. My nsswitch.conf is setup for LDAP authentication. I'm noticing tons of LDAP traffic all of the time between my Samba server and my LDAP server for printer names. For example, I have a printer share called Undergrad Lab

[Samba] Printer Sharing Issue - Printer Error From Windows 2000

2005-07-27 Thread L. Mark Stone
I am getting an error printing to a newly installed printer from Windows 2000. I appreciate this may not be a Samba problem, but I thought this would be the best place to start. I installed an Epson Stylus Photo R300 on a SuSE Pro 9.2 system running Samba 3.0.14a, installed from the

Re: [Samba] Printer sharing

2003-11-26 Thread Joel Hammer
Without thinking about this, have you walked through DIAGNOSIS.txt, which comes in your samba sources? What comes to mind are things like firewalls and network problems. Also, Cups (which I do not use) may have some security issues. It is fun to make the guest user root in smb.conf (just for

Re: [Samba] Printer sharing

2003-11-26 Thread Timo Haberkern
Problem 1 solved! Some typos in the smb.conf. Now i have another problem: if i print on w2k machine ther appears a spooling file in in the spooling folder = /var/spool/samba. But nothing more happens. In my CUPS Printer queue is nothing. i took a look in the cup error_log and found the

[Samba] Samba printer sharing problem

2003-02-05 Thread Adam Bowns
I'm having some problems sharing my printer with samba. The printer works fine locally, but whenever I try to connect to it from a windows machine i get the error message Access denied, unable to connect the parts of my /etc/smb.conf concerned with printing look like this printcap name =