I'm migrating from Samba 3.0.24 to 3.4.3 to add support for Windows 7 on my print server. I've kept the smb.conf essentially the same, changing only the directives corresponding to Kerberos authentication as changed in the 3.4 series. Please see http://pastebin.com/m9c0409 Note that the LPRng backend isn't installed on this server, and Kerberos is working as expected...I am only testing samba's printing abilities. I am using drivers from Windows 7 (as suggested by HP), and they uploaded to the server fine. I am using "HP LaserJet 4250 PCL 5", though the error also occurs with the PCL 6 driver. When I go to add a printer in Windows 7 (after configuring appropriate drivers, permissions, etc), I get an error: "Windows cannot connect to the printer. Operation failed with error 0x000006f7" This error occurs for Windows 7 machines that are in my domain, and for Windows 7 machines that are not in my domain. It doesn't seem to make a difference if UAC and the firewall are on or off. To reproduce, navigate to the server, then try to add a printer (right click, connect). The error occurs near the end of the process. The operation succeeds when I try the same procedure on Windows XP. The following is written to the Security event log (Event ID 6281): "Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error. File Name: \Device\HarddiskVolume2\Windows\System32\l3codeca.acm "
Created attachment 4938 [details] log level 10 of a client experiencing symptom described
I did a similar update, 3.0.28 -> 3.4.3, and have the same problem. I also see the problem in Windows Vista clients. If I remove the printer driver from the server I can install the printer using a locally driver. I don't see Error 6281 in the Security event log.
I am also running into the same issue here. This is really problematic, since I've not found any workarounds in either Win7 or Samba. My configuration is: Client: Win7 Ultimate 64-bit Server: Fedora 11 64-bit, samba 3.4.3. Same server configuration works fine with WinXP. Any updates or suggestions on how to get around this would be awesome.
I am actively looking into this and I think I found the issue. Hopefully a patch is available soon. Stay tuned - and thanks for the patience.
That's great news. I'd be happy to try and test any patch if you need additional user-base testing.
Created attachment 4980 [details] First part of fixing bug 6883 This should fix sambas spoolss_EnumPrinterKey implementation which generated an incorrect list of printer keys.
Created attachment 4992 [details] First part of fixing bug 6883 (revised version)
Created attachment 5003 [details] 3-4: final version of the patch Ok, Metze, I merged the other bits to that patch. Ok now ?
Hello, What version of Samba do I need to test this patch? I note that it doesn't seem to apply cleanly to Samba 3.4.3 in Debian :-( Also, is this patch likely to have any implications for Windows XP? I am having some weird issues under XP now, I don't know what triggered it, and am wondering if this patch is likely to help, or if it is Windows 7 specific. Thanks
i've applied this patch on 3.4.3 running on Solaris 10 |(sparc) The 0x000006f7 error is gone, but now i'm getting 0x00000002 error on 32-bit Vista en Win7 clients. On 64-bit clients - it is 0x0000000d error. WinXP client can load the drivers without any problems. All clients are freshly installed with latest service pack and patch level. Tested with Oce Native Family PS v.4.4 and HP universal print driver for Windows PS v.5.0 It is also not possible to upload the drivers from Vista or Win7 clients. You can go through the procedure, but when you click on finish, close printer properties and open it again - no driver installed... I'll upload logs in a few minutes...
the level 10 log is to big, so i've put it in my homedir: log level 10 of a 32-bits Vista client trying to connect to a samba printer: http://www.few.vu.nl/~mzouskov/samba/tarakan-vista.d10.connect_to_printer.log Adding printer drivers from 32-bit Vista client did went well. If i connect from XP client, it gets the drivers. If i connect from Vista client - error 0x00000002...
Ok, this is an endianness problem that we have addressed in master but not yet in the v3-4-test patch. Fixed patch coming soon.
Created attachment 5026 [details] 3-4-test version of the patch (incl. little/bigendian fixes)
Comment on attachment 5026 [details] 3-4-test version of the patch (incl. little/bigendian fixes) looks good
Karolin, please push to v3-4-test. (this is v3-4-test only). Unfortunately this only the first step on resolving this bug, so please leave it open.
(In reply to comment #15) > Karolin, please push to v3-4-test. (this is v3-4-test only). > > Unfortunately this only the first step on resolving this bug, so please leave > it open. > Done.
applied the latest patch o the clean samba 3.4.3 tree... the new patch doesn't seem to work either. the same 0x00000002 pops up error under Vista. WinXP client gets the drivers. d10 log file: http://www.few.vu.nl/~mzouskov/samba/tarakan-vista.d10.1_dec.log One other observation: sins we've enabled 3.4.2 on our file servers(all Solaris 10 sparc) users complaining about bad performance, e.g. windows profiles (located in homedirs) being loaded too long etc. perhaps this should be reported as a separated bug. After applying the latest patch on the test server, the test server seems to be noticeably slower than for example running 3.3.4 or 3.3.9.
Created attachment 5068 [details] remaining patch from master This should resolve the enum_printer_key issues.
this is a blocker.
Created attachment 5082 [details] remaing patch for master (after much more testing)
Comment on attachment 5082 [details] remaing patch for master (after much more testing) looks good
Karolin, please add the last patch to v3-4-test.
(In reply to comment #22) > Karolin, please add the last patch to v3-4-test. > Done.
x86 WinXP, Vista en Win7 clients seem to be able to get printer drivers from samba 3.4.3 PDC running on on Solaris 10 after applying the last patch. Unfortunately i'm not able to even see the printer properties on x64 clients not connect to them. error 0x0000000d is all i receive...
(In reply to comment #24) > x86 WinXP, Vista en Win7 clients seem to be able to get printer drivers from > samba 3.4.3 PDC running on on Solaris 10 after applying the last patch. great, so we made progress here. > Unfortunately i'm not able to even see the printer properties on x64 clients > not connect to them. error 0x0000000d is all i receive... yeah, see bug #6888. 64bit clients do not work yet.
Hurrah - this is ok for 3.4.4 (IMHO) so long as we add a release note saying 64-bit clients don't currently work for AddPrinter and will be fixed for 3.5.0. Jeremy.
Closing as fixed with 3.4.4 Please reopen if still an issue.