[Samba] Occasional printing to /dev/null with Windows 7
Hello! I'm looking after a small office with several PCs that is using Samba for many years now; however it was Samba 3.2.x with Windows 2000 clients. Now they bought entirely new PCs, of course with Windows 7 pre-installed. I managed to successfully move the setup over to Samba 3.3.10, 3.4.5 and now 3.4.6. Everything is working fine, however one problem stubbornly resists to go away: Ghost Printing. That phrase means that a print job sent to a samba printer is just spooled normally, it appears in the print job list of the Windows client, seemingly is printed and vanishes from the print job list. No error is displayed, the printer is shown as ready and can be seen in the Network Neighborhood just normally. However, the print job that was spooled never gets printed. Printing system is CUPS and it can be deduced from the CUPS logs that the job was never given to CUPS. What drives me mad is that this behavior is sporadic and somehow connected to the logon session of the user. It may happen that the user can print just fine several days in a row and it stops working the next day. Often it helps to just reboot the Windows client PC (just logging the user off and on again leads to The User Profile Service failed the logon - User profile cannot be loaded error in 80% of the cases). Well; of course i combed through the samba smbd.log file at several log levels but honestly, i did not really recognize a error message that is related to cups printing (Samba logs are a bit too much on the chatty side for me...). So, did anybody see similar problems? Or anything i could try to close in on the error? Regards, Peter -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] [LONG] Word 95 behaves strange in file dialog
On 30.05.2004 22:29, Peter Schaefer wrote: Hello! I'm having problems with Word 95 (yes, we still use Office 95) running on W2K SP4. Samba is 3.0.4 running on Debian Testing (package from unstable). However, the problem appeared with 3.0.2a also and 3.0.5 didn't fix this. It was definitely not there with Samba 2.x versions. W2K and Office95 are both German versions. Behaviour: -- In Word, open the File Open dialog. It will present the C:\ folder. However, the default location that is expected to be shown is on a mapped network drive (H:\Documents). Clicking on the H: drive folder within the selection box drops back to C:\ immediately, without error. Ok, now close the file dialog, open the Options dialog and select the tab where you can set the default documents and template paths. When you open an folder selection dialog by the Change...-button you get a Access denied error as soon as a network drive is selected (regardless which one). Logging during this time with log level 3 gets the following into log.smbd: [2004/05/30 14:18:51, 3] smbd/process.c:process_smb(890) Transaction 8701 of length 92 [2004/05/30 14:18:51, 3] smbd/process.c:switch_message(685) switch message SMBntcreateX (pid 4474) [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_uid_cache(152) fetch sid from uid cache 1000 - S-1-5-21-522452230-244634628-243641563-3000 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 102 - S-1-5-21-522452230-244634628-243641563-513 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 102 - S-1-5-21-522452230-244634628-243641563-513 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 103 - S-1-5-21-522452230-244634628-243641563-512 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 1000 - S-1-5-21-522452230-244634628-243641563-3001 [2004/05/30 14:18:51, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (1000, 102) - sec_ctx_stack_ndx = 0 [2004/05/30 14:18:51, 3] smbd/open.c:open_directory(1356) open_directory: unable to stat name = .. Error was Erfolg [2004/05/30 14:18:51, 3] smbd/error.c:error_packet(118) error packet at smbd/trans2.c() cmd=162 (SMBntcreateX) NT_STATUS_ACCESS_DENIED So, what looks weird for me is Error was *Erfolg* because this partially German wording translates to Error was *Success*. WTF? The icing - All this happens only to a few users and only if Word is started using the Office95 quick launch bar. If Word is started via the start menu or directly in explorer by double-clicking the executable all is ok... Of course the said network drives are all reachable via Windows Explorer and within a command prompt. I'm aware of possible UNC path problems, but even hiding the network neighbourhood and editing the registry to change the UNC paths to mapped drives representation didn't help... So, i'm at the end of my capabilities; i just want to be sure that no bigger problem lures here, waiting to bite me later (in other applications that word). So, ok, replying to myself and referring to http://groups.google.com/groups?hl=enlr=ie=UTF-8safe=off; frame=rightth=41b0ffcb61810f73 seekm=1XxUd-67p-39%40gated-at.bofh.it#link2 : This is a known issue (bug 1345) and has been fixed in the patchset at http://samba.org/~jerry/patches/post-3.0.4/samba-3.0.4.patch FWIW. Regards, Peter -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] [LONG] Word 95 behaves strange in file dialog
Hello! I'm having problems with Word 95 (yes, we still use Office 95) running on W2K SP4. Samba is 3.0.4 running on Debian Testing (package from unstable). However, the problem appeared with 3.0.2a also and 3.0.5 didn't fix this. It was definitely not there with Samba 2.x versions. W2K and Office95 are both German versions. Behaviour: -- In Word, open the File Open dialog. It will present the C:\ folder. However, the default location that is expected to be shown is on a mapped network drive (H:\Documents). Clicking on the H: drive folder within the selection box drops back to C:\ immediately, without error. Ok, now close the file dialog, open the Options dialog and select the tab where you can set the default documents and template paths. When you open an folder selection dialog by the Change...-button you get a Access denied error as soon as a network drive is selected (regardless which one). Logging during this time with log level 3 gets the following into log.smbd: [2004/05/30 14:18:51, 3] smbd/process.c:process_smb(890) Transaction 8701 of length 92 [2004/05/30 14:18:51, 3] smbd/process.c:switch_message(685) switch message SMBntcreateX (pid 4474) [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_uid_cache(152) fetch sid from uid cache 1000 - S-1-5-21-522452230-244634628-243641563-3000 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 102 - S-1-5-21-522452230-244634628-243641563-513 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 102 - S-1-5-21-522452230-244634628-243641563-513 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 103 - S-1-5-21-522452230-244634628-243641563-512 [2004/05/30 14:18:51, 3] passdb/lookup_sid.c:fetch_sid_from_gid_cache(226) fetch sid from gid cache 1000 - S-1-5-21-522452230-244634628-243641563-3001 [2004/05/30 14:18:51, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (1000, 102) - sec_ctx_stack_ndx = 0 [2004/05/30 14:18:51, 3] smbd/open.c:open_directory(1356) open_directory: unable to stat name = .. Error was Erfolg [2004/05/30 14:18:51, 3] smbd/error.c:error_packet(118) error packet at smbd/trans2.c() cmd=162 (SMBntcreateX) NT_STATUS_ACCESS_DENIED So, what looks weird for me is Error was *Erfolg* because this partially German wording translates to Error was *Success*. WTF? The icing - All this happens only to a few users and only if Word is started using the Office95 quick launch bar. If Word is started via the start menu or directly in explorer by double-clicking the executable all is ok... Of course the said network drives are all reachable via Windows Explorer and within a command prompt. I'm aware of possible UNC path problems, but even hiding the network neighbourhood and editing the registry to change the UNC paths to mapped drives representation didn't help... So, i'm at the end of my capabilities; i just want to be sure that no bigger problem lures here, waiting to bite me later (in other applications that word). Best regards, Peter -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
