# SMB shares on IBM iSeries (Update) **URL:** \ **Category:** Dev Discussions\ **Created:** [March 20, 2026, 10:40am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550 "2026-03-20T10:40:54Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![gabviv](https://forum.rclone.org/user_avatar/forum.rclone.org/gabviv/32/17586_2.png) [@gabviv](https://forum.rclone.org/u/gabviv)\ **Post date:** [March 20, 2026, 10:40am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/1 "2026-03-20T10:40:54Z")
I’m refering to: [Rclone can't connect to smb share](https://forum.rclone.org/t/rclone-cant-connect-to-smb-share/46329) I’ve fixed the problem in the go-smb2 cloudsoda library and issued a pull request. What is the best procedure to get this modification included in rclone ? ---
**Author:** ![gabviv](https://forum.rclone.org/user_avatar/forum.rclone.org/gabviv/32/17586_2.png) [@gabviv](https://forum.rclone.org/u/gabviv)\ **Post date:** [April 1, 2026, 6:50am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/2 "2026-04-01T06:50:12Z")
Hello, my fix has been merged into the main branch of go-smb2: > > > I tried to use rclone that uses your library to connect to an IBM iSeries, but i… got the error: > > \`\`\` > 2024/06/07 16:51:43 DEBUG : rclone: Version "v1.66.0" starting with parameters \["rclone" "ls" "mysource:myshare:" "-vv"\] > 2024/06/07 16:51:43 DEBUG : Creating backend with remote "mysource:myshare" > 2024/06/07 16:51:43 DEBUG : Using config file from "/config/rclone/rclone.conf" > 2024/06/07 16:51:43 DEBUG : pacer: low level retry 1/10 (error couldn't connect SMB: invalid response error: expected session id: 0, got 6270136581206573312) > 2024/06/07 16:51:43 DEBUG : pacer: Rate limited, increasing sleep to 200ms > 2024/06/07 16:51:43 DEBUG : pacer: low level retry 2/10 (error couldn't connect SMB: invalid response error: expected session id: 0, got 6414251769282429184) > 2024/06/07 16:51:43 DEBUG : pacer: Rate limited, increasing sleep to 400ms > \`\`\` > > This patch fixes this strange behaviour of this SMB implementation. Someone knows when the dependency will be included in rclone ? ---
**Author:** ![kapitainsky](https://forum.rclone.org/user_avatar/forum.rclone.org/kapitainsky/32/14450_2.png) [@kapitainsky](https://forum.rclone.org/u/kapitainsky)\ **Post date:** [April 1, 2026, 7:03am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/3 "2026-04-01T07:03:04Z")
Have you tried to update smb dependency and built rclone yourself? To test if it works? ---
**Author:** ![gabviv](https://forum.rclone.org/user_avatar/forum.rclone.org/gabviv/32/17586_2.png) [@gabviv](https://forum.rclone.org/u/gabviv)\ **Post date:** [April 16, 2026, 8:01am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/4 "2026-04-16T08:01:01Z")
Hy, yes, built successfully and run in production since March 20th. ---
**Author:** ![gabviv](https://forum.rclone.org/user_avatar/forum.rclone.org/gabviv/32/17586_2.png) [@gabviv](https://forum.rclone.org/u/gabviv)\ **Post date:** [May 7, 2026, 10:04am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/5 "2026-05-07T10:04:03Z")
Any news about the merge ? ---
**Author:** ![MXWest](https://forum.rclone.org/user_avatar/forum.rclone.org/mxwest/32/21511_2.png) [@MXWest](https://forum.rclone.org/u/MXWest)\ **Post date:** [June 2, 2026, 2:43pm UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/6 "2026-06-02T14:43:20Z")
I am also waiting on this to be merged. This is a huge unlock for me 🙂 Is there anything I can do to help move this issue along? Is @gabviv ' s assertion that it has been tested enough or is there some other task / formal stroken that needs to be done? ---
**Author:** ![ncw](https://forum.rclone.org/user_avatar/forum.rclone.org/ncw/32/18_2.png) [@ncw](https://forum.rclone.org/u/ncw)\ **Post date:** [June 3, 2026, 9:30am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/7 "2026-06-03T09:30:09Z")
> [@gabviv](#): > > Someone knows when the dependency will be included in rclone ? Send a PR to update the go.mod in rclone I update these once per release cycle but it would need to have made it to a tagged release to be included. ---
**Author:** ![gabviv](https://forum.rclone.org/user_avatar/forum.rclone.org/gabviv/32/17586_2.png) [@gabviv](https://forum.rclone.org/u/gabviv)\ **Post date:** [June 11, 2026, 1:07pm UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/8 "2026-06-11T13:07:47Z")
I encountered a problem when building docker image: `go: ``github.com/cloudsoda/go-smb2@v0.0.0-20260401042019-a9059825d591`` requires go >= 1.26.1 (running go 1.25.0; GOTOOLCHAIN=local)` Using 1.26.1 works great. What can I do to send you the PR ? ---
**Author:** ![ncw](https://forum.rclone.org/user_avatar/forum.rclone.org/ncw/32/18_2.png) [@ncw](https://forum.rclone.org/u/ncw)\ **Post date:** [June 11, 2026, 10:48pm UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/9 "2026-06-11T22:48:26Z")
The rclone build supports go 1.25 and 1.26 which is the current and previous versions of go. This is a pretty standard policy in the Go world. I would make an issue with the go-smb repo asking for them to support go1.25... Actually looks like they have done that already so just try a later version > ---
**Author:** ![dithwick](https://forum.rclone.org/user_avatar/forum.rclone.org/dithwick/32/21582_2.png) [@dithwick](https://forum.rclone.org/u/dithwick)\ **Post date:** [July 1, 2026, 11:41am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/10 "2026-07-01T11:41:37Z")
Hi All, I'm just letting you know that I submitted a PR to update the go-smb2 library in rclone ([smb: Provides fixes for IBM iSeries and signature verification. by dithwick · Pull Request #9563 · rclone/rclone](https://github.com/rclone/rclone/pull/9563)) which Nick very quickly processed (thanks Nick). So if you don't build rclone yourself, the fix for the IBM iSeries should be in the next release I guess. ---
**Author:** ![JosetteLeonard](https://forum.rclone.org/letter_avatar_proxy/v4/letter/j/e47c2d/32.png) [@JosetteLeonard](https://forum.rclone.org/u/JosetteLeonard)\ **Post date:** [July 25, 2026, 10:45am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/11 "2026-07-25T10:45:03Z")
Filing a tracking issue on rclone GitHub now — linking to your CloudSoda PR and explaining the iSeries angle — tends to make things go faster once the upstream merge happens. By the time you open the go.mod bump PR, maintainers already have the context. Wrote up the rest of the procedure (and why iSeries breaks things in the first place) here: [Getting a go-smb2 Fix Into Rclone: A Guide for IBM iSeries SMB Compatibility - Port & Patch](https://portandpatch.com/uncategorized/rclone-go-smb2-ibm-iseries-smb-contribution/) ---
**Author:** ![system](https://forum.rclone.org/uploads/default/original/2X/3/39ad3235f6ffec76ccd0c81616bd55697b4c300d.png) [@system](https://forum.rclone.org/u/system)\ **Post date:** [August 24, 2026, 10:45am UTC](https://forum.rclone.org/t/smb-shares-on-ibm-iseries-update/53550/12 "2026-08-24T10:45:23Z")
Closed on August 24, 2026, 10:45am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.