Bug 527 - XP will not recognize a Samba printer
Summary: XP will not recognize a Samba printer
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Printing (show other bugs)
Version: 3.0.0preX
Hardware: All AIX
: P3 normal
Target Milestone: 3.0.1
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-27 17:47 UTC by Rick Cochran
Modified: 2005-11-14 09:28 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Cochran 2003-09-27 17:47:19 UTC 
Error message: "printer not found on server, unable to connect"

"net view" from XP works
"net print" from XP works
I can print to the printer from Linux using smbclient

If I run 2.2.8a with exactly the same smb.conf, XP is happy.
Comment 1 Rick Cochran 2003-09-28 11:42:57 UTC 
After a Google search and R'ing TFM, I added "use client driver = yes" to
smb.conf.  I was already using "disable spoolss = yes".

This made _absolutely no difference_.
Comment 2 Kenny Root 2003-10-07 14:53:52 UTC 
I have this same problem.  I thought it was because "Windows NT x86" for 
short_archi "W32X86" version "2" and "3" and no "Windows 2000 and XP" that 
points to short_archi "W32X86" version "3".  Can anyone confirm or deny this?
Comment 3 Gerald (Jerry) Carter (dead mail address) 2003-10-07 15:16:59 UTC 
Nope.  Windows 2000 & XP both use the "Windows NT x86" 
architecture string.
Comment 4 Gerald (Jerry) Carter (dead mail address) 2003-11-13 12:12:25 UTC 
I cannot reproduce this against the 
latest SAMBA_3_0 cvs code.  Please retest 3.0.1pre3 
after it is released tomorrow.  Closing this out 
now.
Comment 5 Gerald (Jerry) Carter (dead mail address) 2005-02-07 09:05:58 UTC 
originally reported against one of the 3.0.0rc[1-4] releases.
Cleaning up non-production versions.
Comment 6 Gerald (Jerry) Carter (dead mail address) 2005-11-14 09:28:58 UTC 
database cleanup