XPost: misc.phone.mobile.iphone, comp.mobile.android
Frank Slootweg and I discussed this years ago and the problem with Android running an SMB server is the ports are 139 (SMB over NetBIOS) and 445 (SMB directly over TCP/IP) both of which are below 1024 and hence impossible on
a non-rooted Android. Since 139 is deprecated, let's just talk about 445.
It's my understanding non jailbroken iOS has the exact same restrictions. Windows expects SMB to be on port 445.
Yet, "SMB Server" apps are advertised on both the Android & iOS App
Stores... so it behooves us to understand how they work.
Android:
"File Manager +": This app, among its many file management features,
advertises the ability to create an SMB server.
<
https://play.google.com/store/apps/details?id=com.alphainventor.filemanager>
"Cx File Explorer": Similar to "File Manager +", this app also offers SMB server functionality.
<
https://play.google.com/store/apps/details?id=com.cxinventor.file.explorer>
iOS:
"FileBrowser Professional": This app is often mentioned for its file
sharing capabilities, including SMB. It's a paid app, and its developers
claim it offers robust SMB support.
https://apps.apple.com/us/app/filebrowser-professional/id854618029
"FE File Explorer": This app also advertises SMB server capabilities.
<
https://apps.apple.com/us/app/fe-file-explorer-pro/id499470113>
Hence the paradox:
A. Neither iOS nor Android can run a server on port 445.
B. Yet, these apps "advertise" SMB-server functionality.
Hmmm... what port do they run on?
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)