We run identical setups with ubuntu 9.04 (samba 3.3.2) and ubuntu 9.10 (samba 3.4.0). The problem only appeared with 3.4 (ubuntu 9.10 karmic) When trying to connect to a printer from a windows xp workstation, a popup appears that the drivers are not installed correctly on the server. clicking ok finds the drivers just fine (from the server). We used wireshark on the workstation to find the problem. Wireshark reports "SPOOLSS GetPrinter response, level 2[Malformed Packet]" and it does not do this with 3.3.2 and identical printer drivers, service pack for the clients and other config.
Created attachment 5146 [details] Packet capture
Created attachment 5147 [details] smb.conf
Created attachment 5148 [details] log.smbd with log level = 10
This happens with 3.4.3-1ubuntu1~karmic~pgquiles1 also (from the following ppa): https://launchpad.net/~pgquiles/+archive/ppa
Ok, 3.4.4 should revolve this. I know, 3.4.4 has just been released but as soon as people can get their hand on it, can you please test with that release ?
(In reply to comment #5) > Ok, 3.4.4 should revolve this. I know, 3.4.4 has just been released but as soon > as people can get their hand on it, can you please test with that release ? > compiled 3.4.4 and it does not seem to fix this. Also 3.4.4 refuses to create a folder named '3' in W32X86 for some reason. windows dumps the drivers in W32X86 for some reason the complains that the driver it just tried to add is not for this version of windows
(In reply to comment #6) > compiled 3.4.4 and it does not seem to fix this. > > Also 3.4.4 refuses to create a folder named '3' in W32X86 for some reason. > > windows dumps the drivers in W32X86 for some reason the complains that the > driver it just tried to add is not for this version of windows Sure, Windows clients are supposed to upload drivers to the architecture directory (W32X86 in that case), it is the job of the server to move them into their appropriate '3' directory. Can you please upload a log level 10 log.smbd from a client that fails to upload the drivers ?
(In reply to comment #7) > > Sure, Windows clients are supposed to upload drivers to the architecture > directory (W32X86 in that case), it is the job of the server to move them into > their appropriate '3' directory. > > Can you please upload a log level 10 log.smbd from a client that fails to > upload the drivers ? > My bad. It does not have the problem when not installed in a weird prefix. And 3.4.4 seems to do the job on the original issue
Martijn, so we can close this bug as fixed with 3.4.4 ?
(In reply to comment #9) > Martijn, so we can close this bug as fixed with 3.4.4 ? > Yes it fixes the problem reported but i have only tested it with windows xp. Also wireshark does not report malformed packets. And the "Also 3.4.4 refuses to create a folder named '3' in W32X86 for some reason." was due to a wrong configuration on my part. I build a deb with 3.4.4 and no patches (used lucid definitions) and that did fix my problem.
great, thanks for checking.