RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1452028 - SMB2->Nego->prot->resp->Max_Tras_size=65536. Cannot send data using smbclient but can copy using cifs share
Summary: SMB2->Nego->prot->resp->Max_Tras_size=65536. Cannot send data using smbclient...
Keywords:
Status: CLOSED DUPLICATE of bug 1452003
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: samba
Version: 7.5-Alt
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Andreas Schneider
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-18 07:59 UTC by amitkuma
Modified: 2020-12-14 08:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-05 14:19:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description amitkuma 2017-05-18 07:59:07 UTC
Description of problem:
smbclient cannot send/recv more than 65K packet, if SMB2->Nego-Prot_Resp->Max_Write_Size=65536, Max_Read_Size=65536. Again if share-folder from server is mounted on client machine, smbclient can transfer packets > 65k using put command.

Failure case
    [netApps SMB-server]                    [smb-Client]
      |                                         |
      |  <- Nego Prot Req-                      |                               
      |  - Nego Prot Res(Max Transaction Size=65536)(Max Read Size=65536)(Max Write Size=65536) ->                            |
      |                                         |
                                  //smb-client cannot send packets > 65k


Passing Case
  [netApps SMB-server(xyz.com)]              [smb-Client]
   # mkdir /share
      |                                         |
      |                                    # mkdir /mt
      |              # mount -t cifs -o user,pas //xyz.com/share   /mt 
      |              # ls -ltr /test/*
      |               -rwxrwxrwx. 1 p p 1048576 Feb 8 22:42 tp
      |              //Can upload successfully
      |              # smbclient -E -mSMB2 -U //smb-server-ip/share -c "put tp"  
      |                                         |

Version-Release number of selected component (if applicable):
smbclient-4.4.4-12.el7_3

How reproducible:
Always

Steps to Reproduce:
1. Mentioned above in passing case text
2.
3.

Actual results:

Expected results:


Additional info:

Comment 2 Andreas Schneider 2017-05-30 14:55:11 UTC
https://bugzilla.samba.org/show_bug.cgi?id=12776 might be related.

Comment 3 Andreas Schneider 2017-05-31 15:07:40 UTC
Looking at the traces it uses SMB2 and returns the same error code (STATUS_NOT_SUPPORTED) in the attached traces are reported by bug #1452003

Comment 5 Andreas Schneider 2017-09-05 14:19:36 UTC

*** This bug has been marked as a duplicate of bug 1452003 ***


Note You need to log in before you can comment on or make changes to this bug.