Bug 10664 - Samba Printing using local port print in IPV6 environment from Windows7 client machine fails
Summary: Samba Printing using local port print in IPV6 environment from Windows7 clien...
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Printing (show other bugs)
Version: 4.4.7
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: printing-maintainers
QA Contact: Samba QA Contact
Depends on:
Reported: 2014-06-18 15:11 UTC by shivappa
Modified: 2021-02-26 22:26 UTC (History)
0 users

See Also:

samba_Ipv6_Win7_Print_fails (1.32 MB, application/octet-stream)
2014-06-18 15:11 UTC, shivappa
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description shivappa 2014-06-18 15:11:34 UTC
Created attachment 10041 [details]

Hi Team,

We are running samba-4.1.4 on fedora-OS and found issue on ipv6 printing.
The detailed description is as below.

1.Installed the printer from Windows7 using local-port print(\\ipv4.address\print).
2.Printer installation succeeded.
3.Test page spooled and job-success.

IPV6:(issue present from 3.6.x)
1.Installed the printer from Windows7 using local-port print(\\ipv6.address\print).
2.Printer installation succeeds.
3.Test page spooled but no job-success.
4.Got  "print_job_end: canceling spool of /var/spool/samba/smbprn.4cLprE (zero length)" error in logfile.

Observations on the issue:
smbprn files present in /var/spool/samba/ are having proper data(header , EOF and all).

smbd_smb2_request_dispatch: opcode[SMB2_OP_CREATE] is happening many times.Then after opcode[SMB2_OP_WRITE] is calling, by that time the new smbprn files are created and having zero length, so job not gets succeed. 

Please help to resolve the issue.

I can provide more debugging details, please let me know how I can help.

Best Regards,
Comment 1 David Disseldorp 2014-06-18 15:40:11 UTC

*** This bug has been marked as a duplicate of bug 10561 ***
Comment 2 shivappa 2016-12-26 06:46:00 UTC
I checked this issue on samba-4.4.7.
Still this issue exists.
Could you please help to resolve this issue. ?
The issue cannot be reproduced from win8 onwards(win8,win8.1,win10,win2k16 No issues)
Is it issue from windows side ?
Comment 3 Björn Jacke 2021-02-26 22:26:27 UTC
using UNC names with colon-separated bare IPv6 addresses is not a good idea anyway and will cause problems at several places; is this also a problem for you if you use proper DNS names that resolve to IPv6 addresses?