On Sunday 19 January 2025 13:04:05 Steve French wrote: > "This allows Linux SMB client to connect to older SMB1 server listening on > non-standard port" > > Pali, > Are there examples you have seen of a case where SMB1 server was > listening on something other than port 139? > > -- > Thanks, > > Steve Yes and I think that have mentioned it in one of the commit messages. Anyway, I will try to explain it a bit more. When running qemu (or other hypervisor) with SMB server in virtual machine and qemu is with userspace networking, then qemu outside of the VM would have to map privileged port 139 to some non-privileged port (above 1024). It is because non-privileged process (like qemu when running by normal user) cannot listen on privileged port. So for host machine or other virtual machine, that SMB server in that VM would not be accessible on port 139, but on any other chosen in qemu settings (or command line argument). For testing environment this is really needed as it would allow to run more SMB servers on one network interface at the same time for example in virtual machines. And if you are asking for the real production example, if I remember correctly I saw backup service which used custom ports 140 and 446 for SMB1 (it was standard port plus one).
