Re: [Samba] Printer sharing with 64-bit Windows clients
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 get it into the release notes. Hope this hasn't caused you too many problems. Just to add my 2cents. We're going to see alot more of this problem as Win7 64bit becomes the standard oem install for new systems. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer sharing with 64-bit Windows clients
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 this up as a tech-note for the next 3.4.x release and for 3.5.0 and get it into the release notes. Hope this hasn't caused you too many problems. Just to add my 2cents. We're going to see alot more of this problem as Win7 64bit becomes the standard oem install for new systems. I know. We're working on it as fast as we can... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Printer sharing with 64-bit Windows clients
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 64-bit Windows clients, but perhaps not all 64-bit Windows clients. See also: https://bugs.launchpad.net/fedora/+bug/482836 http://ubuntuforums.org/showthread.php?p=8263192 I'm running Samba v3.4.5 on a 32-bit Slackware v13 virtual machine, Linux kernel v2.6.29.6. CUPS is v1.3.11. I have produced a log level 5 output showing two clients connecting to the Samba system and trying to view properties on the printer. The 32-bit client Manager2b succeeds, the 64-bit client MasterIm64VM does not. The logs (and config) are in http://thor.chguernsey.com/temp/samba3.4.5logs-0.tgz (116kb, MD5SUM 04672e49116c4596820812db5cb8cdfb). 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. The reason (and Guenther can correct me if I'm wrong), is that in 3.4.x we changed from the hand-marshalled SPOOLSS RPC we used in 3.3.x, which was mostly correct after being worked on for many years, to pidl-generated SPOOLSS RPC directly from the idl files. Now our idl files are correct, but it turns out that the Windows idl parser for SPOOLSS is itself custom, and won't accept the normally marshalled RPC packets that the pidl-generated code creates. Guenter and Metze have been doing a lot of work on fixing this, and this is why 32-bit Windows clients work in 3.4.5. However there are still some changes needed for 64-bit Windows clients, and this will probably make it into an early patch for 3.5.x (it won't make 3.5.0, as it's too late to test the changes needed before we ship next month). I'm going to write this up as a tech-note for the next 3.4.x release and for 3.5.0 and get it into the release notes. Hope this hasn't caused you too many problems. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printer sharing with 64-bit Windows clients
-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. See also: https://bugs.launchpad.net/fedora/+bug/482836 http://ubuntuforums.org/showthread.php?p=8263192 I'm running Samba v3.4.5 on a 32-bit Slackware v13 virtual machine, Linux kernel v2.6.29.6. CUPS is v1.3.11. I have produced a log level 5 output showing two clients connecting to the Samba system and trying to view properties on the printer. The 32-bit client Manager2b succeeds, the 64-bit client MasterIm64VM does not. The logs (and config) are in http://thor.chguernsey.com/temp/samba3.4.5logs-0.tgz (116kb, MD5SUM 04672e49116c4596820812db5cb8cdfb). Detailed steps: Both clients can browse to \\PrintA\ and see the printer LJ2200-A and the Printers and Faxes icon. Double-clicking the Printers and Faxes icon works and shows the printer again (now with Add Printer above it) BUT the 64-bit system shows the printer name as a box now. Copying and pasting that box gives the non-ASCII hex values e3 a0 88. Right-clicking the entry and selecting Properties gives a box with a red X saying Printer properties cannot be displayed. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server. For more information, click Help. The first obvious issue I see in the log occurs at line 14,505 in s.masterim64vm: [2010/01/26 11:39:01, 4] rpc_server/srv_pipe.c:2297(api_rpcTNP) api_rpcTNP: \spoolss op 0x45 - api_rpcTNP: rpc command: SPOOLSS_OPENPRINTEREX checking name: \\PrintA\ã 88 For what it's worth, another server running Samba v3.4.3 with CUPS v1.3.7 has no problems with 64-bit clients (so far). I have been unable install Samba v3.4.3 on the first server...Neither 32-bit nor 64-bit systems are able to connect at all with v3.4.3 running on the server. Daniel Johnson progman2...@usa.net / djohn...@progman.us -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFLXzdF6vGcUBY+ge8RAkc3AKCTOwImjekcpqaQTGgls5G+2dbFswCfRQlZ TqPNESxDbqko2KvL8mi50k4= =TUjQ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Printer sharing and LDAP traffic
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 Printer. I'm seeing LDAP search requests for undergrad lab printer, Undergrad Lab Printer, and UNDERGRAD LAB PRINTER. Why is it making all of this traffic and how do I stop it? ~~ Thom Savage Systems Analyst Computer and Information Sciences University of Alabama at Birmingham http://www.cis.uab.edu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printer Sharing Issue - Printer Error From Windows 2000
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 SuSE-supplied unofficial rpms. A Windows 2000 virtual machine runs in a VMware Workstation 5 vm, and shares documents with this Linux host and prints via Samba. Document sharing works perfectly, and printing, when there was an Epson C84 attached, worked fine also. (Alas, the C84 is literally worn out...) I installed the R300 in Windows the same way I installed the C84: I used the Adobe winsteng.exe Postscript printer installer, and pointed it to the ppd file generated by SuSE for the R300. The R300 does actually print fine from Windows, but at the end of each print job it spits out a blank sheet of paper, and then another sheet of paper with the following on it: ERROR: rangecheck OFFENDING COMMAND: .installpagedevice Stack: -null- -dictionary- -savelevel- This makes it a bit of pain to print, say, multiple checks from QuickBooks as QuickBooks creates each check as a separate print job. The only thing different on the SuSE side between the C84 setup and the R300 setup is the Linux printer driver. For the C84 I used the CUPS+Gimp-Print v4.2.7 driver. That equivalent driver for the R300 resulted in nothing being printed at all, so I am using instead the Foomatic/Gimp-Print driver. (The R300 prints totally fine from Linux, btw.) To test, I created another printer in Windows using using winsteng.exe, but this time I let it use the Adobe provided generic Postscript ppd file. I get the same error printing from Windows as well. I also tried the Epson Kowa drivers; these worked like the CUPS driver--not at all. Anyone seen anything like this before? Any suggestions for narrowing this down? Thanks! Mark -- _ A Message From... L. Mark Stone Reliable Networks of Maine, LLC We manage your network so you can manage your business. 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printer sharing
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 testing!) and see if the problem goes away. Joel On Wed, Nov 26, 2003 at 11:46:56AM +0100, Timo Haberkern wrote: Hi, i used [printers] comment = All Printers path = /var/spool/samba browseable = yes printable = yes public=yes create mode = 0700 to share my printers to W2K Clients. For that i created a printer (printing is working locally) on my linux machine (RH9, Samba 2.2.7, Cups). If i try now to use this printer on my W2K machines i can create a Printer in the Control Panel browsing the Domain and installing the driver for Windows. The printer is there but i can't access him (Access not allowed; no connection possible) Has anyone an idea whats going wrong? Timo -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printer sharing
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 following: I [26/Nov/2003:13:27:26 +0100] Job 8 queued on 'LaserJet_1300' by 'thaberkern'. I [26/Nov/2003:13:27:26 +0100] Started filter /usr/lib/cups/filter/cupsomatic (PID 12482) for job 8. I [26/Nov/2003:13:27:26 +0100] Started backend /usr/lib/cups/backend/socket (PID 12483) for job 8. Timo Joel Hammer wrote: 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 testing!) and see if the problem goes away. Joel On Wed, Nov 26, 2003 at 11:46:56AM +0100, Timo Haberkern wrote: Hi, i used [printers] comment = All Printers path = /var/spool/samba browseable = yes printable = yes public=yes create mode = 0700 to share my printers to W2K Clients. For that i created a printer (printing is working locally) on my linux machine (RH9, Samba 2.2.7, Cups). If i try now to use this printer on my W2K machines i can create a Printer in the Control Panel browsing the Domain and installing the driver for Windows. The printer is there but i can't access him (Access not allowed; no connection possible) Has anyone an idea whats going wrong? Timo -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- Grüsse Timo Haberkern EMEDIA OFFICE GmbH Wingertstr. 4 74850 Schefflenz-Kl. http://www.emedia-office.com [EMAIL PROTECTED] Tel.: 06293/921121 Fax: 06293/921129 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba printer sharing problem
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 = /etc/printcap load printers = yes printing = lprng [printers] comment = All Printers path = /var/spool/samba printer = raw browseable = yes guest ok = yes writable = no printable = yes And my /etc/printcap looks like this Print:\ :ml#0:\ :mx#0:\ :sd=/var/spool/lpd/Print:\ :af=/var/spool/lpd/Print/Print.acct:\ :sh:\ :lp=/dev/usb/lp0:\ :lpd_bounce=true:\ :if=/usr/share/printconf/util/mf_wrapper: Seen as its an access denied error i though it could be to do with the permissions of /var/spool/samba but they are set drwxrwxrwt which as far as i know is correct. The ip of the server is 192.168.0.2. and from the windows machine I am trying to connect by typing \\192.168.0.2\printers I am new to the world of samba so if I'm betting i've made an obvious mistake somewhere along the line. Thanks in advance, Adam -- +---+ | Adam Bowns | | [EMAIL PROTECTED] | | http://homepage.ntlworld.com/adam-bowns/ | +---+ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
