• Re: How do nonroot Android & nonjailbroken iOS run SMB servers to conne

    From Tyrone@21:1/5 to Chris on Wed Apr 16 14:22:57 2025
    XPost: misc.phone.mobile.iphone

    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote:

    Marion <marion@facts.com> wrote:
    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.

    As per usual your understanding of iOS is lacking. There is no such restriction.

    I use "LAN Drive Samba server" and these are the server settings: https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I was able to start the server on an iPad and create a user account with read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine.
    LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can copy photos from the iPad to Windows. Note that the iPad appears as a mapped drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder.
    On Windows 11, I was able to see and copy this file over to Windows. Just
    like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can move files back and forth FROM Windows instead of FROM iOS. Certainly such apps are available for Android as well.

    As I said yesterday, all that is needed is an SMB Server.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Tyrone on Wed Apr 16 10:54:29 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-16 07:22, Tyrone wrote:
    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote:

    Marion <marion@facts.com> wrote:
    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.

    As per usual your understanding of iOS is lacking. There is no such
    restriction.

    I use "LAN Drive Samba server" and these are the server settings:
    https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I was able to start the server on an iPad and create a user account with read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad SMB Server). All very standard Windows networking stuff. So it clearly IS using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder.
    On Windows 11, I was able to see and copy this file over to Windows. Just like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can move files back and forth FROM Windows instead of FROM iOS. Certainly such apps are available for Android as well.

    As I said yesterday, all that is needed is an SMB Server.

    Arlen will now come on and claim you're lying, because he "knows" that
    it can't work.

    :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Alan on Wed Apr 16 19:11:17 2025
    XPost: misc.phone.mobile.iphone

    On Apr 16, 2025 at 1:54:29 PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2025-04-16 07:22, Tyrone wrote:
    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote:

    Marion <marion@facts.com> wrote:
    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.

    As per usual your understanding of iOS is lacking. There is no such
    restriction.

    I use "LAN Drive Samba server" and these are the server settings:
    https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with
    read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >> SMB Server). All very standard Windows networking stuff. So it clearly IS >> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. >> LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >> On Windows 11, I was able to see and copy this file over to Windows. Just >> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing >> this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they >> were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE. >> Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can >> move files back and forth FROM Windows instead of FROM iOS. Certainly such >> apps are available for Android as well.

    As I said yesterday, all that is needed is an SMB Server.

    Arlen will now come on and claim you're lying, because he "knows" that
    it can't work.

    :-)

    No doubt. More "Imaginary Functionality". When all he has to do is use one of his MANY iOS devices and try it.

    Because his track record of things he "knows" about iOS is SO good. Like the classic "Even if only 1 line of code is changed in iOS, Apple rebuilds and sends the ENTIRE iOS to everyone.

    Nevermind that some iOS updates are 40MB and some are 5GB.

    Not to mention how many times this topic has shifted. First it was "its impossible to send a photo from Windows to iOS without using the internet". That, of course, was an absurd lie.

    Now we are at "How do nonroot Android & nonjailbroken iOS run SMB servers to connect to each other & Windows?". Of course this works fine, there are several apps to do this. I have also tried FSharing from the App Store.

    What he knows about iOS couldn't fill a thimble.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Jolly Roger on Wed Apr 16 13:11:13 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-16 12:43, Jolly Roger wrote:
    On 2025-04-16, Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 1:54:29 PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2025-04-16 07:22, Tyrone wrote:
    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote: >>>>
    Marion <marion@facts.com> wrote:
    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.

    As per usual your understanding of iOS is lacking. There is no such
    restriction.

    I use "LAN Drive Samba server" and these are the server settings:
    https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with >>>> read/write access. The folder it creates is a folder in the Files app. >>>>
    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS >>>> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine.
    LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >>>> On Windows 11, I was able to see and copy this file over to Windows. Just >>>> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing
    this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can
    move files back and forth FROM Windows instead of FROM iOS. Certainly such
    apps are available for Android as well.

    As I said yesterday, all that is needed is an SMB Server.

    Arlen will now come on and claim you're lying, because he "knows" that
    it can't work.

    :-)

    No doubt. More "Imaginary Functionality". When all he has to do is use one of
    his MANY iOS devices and try it.

    Because his track record of things he "knows" about iOS is SO good. Like the
    classic "Even if only 1 line of code is changed in iOS, Apple rebuilds and >> sends the ENTIRE iOS to everyone.

    Nevermind that some iOS updates are 40MB and some are 5GB.

    Not to mention how many times this topic has shifted. First it was "its
    impossible to send a photo from Windows to iOS without using the internet". >> That, of course, was an absurd lie.

    Now we are at "How do nonroot Android & nonjailbroken iOS run SMB servers to >> connect to each other & Windows?". Of course this works fine, there are
    several apps to do this. I have also tried FSharing from the App Store.

    What he knows about iOS couldn't fill a thimble.

    Well I'll have you know badgolferman says Arlen apologized to him for something in the past, so we should all just forget all of this and treat Arlen like he /doesn't/ regularly insult Apple users for daring to use a product he has a personal (and irrational) hatred for. 😉


    Arlen is one of the few people on Usenet that I would cheerfully slap
    across is (undoubtedly) smug mouth.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Tyrone on Wed Apr 16 19:43:37 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-16, Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 1:54:29 PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2025-04-16 07:22, Tyrone wrote:
    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote: >>>
    Marion <marion@facts.com> wrote:
    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.

    As per usual your understanding of iOS is lacking. There is no such
    restriction.

    I use "LAN Drive Samba server" and these are the server settings:
    https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with
    read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >>> SMB Server). All very standard Windows networking stuff. So it clearly IS >>> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. >>> LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >>> On Windows 11, I was able to see and copy this file over to Windows. Just >>> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing >>> this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can >>> move files back and forth FROM Windows instead of FROM iOS. Certainly such >>> apps are available for Android as well.

    As I said yesterday, all that is needed is an SMB Server.

    Arlen will now come on and claim you're lying, because he "knows" that
    it can't work.

    :-)

    No doubt. More "Imaginary Functionality". When all he has to do is use one of
    his MANY iOS devices and try it.

    Because his track record of things he "knows" about iOS is SO good. Like the classic "Even if only 1 line of code is changed in iOS, Apple rebuilds and sends the ENTIRE iOS to everyone.

    Nevermind that some iOS updates are 40MB and some are 5GB.

    Not to mention how many times this topic has shifted. First it was "its impossible to send a photo from Windows to iOS without using the internet". That, of course, was an absurd lie.

    Now we are at "How do nonroot Android & nonjailbroken iOS run SMB servers to connect to each other & Windows?". Of course this works fine, there are several apps to do this. I have also tried FSharing from the App Store.

    What he knows about iOS couldn't fill a thimble.

    Well I'll have you know badgolferman says Arlen apologized to him for
    something in the past, so we should all just forget all of this and treat
    Arlen like he /doesn't/ regularly insult Apple users for daring to use a product he has a personal (and irrational) hatred for. 😉

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Tyrone on Wed Apr 16 22:51:32 2025
    XPost: misc.phone.mobile.iphone

    On Wed, 16 Apr 2025 19:11:17 +0000, Tyrone wrote :


    No doubt. More "Imaginary Functionality". When all he has to do is use one of
    his MANY iOS devices and try it.

    I'm always logical where the fact it works says NOTHING about what port it uses, especially if it's using port-forwarding redirection tricks to do it.

    We'd need something like a wireshark scan to know for sure the actual port.

    Because his track record of things he "knows" about iOS is SO good. Like the classic "Even if only 1 line of code is changed in iOS, Apple rebuilds and sends the ENTIRE iOS to everyone.

    Hmmm... sometimes you say *exactly* what nospam says... especially since everyone knows that only in iOS 16 did Apple change the way they released.
    <https://support.apple.com/en-us/HT201224>

    What's interesting is you Apple trolls are ten years behind in the facts.

    Nevermind that some iOS updates are 40MB and some are 5GB.

    Again, this "Tyrone" employs the same logical fallacies as nospam did, when even Apple publicly stated they only changed the way they update in iOS 16.
    <https://support.apple.com/en-ph/guide/security/sec87fc038c2/web>

    The first Rapid Security Response updates for iOS 16.4.1, iPadOS 16.4.1,
    and macOS 13.3.1 (Ventura) started rolling out on May 1, 2023.
    <https://duo.com/decipher/apple-releases-fix-for-actively-exploited-webkit-bug>

    What you Apple trolls don't know about iOS updates would fill a lake.

    Not to mention how many times this topic has shifted. First it was "its impossible to send a photo from Windows to iOS without using the internet". That, of course, was an absurd lie.

    I'll always be sensible and logical since I have no vested interest in defending Apple's honor to the death like you religious zealots often do.

    Without using the Internet or any login/password account, the main ways
    we've together shown iOS to be able to *receive* a file from Windows are:
    a. SMB client/server
    b. LocalSend
    c. The iTunes bloatware abomination
    d. Plus, I listed at least a half dozen other common Apple clusterfucks
    (e.g., iMazing, DearMob iPhone Manager, AnyTrans, etc.)

    For you to claim that I haven't agree they all work (to some value of work)
    is disingenuous on your part, because it was already proven to me.

    Since I'm not an Apple troll, I have no problem agreeing with the tests
    that people ran, as long as their tests & conclusions were logically sound.

    Keep in mind I'm intelligent and well educated; Apple trolls are not.

    Now we are at "How do nonroot Android & nonjailbroken iOS run SMB servers to connect to each other & Windows?". Of course this works fine, there are several apps to do this. I have also tried FSharing from the App Store.

    The purpose of this thread is simply to prove what port is being used.
    Nothing yet, proves what port is being used since redirection is possible.

    Not only is redirection possible, but given how iOS is designed, it's much
    like how Android is designed - so this isn't an us-versus-them issue.

    The question is which port is being used.
    The fact that it works - does NOT prove which port is being used.

    Neither does a displayed value which has been shown by others to be
    editable (e.g., the "localhost" can be anything, apparently).

    What he knows about iOS couldn't fill a thimble.

    I'll ignore that baseless insult simply because I get it that you Apple
    trolls hate me (as you hate anyone to bursts your religious bubble).

    You Apple trolls have no adult defense to facts; so you insult them away.

    Now back to the rather adult technical question asked of both ngs...

    How do we figure out what PORT is being used when SMB servers are employed
    on both iOS and Android? Anyone have an idea how to prove the port used?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Chris on Wed Apr 16 23:19:28 2025
    XPost: misc.phone.mobile.iphone

    On Wed, 16 Apr 2025 22:00:00 -0000 (UTC), Chris wrote :


    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >> SMB Server). All very standard Windows networking stuff. So it clearly IS >> using port 445.

    But it can't be. lol.

    I'm always logically sensible and reasonable, and if I make a mistake, I
    own up to it - but more to the point - I look for proven facts before I
    make my assessments of those facts.

    That's the fundamental difference between a normal person & an Apple troll. Apple trolls are what they are because they guess at everything.

    They're herd animals to the core.
    It's a protective mechanism because they can't resolve fact from fiction.

    So they assume the herd, en masse, does what they themselves, can't do.

    First off, this wouldn't be the first time Apple trolls "claimed" something that they "saw" thinking it proved what they didn't bother to understand.

    Witness, for example, the infamous Snit (with Jolly Roger & nospam's +1)
    *2-1/2 minute Snit video purportedly detailing iOS showing Wi-Fi decibels*
    <https://youtu.be/7QaABa6DFIo> iKooks can't even see the fatal flaw!
    From: Snit <usenet@gallopinginsanity.com> === Michael Glasser

    REFERENCE: Oct 10, 2017, 8:50:05 AM
    *It's a fact iOS devices can't even graph Wi-Fi signal strength over time*
    <https://groups.google.com/g/misc.phone.mobile.iphone/c/PZuec56EWB0>
    <https://groups.google.com/forum/#!topic/misc.phone.mobile.iphone/PZuec56EWB0>

    That video, which JR & nospam high-fived, proves none of the Apple trolls
    ever learned the the difference between a MegabitPerSecond & a Decibel.

    It's almost certainly a similar logical fallacy at work here.
    a. We know the SMB servers work
    b. But we also are aware they can't use ports below 1024 (AFAICT)
    c. So redirection is most likely what's really going on under the covers

    All the triumphant insults by the Apple trolls aside, the technical
    question to resolve is what port do the iOS/Android SMB servers use?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Marion on Thu Apr 17 00:57:46 2025
    XPost: misc.phone.mobile.iphone

    On Apr 16, 2025 at 7:19:28 PM EDT, "Marion" <marion@facts.com> wrote:

    On Wed, 16 Apr 2025 22:00:00 -0000 (UTC), Chris wrote :


    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >>> SMB Server). All very standard Windows networking stuff. So it clearly IS >>> using port 445.

    But it can't be. lol.

    I'm always logically sensible and reasonable, and if I make a mistake, I
    own up to it - but more to the point - I look for proven facts before I
    make my assessments of those facts.

    Uh huh. Sure. I have NEVER seen you admit to being wrong.

    Question. Do you STILL claim that "Even if only 1 line of code is changed, Apple still rebuilds the entire iOS system and sends that to all users"? Even though some iOS updates and 50MB and some are 6GB?

    All the triumphant insults by the normal Apple users aside, the technical question to resolve is what port do the iOS/Android SMB servers use?

    Why does that even matter? It clearly IS using 445, because the standard Windows "Map Network Drive" works.

    But even if its using port 40450 or Magic Server Pixie Dust, so what? IT WORKS. I was able connect my iPad as drive X: in Windows. I moved files both directions, from Windows.

    Free bonus is that DCIM is one of the shares you can map to. It appears to be Read Only, but it is still there. Interesting folder structure in that. I copied a random photo to Windows.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Marion on Thu Apr 17 00:44:19 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-16, Marion <marion@facts.com> wrote:
    On Wed, 16 Apr 2025 19:11:17 +0000, Tyrone wrote :

    No doubt. More "Imaginary Functionality". When all he has to do is
    use one of his MANY iOS devices and try it.

    I'm always logical where the fact it works says NOTHING about what
    port it uses, especially if it's using port-forwarding redirection
    tricks to do it.

    We'd need something like a wireshark scan to know for sure the actual
    port.

    Notice how little Arlen ignores the fact that I already posted proof
    showing an iOS SMB server using the standard port on iOS. And here he is desperately trying to dispute reality, which makes his position
    *literally insane*.

    What you Apple trolls don't know about iOS updates would fill a lake.

    All the proof you need that Arlen is a fucking CLOWN.

    Not to mention how many times this topic has shifted. First it was "its
    impossible to send a photo from Windows to iOS without using the internet". >> That, of course, was an absurd lie.

    I'll always be sensible and logical

    There's nothing sensible or logical about your bullshit claim above. You
    lie like this constantly here, all while slinging schoolyard insults at
    anyone who corrects you.

    I have no vested interest in defending Apple's honori

    No, your vested interest is in attacking all things Apple - often as in
    the case here lying about basic shit that anyone can easily disprove.

    you religious zealots

    Pure projection.

    How do we figure out what PORT is being used when SMB servers are employed
    on both iOS and Android? Anyone have an idea how to prove the port used?

    This from the know-nothing troll who claims to know more than anyone
    else... 🤣

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Chris on Thu Apr 17 01:16:06 2025
    XPost: misc.phone.mobile.iphone

    On Apr 16, 2025 at 6:00:00 PM EDT, "Chris" <ithinkiam@gmail.com> wrote:

    Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote:

    Marion <marion@facts.com> wrote:
    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.

    As per usual your understanding of iOS is lacking. There is no such
    restriction.

    I use "LAN Drive Samba server" and these are the server settings:
    https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow.

    Yeah, it's restricted to get you to buy the full version.

    Yes, I get that. BTW what is the cost? I don't see it mentioned anywhere.

    was able to start the server on an iPad and create a user account with
    read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >> SMB Server). All very standard Windows networking stuff. So it clearly IS >> using port 445.

    But it can't be. lol.

    I know. Hilarious, sad and pathetic all at the same time.

    I can guarantee you Arlen will now go quiet for a few days and completely ignore this topic. He'll start something else.

    He NEVER goes quiet. He is already back claiming that it is now SO VERY important that we figure out what port this is using.

    But it clearly IS using 445 since (1) it shows that it is using 445 and (2)
    the standard Windows "Map Network Drive" dialog works fine.

    But it CAN'T be 445 because Arlen KNOWS it can't be. "His understanding" is
    the way all things work.

    Because he will *never accept he's wrong* from people he's labelled as
    being trolls.

    Yup. Never.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Tyrone on Thu Apr 17 01:31:16 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 6:00:00 PM EDT, "Chris" <ithinkiam@gmail.com> wrote:
    Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 2:35:09 AM EDT, "Chris" <ithinkiam@gmail.com> wrote: >>>> I use "LAN Drive Samba server" and these are the server settings:

    https://i.postimg.cc/8CK3h4bT/IMG-6999.jpg

    Works just fine.

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of
    slow.

    Yeah, it's restricted to get you to buy the full version.

    Yes, I get that. BTW what is the cost? I don't see it mentioned
    anywhere.

    It shows a banner at the top when you launch the app. On my device, the
    price displayed was actually "$0.00". So I went ahead and purchased it
    at $0 without issue and now have the full version. 🙂👍🏼

    One of Arlen's lame trolling tactics is to add a "it must be free"
    restriction when someone shows an app that does what he claims isn't
    possible. He can't do that here. 🤣

    But it can't be. lol.

    I know. Hilarious, sad and pathetic all at the same time.

    I can guarantee you Arlen will now go quiet for a few days and
    completely ignore this topic. He'll start something else.

    He NEVER goes quiet. He is already back claiming that it is now SO
    VERY important that we figure out what port this is using.

    But it clearly IS using 445 since (1) it shows that it is using 445
    and (2) the standard Windows "Map Network Drive" dialog works fine.

    It's using port 445:

    # nc -z rogersiphone 1-65535
    Connection to rogersiphone port 445 [tcp/microsoft-ds] succeeded!
    Connection to rogersiphone port 853 [tcp/domain-s] succeeded!

    But it CAN'T be 445 because Arlen KNOWS it can't be. "His understanding" is the way all things work.

    Because he will *never accept he's wrong* from people he's labelled as
    being trolls.

    Yup. Never.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Marion on Wed Apr 16 18:56:03 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-16 16:19, Marion wrote:
    On Wed, 16 Apr 2025 22:00:00 -0000 (UTC), Chris wrote :


    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >>> SMB Server). All very standard Windows networking stuff. So it clearly IS >>> using port 445.

    But it can't be. lol.

    I'm always logically sensible and reasonable, and if I make a mistake, I
    own up to it - but more to the point - I look for proven facts before I
    make my assessments of those facts.

    That's the fundamental difference between a normal person & an Apple troll. Apple trolls are what they are because they guess at everything.

    They're herd animals to the core.
    It's a protective mechanism because they can't resolve fact from fiction.

    So they assume the herd, en masse, does what they themselves, can't do.

    First off, this wouldn't be the first time Apple trolls "claimed" something that they "saw" thinking it proved what they didn't bother to understand.

    Witness, for example, the infamous Snit (with Jolly Roger & nospam's +1)
    *2-1/2 minute Snit video purportedly detailing iOS showing Wi-Fi decibels*
    <https://youtu.be/7QaABa6DFIo> iKooks can't even see the fatal flaw!
    From: Snit <usenet@gallopinginsanity.com> === Michael Glasser


    I'd rather witness your attempt to deflect from the fact that multiple
    people have shown that that which you claim cannot work...

    ...works.


    REFERENCE: Oct 10, 2017, 8:50:05 AM
    *It's a fact iOS devices can't even graph Wi-Fi signal strength over time*
    <https://groups.google.com/g/misc.phone.mobile.iphone/c/PZuec56EWB0>
    <https://groups.google.com/forum/#!topic/misc.phone.mobile.iphone/PZuec56EWB0>

    That video, which JR & nospam high-fived, proves none of the Apple trolls ever learned the the difference between a MegabitPerSecond & a Decibel.

    It's almost certainly a similar logical fallacy at work here.
    a. We know the SMB servers work
    b. But we also are aware they can't use ports below 1024 (AFAICT)
    c. So redirection is most likely what's really going on under the covers

    All the triumphant insults by the Apple trolls aside, the technical
    question to resolve is what port do the iOS/Android SMB servers use?

    Other than avoiding admitting you're wrong, why would anyone care?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Chris on Wed Apr 16 23:45:53 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-16 23:04, Chris wrote:
    Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 7:19:28 PM EDT, "Marion" <marion@facts.com> wrote:

    On Wed, 16 Apr 2025 22:00:00 -0000 (UTC), Chris wrote :


    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS
    using port 445.

    But it can't be. lol.

    I'm always logically sensible and reasonable, and if I make a mistake, I >>> own up to it - but more to the point - I look for proven facts before I
    make my assessments of those facts.

    Uh huh. Sure. I have NEVER seen you admit to being wrong.

    Question. Do you STILL claim that "Even if only 1 line of code is changed, >> Apple still rebuilds the entire iOS system and sends that to all users"? Even
    though some iOS updates and 50MB and some are 6GB?

    All the triumphant insults by the normal Apple users aside, the technical >>> question to resolve is what port do the iOS/Android SMB servers use?

    Why does that even matter? It clearly IS using 445, because the standard
    Windows "Map Network Drive" works.

    Not very familiar with Windows, but on a mac you can specify the port when connecting to a network share. Only port 445 works with this server.

    Apple also list the ports they commonly use: https://support.apple.com/en-us/103229

    There are many below 1024.


    The point is moot.

    Arlen is only arguing about the port because he can't accept that he was
    wrong and then wrong again.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Tyrone on Thu Apr 17 07:49:06 2025
    XPost: misc.phone.mobile.iphone

    On Thu, 17 Apr 2025 01:16:06 +0000, Tyrone wrote :


    But it clearly IS using 445 since (1) it shows that it is using 445 and (2) the standard Windows "Map Network Drive" dialog works fine.

    I use "Map Network Drive" all day, every day, with Android/Windows Tyrone.
    My entire Android phone is mounted as a Windows drive letter using it.
    <https://i.postimg.cc/BvJdKWzt/webdav06.jpg> Both sdcards mounted

    The fact I can "Map Network Drive" doesn't prove anything about the port.
    <https://i.postimg.cc/k5F8sLbc/filesys01.jpg> Starting WebDAV servers
    <https://i.postimg.cc/RZtw6WC2/filesys02.jpg> Mount Android system filesys
    <https://i.postimg.cc/Zngy0SGT/filesys03.jpg> Look at /etc/resolv.conf

    Since you map network drive also, what is it you claim it's telling us
    about the port that was used by the server?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Jolly Roger on Thu Apr 17 10:52:55 2025
    XPost: misc.phone.mobile.iphone

    On 17 Apr 2025 00:44:19 GMT, Jolly Roger wrote :


    Notice how little Arlen ignores the fact that I already posted proof
    showing an iOS SMB server using the standard port on iOS.

    Yeah, and Snit posted a video showing proof of what you and nospam claimed
    was iOS showing graphical wi-fi signal strength for nearby access points.
    *Snit posting "proof" of iOS showing graphical Wi-Fi signal strength"
    <https://youtu.be/7QaABa6DFIo>
    REFERENCE: Oct 10, 2017, 8:50:05 AM
    *It's a fact iOS devices can't even graph Wi-Fi signal strength over time*
    <https://groups.google.com/g/misc.phone.mobile.iphone/c/PZuec56EWB0>
    <https://groups.google.com/forum/#!topic/misc.phone.mobile.iphone/PZuec56EWB0>

    You insisted then that Snit's video "proved" I was wrong, and yet, none of
    you Apple trolls appears to know the difference between a dBm & a Mbps.

    What's really happening is none of you Apple trolls understands anything.
    It's a defining feature of Apple trolls.

    But I'm not yet saying I know any more than you do, other than I know
    Android & iOS are not binding to any port below 1024 without being rooted.

    So at this point, the main thing I know that you don't know, is that you're wrong (and you're so blissfully sure that you're right, that you'll never figure out how it works - just like Snit who still thinks his video shows graphical Wi-Fi signal strength debugging on iOS).

    To give you ignorant Apple trolls a hint, what's likely happening with SMB
    is the same tech trick that WebDav (or LocalSend for that matter) uses.

    What's interesting is the very fact you Apple trolls are so sure that only
    iOS can do magical things that nobody else can, is why you're Apple trolls.

    You're so stupid you don't realize iOS can't be using ports <1024 (AFAIK).
    In other words, you're so stupid, that you imagine iOS does the impossible.

    Prove me wrong.
    (HINT: Remember that Snit video which you, Jolly Roger, applauded.)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Chris on Thu Apr 17 11:05:12 2025
    XPost: misc.phone.mobile.iphone

    On Thu, 17 Apr 2025 05:58:07 -0000 (UTC), Chris wrote :


    No you don't. You look for anything that you try and squirm away from the facts when they don't match your anti-Apple bias.

    Chris,

    I'm digging for the answer - like an intelligent person should.

    Yet I'm well aware of how Apple trolls think, which is that only Apple can (magically) do the impossible. It's a defining feature of all Apple trolls.

    Another defining feature of all Apple trolls is they have no idea how
    anything works. That's also what makes Apple trolls what they are.

    So you insist - repeatedly - that iOS is binding to ports below 1024.
    When it's not. As far as I know, it's impossible. So it's just not.

    But what is it doing then?
    I do not know (yet).

    That's why I asked the question.
    This is a defining feature of intelligent people, Chris.

    When you "see" Apple doing the impossible, you believe it.
    (Like Apple saying they have special battery chemistry for example.)

    When I see Apple or Android doing what appears to be impossible, I try to figure out _how_ they managed that feat. Because it's clear that they did.

    I get it that you believe that only iOS has special ways to get around the
    port restriction for nonjailbroken/nonrooted devices to bind to ports below 1024, but the fact is iOS isn't special any more than Android is.

    Neither of them can bind to ports lower than 1024 (AFAIK).
    But let's work together to figure out precisely WHAT they're dong, Chris.

    Note that you're the only Apple troll who can actually do that.
    Maybe Tyrone can also. But not Jolly Roger. He's incapable of a GED.
    You, ahem, have a PhD in the biological sciences Chris. Remember?

    Moving forward to resolve the technical question of how they do it,
    it seems we have the same issue with WebDav servers & LocalSend too.

    Let's take the case of Android/iOS WebDAV Servers using Port 80:

    Instead of the WebDAV application directly binding to port 80,
    the operating system (or a privileged system process)
    likely handles incoming HTTP requests on port 80.

    When a request arrives on port 80, the system then forwards
    or redirects that traffic to the actual port the WebDAV server
    application is listening on (which would be a port above 1024).

    This redirection is transparent to the user!

    They access the WebDAV server using http://<device_ip>
    (which defaults to port 80), and the system takes care of
    routing the connection to the correct application port.

    Something like that is almost certainly happening with SMB servers.

    Only you and Tyrone (of the Apple trolls) has the capacity to comprehend
    this, so I'm imploring you to start putting your thinking hat on please.

    I'll eventually figure it out, but I'm asking for help to figure it out.
    That way we all benefit from what we've learned about how this works.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Chris on Thu Apr 17 12:43:29 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 2:04:39 AM EDT, "Chris" <ithinkiam@gmail.com> wrote:

    Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 7:19:28 PM EDT, "Marion" <marion@facts.com> wrote:

    On Wed, 16 Apr 2025 22:00:00 -0000 (UTC), Chris wrote :


    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS
    using port 445.

    But it can't be. lol.

    I'm always logically sensible and reasonable, and if I make a mistake, I >>> own up to it - but more to the point - I look for proven facts before I
    make my assessments of those facts.

    Uh huh. Sure. I have NEVER seen you admit to being wrong.

    Question. Do you STILL claim that "Even if only 1 line of code is changed, >> Apple still rebuilds the entire iOS system and sends that to all users"? Even
    though some iOS updates and 50MB and some are 6GB?

    All the triumphant insults by the normal Apple users aside, the technical >>> question to resolve is what port do the iOS/Android SMB servers use?

    Why does that even matter? It clearly IS using 445, because the standard
    Windows "Map Network Drive" works.

    Not very familiar with Windows, but on a mac you can specify the port when connecting to a network share. Only port 445 works with this server.

    Apple also list the ports they commonly use: https://support.apple.com/en-us/103229

    There are many below 1024.

    What? Actual documentation from Apple?

    No, it CAN'T be.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Alan on Thu Apr 17 12:43:51 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 2:45:53 AM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2025-04-16 23:04, Chris wrote:
    Tyrone <none@none.none> wrote:
    On Apr 16, 2025 at 7:19:28 PM EDT, "Marion" <marion@facts.com> wrote:

    On Wed, 16 Apr 2025 22:00:00 -0000 (UTC), Chris wrote :


    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS
    using port 445.

    But it can't be. lol.

    I'm always logically sensible and reasonable, and if I make a mistake, I >>>> own up to it - but more to the point - I look for proven facts before I >>>> make my assessments of those facts.

    Uh huh. Sure. I have NEVER seen you admit to being wrong.

    Question. Do you STILL claim that "Even if only 1 line of code is changed, >>> Apple still rebuilds the entire iOS system and sends that to all users"? Even
    though some iOS updates and 50MB and some are 6GB?

    All the triumphant insults by the normal Apple users aside, the technical >>>> question to resolve is what port do the iOS/Android SMB servers use?

    Why does that even matter? It clearly IS using 445, because the standard >>> Windows "Map Network Drive" works.

    Not very familiar with Windows, but on a mac you can specify the port when >> connecting to a network share. Only port 445 works with this server.

    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.


    The point is moot.

    Arlen is only arguing about the port because he can't accept that he was wrong and then wrong again.

    Yup.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Marion on Thu Apr 17 13:48:55 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 3:49:06 AM EDT, "Marion" <marion@facts.com> wrote:

    On Thu, 17 Apr 2025 01:16:06 +0000, Tyrone wrote :


    But it clearly IS using 445 since (1) it shows that it is using 445 and (2) >> the standard Windows "Map Network Drive" dialog works fine.

    I use "Map Network Drive" all day, every day, with Android/Windows Tyrone.
    My entire Android phone is mounted as a Windows drive letter using it.
    <https://i.postimg.cc/BvJdKWzt/webdav06.jpg> Both sdcards mounted

    The fact I can "Map Network Drive" doesn't prove anything about the port.
    <https://i.postimg.cc/k5F8sLbc/filesys01.jpg> Starting WebDAV servers
    <https://i.postimg.cc/RZtw6WC2/filesys02.jpg> Mount Android system filesys
    <https://i.postimg.cc/Zngy0SGT/filesys03.jpg> Look at /etc/resolv.conf

    Since you map network drive also, what is it you claim it's telling us
    about the port that was used by the server?

    Jolly Roger just answered that. Try again.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Marion on Thu Apr 17 13:45:59 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 7:05:12 AM EDT, "Marion" <marion@facts.com> wrote:

    On Thu, 17 Apr 2025 05:58:07 -0000 (UTC), Chris wrote :


    No you don't. You look for anything that you try and squirm away from the
    facts when they don't match your anti-Apple bias.

    Chris,

    I'm digging for the answer - like an intelligent person should.

    No. An intelligent person would accept the facts. A petulant child would
    remain in denial.

    Yet I'm well aware of how Apple users think, which is that only Apple can (magically) do the impossible. It's a defining feature of all Apple users.

    Why is this impossible? Do you think it is hard coded into Unix forever that
    no one can ever use port 445? Do you think Apple can't change anything they want? In their own source code?

    Another defining feature of all Apple users is they have no idea how
    anything works. That's also what makes Apple users what they are.

    I know exactly how this works. I have been networking computers since before you were born. The only troll here is you, claiming it can't work because YOU say it can't work. Circular logic much?

    You even admitted that Windows SMB needs port 445. The app SHOWS it is using port 445.

    Therefore, it IS using port 445.

    AGAIN, why don't you DL the app "LAN Drive SMB Server" and try it? BTW this app has existed for a least 6 years. So this is not a new solution.

    Why are you always claiming something is "impossible" that you yourself have never tried? Remember, you ALSO said it was "impossible to copy a photo from Windows to iOS without using internet servers".

    Do you STILL cling to that absurd claim? As we proved, it not only CAN be
    done, but it is easy to do using built-in functionality in both Windows and iOS.

    Of course, after proving that claim to be wrong, you moved the goal posts by stating "No, I meant that I want to do all file moves FROM Windows. But that
    is impossible".

    And here we are, proving that it IS possible by using an SMB Server app on
    iOS. And yet you are still claiming it is "impossible", only because you say
    it is "impossible".

    Now, you are AGAIN changing the "issue" into "What port can this app be using?
    It CAN'T be port 445 because I say so".

    Which is just more deflection away from you being wrong twice about moving files between Windows and iOS. But keep on digging that hole. In a couple more days you will have been proven wrong 3 times.

    What will your next deflection be? "What I REALLY want is to pretend it is 2005 and do all of this over a USB cable"?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Tyrone on Thu Apr 17 14:34:00 2025
    XPost: misc.phone.mobile.iphone

    On Thu, 17 Apr 2025 13:45:59 +0000, Tyrone wrote :


    I'm digging for the answer - like an intelligent person should.

    No. An intelligent person would accept the facts. A petulant child would remain in denial.

    Please remember those words when you decide whether to apologize or not
    when you're forced (by facts) to admit iOS/Android can't bind to port 445.

    Make note of these two very important data points:
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Bonjour/mDNS can make things simpler but it won't change the underlying interaction other than to allow automatic discovery of the hostname (e.g., \\my-iphone.local) and the port (which will still be 445 in this test).
    net use Z: \\192.168.1.24\SharedFiles /user:tyrone mypasswd
    net use Z: \\my-iphone.local\SharedFiles /user:tyrone mypasswd

    Yet I'm well aware of how Apple users think, which is that only Apple can
    (magically) do the impossible. It's a defining feature of all Apple users.

    Why is this impossible? Do you think it is hard coded into Unix forever that no one can ever use port 445? Do you think Apple can't change anything they want? In their own source code?

    Just as it was when you Apple trolls insisted a dBm & a Mbps were the same,
    the reason you are Apple trolls is because you believe Apple is your God.

    Funny, Apple trolls never admitted they were dead wrong then either.
    *Snit video purportedly detailing iOS showing Wi-Fi dBm over time*
    <https://youtu.be/7QaABa6DFIo>
    *It's a fact iOS devices can't even graph Wi-Fi signal strength over time*
    <https://groups.google.com/g/misc.phone.mobile.iphone/c/PZuec56EWB0>
    <https://groups.google.com/forum/#!topic/misc.phone.mobile.iphone/PZuec56EWB0>

    I don't mind that you Apple trolls are wrong. What I mind is you don't know
    the difference between a decibel and a megabitpersecond in that case.

    In this case, you Apple trolls still can't figure out the difference
    between what an iOS SMB server does versus what the iOS SMB client does.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Another defining feature of all Apple users is they have no idea how
    anything works. That's also what makes Apple users what they are.

    I know exactly how this works. I have been networking computers since before you were born. The only troll here is you, claiming it can't work because YOU say it can't work. Circular logic much?

    Heh heh heh... first off, I never said I was a networking expert. In fact,
    I've said many times that I'm NOT a networking expert.

    Yet, just as Alan Baker claims to be an expert in things he knows nothing about, you don't appear to know the difference between a server & a client.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)

    To use the iOS SMB server, you need to run a command like this:
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    You even admitted that Windows SMB needs port 445. The app SHOWS it is using port 445.

    Heh heh heh... as an SMB client.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Therefore, it IS using port 445.

    You need to go back to Costco where you bought that "Networking Expert"
    name plate and return it since you can't figure out the difference between
    what an iOS SMB client does, versus what an iOS SMB server does.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Don't worry. Costco will refund your money... no questions asked.

    AGAIN, why don't you DL the app "LAN Drive SMB Server" and try it? BTW this app has existed for a least 6 years. So this is not a new solution.

    Copying a file from iOS to a Windows share is using the iOS SMB client.
    Copying a file from a Windows share to iOS is using the iOS SMB client.

    Do you even have any idea how to test using an iOS SMB server with Windows?
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Why are you always claiming something is "impossible" that you yourself have never tried? Remember, you ALSO said it was "impossible to copy a photo from Windows to iOS without using internet servers".

    Heh heh heh,... I expressly said I don't doubt that SMB clients can copy a
    file from Windows to iOS and vice versa. The issue was *initiating* it.

    Do you STILL cling to that absurd claim? As we proved, it not only CAN be done, but it is easy to do using built-in functionality in both Windows and iOS.

    First, tell me which device you are sitting at when you initiate that copy.

    Of course, after proving that claim to be wrong, you moved the goal posts by stating "No, I meant that I want to do all file moves FROM Windows. But that is impossible".

    I operate my entire Android interactions over Windows, not on the phone
    itself. That's well known. Why would that have to be crippled on iOS?

    And here we are, proving that it IS possible by using an SMB Server app on iOS. And yet you are still claiming it is "impossible", only because you say it is "impossible".

    heh heh heh... I wonder if you'll apologize as vehemently as you attack
    when you finally realize you mixed up what a server does versus a client.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Note that Bonjour or mDNS can make the discovery hidden so expressly state
    the port so that we're sure of exactly which port is being used please.

    Now, you are AGAIN changing the "issue" into "What port can this app be using?
    It CAN'T be port 445 because I say so".

    A non-rooted/jailbroken iOS/Android device can't bind to port 445 (AFAIK).
    You can pick any reason you like.

    Don't blame me for your inability to like what happens to be how it works.

    Which is just more deflection away from you being wrong twice about moving files between Windows and iOS. But keep on digging that hole. In a couple more
    days you will have been proven wrong 3 times.

    heh heh heh... Let's see how many (if any) of you Apple trolls will
    publicly apologize for not understanding an SMB server versus the client.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    What will your next deflection be? "What I REALLY want is to pretend it is 2005 and do all of this over a USB cable"?

    Simply copying a file from iOS to Windows and back is NOT exercising an SMB server even though you "think" that's what it's doing. It's not.
    \\192.168.1.24:445 (on iOS is using the iOS SMB client)
    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd

    Since you bought a "Networking Expert" placard from Costco, let's test it
    out by having you run the simple "net use" command with your iOS server.

    net use Z: \\192.168.1.24:445\SharedFiles /user:tyrone mypasswd
    If you are correct, then that command should report it succeeded. Right?
    Show us a screenshot of: "The command completed successfully."
    You would then be able to access the files and folders within
    \\192.168.1.24\SharedFiles through File Explorer or by using the
    assigned drive letter.

    If I'm correct, then I predict you'll get a Connection Timeout or Refusal
    with some kind of typical Windows networking error message such as

    a. "No network provider accepted the given network path."
    b. "The network path was not found."
    c. "The remote computer refused the network connection."
    d. A timeout error might also occur as Windows waits for a response

    In summary, when you run the "net use" command above, specifying the port
    you claim is being bound by iOS, it will either work - or it won't work.

    You tell me since you insist it works.
    (I already assume it will fail based on my understanding of how iOS works.)

    Prove me wrong if you're so sure non-jailbroken iOS binds to port 445.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Marion on Thu Apr 17 14:27:40 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 3:49:06 AM EDT, "Marion" <marion@facts.com> wrote:

    On Thu, 17 Apr 2025 01:16:06 +0000, Tyrone wrote :


    But it clearly IS using 445 since (1) it shows that it is using 445 and (2) >> the standard Windows "Map Network Drive" dialog works fine.

    I use "Map Network Drive" all day, every day, with Android/Windows Tyrone.
    My entire Android phone is mounted as a Windows drive letter using it.
    <https://i.postimg.cc/BvJdKWzt/webdav06.jpg> Both sdcards mounted

    The fact I can "Map Network Drive" doesn't prove anything about the port.
    <https://i.postimg.cc/k5F8sLbc/filesys01.jpg> Starting WebDAV servers
    <https://i.postimg.cc/RZtw6WC2/filesys02.jpg> Mount Android system filesys
    <https://i.postimg.cc/Zngy0SGT/filesys03.jpg> Look at /etc/resolv.conf

    Since you map network drive also, what is it you claim it's telling us
    about the port that was used by the server?

    I know because this works in Windows Powershell:

    net use F: \\10.0.0.149\LANDrive /tcpport:445 /USER:Test Test-905
    The command completed successfully.

    AGAIN, stop arguing with zero knowledge. DL the app and try it. BTW you showing how you map drives using port 8080 on Android does not prove that port 445 on iOS does not work.

    Also, this app is free.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Marion on Thu Apr 17 17:02:10 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17, Marion <marion@facts.com> wrote:
    On 17 Apr 2025 00:44:19 GMT, Jolly Roger wrote :

    Notice how little Arlen ignores the fact that I already posted proof
    showing an iOS SMB server using the standard port on iOS.

    Yeah, and Snit

    This isn't about "Snit". Don't change the subject, little Arlen.

    What's really happening is none of you Apple trolls understands anything. It's a defining feature of Apple trolls.

    Pure projection from a know-nothing loser troll who literally spends
    hours every single day trolling the Apple newsgroups. 🤣


    But I'm not yet saying I know any more than you doi

    You say that repeatedly about anyone who calls out your bullshit.

    I know Android & iOS are not binding to any port below 1024 without
    being rooted.

    Wrong. And very easily proved wrong. Yet you refuse to admit it.

    So at this point, the main thing I know that you don't know, is that you're wrong (and you're so blissfully sure that you're right, that you'll never figure out how it works

    LOL... Says the useless troll who can't figure out basic networking...
    🤣

    you ignorant Apple trolls
    you Apple trolls
    you're Apple trolls.
    You're so stupid
    you're so stupid
    you imagine iOS does the impossible.

    Prove me wrong.

    Easy:

    # nc -z rogersiphone 1-65535
    Connection to rogersiphone port 53 [tcp/domain] succeeded!
    Connection to rogersiphone port 445 [tcp/microsoft-ds] succeeded!
    Connection to rogersiphone port 853 [tcp/domain-s] succeeded!

    (HINT: Remember that Snit video which you, Jolly Roger, applauded.)

    Nope, because that never happened. Lies and schoolyard insults are all
    you have to offer this newsgroup.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to All on Thu Apr 17 18:03:04 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid> wrote:

    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with
    read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >> SMB Server). All very standard Windows networking stuff. So it clearly IS >> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. >> LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >> On Windows 11, I was able to see and copy this file over to Windows. Just >> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing >> this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they >> were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE. >> Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can >> move files back and forth FROM Windows instead of FROM iOS. Certainly such >> apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Thank you SO much for the verification. Arlen had dropped your name somewhere in this tangled mess of threads as "proof" that iOS could not do this. All
    the while claiming that I was making all of this up. He claimed "Imaginary Functionality".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Tyrone on Thu Apr 17 17:57:20 2025
    XPost: misc.phone.mobile.iphone

    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I was able to start the server on an iPad and create a user account with read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad SMB Server). All very standard Windows networking stuff. So it clearly IS using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder.
    On Windows 11, I was able to see and copy this file over to Windows. Just like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can move files back and forth FROM Windows instead of FROM iOS. Certainly such apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy
    *from* Windows).

    What was the thing with birds and a stone again!? :-)

    --
    Frank Slootweg, Android (and Windows) *user*.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to All on Thu Apr 17 20:39:37 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid> wrote in How Do nonroot Android...:

    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with
    read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >> SMB Server). All very standard Windows networking stuff. So it clearly IS >> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. >> LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >> On Windows 11, I was able to see and copy this file over to Windows. Just >> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing >> this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they >> were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE. >> Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can >> move files back and forth FROM Windows instead of FROM iOS. Certainly such >> apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Arlen, are you going to FINALLY admit that you are wrong? The limitation of Server ports below 1024 is an Android limitation. NOT iOS. Get it now?

    LAN Drive SMB Server does - in fact - use port 445. Just like we have been telling you. If you actually had a single iOS device, you could have tested
    it yourself.

    But I suspect you will keep on digging that hole, because you are halfway to China already. So why stop now.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Tyrone on Thu Apr 17 21:12:32 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid>
    wrote in How Do nonroot Android...:
    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with
    read/write access. The folder it creates is a folder in the Files app.

    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to
    \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad >>> SMB Server). All very standard Windows networking stuff. So it clearly IS >>> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine. >>> LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >>> On Windows 11, I was able to see and copy this file over to Windows. Just >>> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing >>> this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can >>> move files back and forth FROM Windows instead of FROM iOS. Certainly such >>> apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy
    *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Arlen, are you going to FINALLY admit that you are wrong? The limitation of Server ports below 1024 is an Android limitation. NOT iOS. Get it now?

    LAN Drive SMB Server does - in fact - use port 445. Just like we have been telling you. If you actually had a single iOS device, you could have tested it yourself.

    But I suspect you will keep on digging that hole, because you are halfway to China already. So why stop now.

    Or he'll just slink away for a while hoping everyone will forget about
    this, only to return with a new unrelated troll. 😉

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Jolly Roger on Thu Apr 17 21:35:35 2025
    XPost: misc.phone.mobile.iphone

    On Apr 17, 2025 at 5:12:32 PM EDT, "Jolly Roger" <jollyroger@pobox.com> wrote:

    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid>
    wrote in How Do nonroot Android...:
    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with >>>> read/write access. The folder it creates is a folder in the Files app. >>>>
    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS >>>> using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine.
    LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder. >>>> On Windows 11, I was able to see and copy this file over to Windows. Just >>>> like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing
    this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can
    move files back and forth FROM Windows instead of FROM iOS. Certainly such
    apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available >>> on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy
    *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Arlen, are you going to FINALLY admit that you are wrong? The limitation of >> Server ports below 1024 is an Android limitation. NOT iOS. Get it now?

    LAN Drive SMB Server does - in fact - use port 445. Just like we have been >> telling you. If you actually had a single iOS device, you could have tested >> it yourself.

    But I suspect you will keep on digging that hole, because you are halfway to >> China already. So why stop now.

    Or he'll just slink away for a while hoping everyone will forget about
    this, only to return with a new unrelated troll. 😉

    Still, it is nice to have beaten him into submission. If only for a day. Because everyone reading this knows who was right and who IS the troll.

    Prediction: his next fallback position will be "This server port restriction obviously changed very recently. Because it never worked before". Nevermind that the app we are using is at least 6 years old.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Tyrone on Thu Apr 17 21:47:44 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 5:12:32 PM EDT, "Jolly Roger" <jollyroger@pobox.com> wrote:
    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid>
    wrote in How Do nonroot Android...:
    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with >>>>> read/write access. The folder it creates is a folder in the Files app. >>>>>
    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS
    using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine.
    LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder.
    On Windows 11, I was able to see and copy this file over to Windows. Just
    like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing
    this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can
    move files back and forth FROM Windows instead of FROM iOS. Certainly such
    apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available >>>> on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS >>>> can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy >>>> *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Arlen, are you going to FINALLY admit that you are wrong? The limitation of >>> Server ports below 1024 is an Android limitation. NOT iOS. Get it now? >>>
    LAN Drive SMB Server does - in fact - use port 445. Just like we have been >>> telling you. If you actually had a single iOS device, you could have tested
    it yourself.

    But I suspect you will keep on digging that hole, because you are halfway to
    China already. So why stop now.

    Or he'll just slink away for a while hoping everyone will forget about
    this, only to return with a new unrelated troll. 😉

    Still, it is nice to have beaten him into submission. If only for a day. Because everyone reading this knows who was right and who IS the troll.

    badgolferman would like a word...

    Prediction: his next fallback position will be "This server port restriction obviously changed very recently. Because it never worked before". Nevermind that the app we are using is at least 6 years old.

    🤣👍🏼

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Jolly Roger on Thu Apr 17 15:05:59 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17 14:47, Jolly Roger wrote:
    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 5:12:32 PM EDT, "Jolly Roger" <jollyroger@pobox.com> wrote:
    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid>
    wrote in How Do nonroot Android...:
    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with >>>>>> read/write access. The folder it creates is a folder in the Files app. >>>>>>
    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS
    using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine.
    LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder.
    On Windows 11, I was able to see and copy this file over to Windows. Just
    like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing
    this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can
    move files back and forth FROM Windows instead of FROM iOS. Certainly such
    apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available >>>>> on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS >>>>> can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy >>>>> *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Arlen, are you going to FINALLY admit that you are wrong? The limitation of
    Server ports below 1024 is an Android limitation. NOT iOS. Get it now? >>>>
    LAN Drive SMB Server does - in fact - use port 445. Just like we have been >>>> telling you. If you actually had a single iOS device, you could have tested
    it yourself.

    But I suspect you will keep on digging that hole, because you are halfway to
    China already. So why stop now.

    Or he'll just slink away for a while hoping everyone will forget about
    this, only to return with a new unrelated troll. 😉

    Still, it is nice to have beaten him into submission. If only for a day.
    Because everyone reading this knows who was right and who IS the troll.

    badgolferman would like a word...

    His name is "lickspittle" or "toadie", please!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Alan on Thu Apr 17 22:11:45 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17, Alan <nuh-uh@nope.com> wrote:
    On 2025-04-17 14:47, Jolly Roger wrote:
    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 5:12:32 PM EDT, "Jolly Roger" <jollyroger@pobox.com> wrote:
    On 2025-04-17, Tyrone <none@none.none> wrote:
    On Apr 17, 2025 at 1:57:20 PM EDT, "Frank Slootweg" <this@ddress.is.invalid>
    wrote in How Do nonroot Android...:
    Tyrone <none@none.none> wrote:
    [...]

    [About "LAN Drive Samba server" on iOS:]

    That is one of the apps I looked at yesterday.

    So I installed it today. The free version works fine, but is sort of slow. I
    was able to start the server on an iPad and create a user account with >>>>>>> read/write access. The folder it creates is a folder in the Files app. >>>>>>>
    BTW the "localhost" in the picture above is just the default name used for the
    iPad/iPhone. I changed that to "ipad1'.

    I then did a standard "Map Network Drive" in Windows 11. I connected to >>>>>>> \\ipad1\LANDrive". I entered my name and password (that I setup on the iPad
    SMB Server). All very standard Windows networking stuff. So it clearly IS
    using port 445.

    I then transferred a random PDF file from Windows to the iPad. Worked fine.
    LAN Drive Samba Server also gives you access to DCIM on the iPad. Yes, you can
    copy photos from the iPad to Windows. Note that the iPad appears as a mapped
    drive on Windows. I used drive letter X.

    I then moved a file in the Files app on the iPad into the LANDrive folder.
    On Windows 11, I was able to see and copy this file over to Windows. Just
    like any network drive.

    The DCIM access appears to be read only. At least, in 30 minutes of testing
    this app, I don't see a way to get write access. But you DO have access to it.

    So, the Apple-hating trolls can lose more sleep. Yet ANOTHER thing that they
    were absolutely SURE could not be done (because "iOS is a toy") CAN BE DONE.
    Direct transfers between iOS and Android is possible. You can access the DCIM
    folder. You CAN map an iPad/iPhone as a drive letter on Windows, so you can
    move files back and forth FROM Windows instead of FROM iOS. Certainly such
    apps are available for Android as well.

    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS >>>>>> can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy >>>>>> *from* Windows).

    What was the thing with birds and a stone again!? :-)

    Arlen, are you going to FINALLY admit that you are wrong? The limitation of
    Server ports below 1024 is an Android limitation. NOT iOS. Get it now? >>>>>
    LAN Drive SMB Server does - in fact - use port 445. Just like we have been
    telling you. If you actually had a single iOS device, you could have tested
    it yourself.

    But I suspect you will keep on digging that hole, because you are halfway to
    China already. So why stop now.

    Or he'll just slink away for a while hoping everyone will forget about >>>> this, only to return with a new unrelated troll. 😉

    Still, it is nice to have beaten him into submission. If only for a day. >>> Because everyone reading this knows who was right and who IS the troll.

    badgolferman would like a word...

    His name is "lickspittle" or "toadie", please!

    Notice how both badgolferman and Arlen have gone mute today? 🙂

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Frank Slootweg on Fri Apr 18 04:25:07 2025
    XPost: misc.phone.mobile.iphone

    On 17 Apr 2025 17:57:20 GMT, Frank Slootweg wrote :


    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    Hi Frank,

    The only thing that matters to me is that my beliefs are based on facts.

    You peg me wrong as I can handle the truth - which is all that matters.
    In fact, I *love* that finally we can sit at Windows and control iOS.

    Yes, you are a truly despicable unprepossessing human being, almost devoid
    of personable traits, but, you know some things & you've taught me them.

    For that, I respect your knowledge, in that it was you who first taught me about unrooted Android apps not being able to bind to ports below 1024.

    For that knowledge, I thank you.

    As I said yesterday, all that is needed is an SMB Server.

    Which also closes another open question (control a Windows<->iOS copy *from* Windows).

    You probably saw my extensive tests which proved beyond any doubt in my
    mind, although I still could be wrong, that iOS LAN drive binds to 445.

    I think that's FANTASTIC, and I issued multiple apologies on the Apple newsgroup for doubting that iOS does do this BETTER'n Android does it.

    You don't understand me, mainly due to your idiotic belief systems, but nonetheless, what matters to me only is to know what the facts are.

    And the facts clearly are, with respect to SMB, so far anyway (as things
    can change with more knowledge) that Lan drive does bind to port 445.

    The only thing that matters to me is that my beliefs are based on facts.
    So far, these two facts appear to be backed up in my tests with Windows.

    a. iOS does allow Lan drive to bind to port 445
    b. This means I can copy bidirectionally while sitting at Windows
    c. However, I can't "mount" the drive letter like I do with WebDav

    If someone can explain why "net use Z:" mounts Android as a Windows drive letter when I use a WebDav server on Android, but the same command doesn't mount Android as a drive letter when I use SMB, I'd love to know why.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Marion on Fri Apr 18 10:20:21 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-17 21:25, Marion wrote:
    On 17 Apr 2025 17:57:20 GMT, Frank Slootweg wrote :


    No, such apps (SMB servers which can use port 445) are *not* available
    on Android!

    That's why 'Arlen' can't handle your facts, because in this case, iOS
    can do something which (non-rooted) Android can not.

    Android servers (of any type) can not use ports below 1024.

    Hi Frank,

    The only thing that matters to me is that my beliefs are based on facts.

    Your belief that iOS couldn't allow an app to use port 445 was
    definitely NOT based on fact.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Marion on Fri Apr 18 18:35:32 2025
    XPost: misc.phone.mobile.iphone

    On Apr 18, 2025 at 12:25:07 AM EDT, "Marion" <marion@facts.com> wrote:

    If someone can explain why "net use Z:" mounts Android as a Windows drive letter when I use a WebDav server on Android, but the same command doesn't mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not allow anyone to use port 445 for servers. iOS does. WebDav is using port
    8080. That's why it works on Android.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Tyrone on Fri Apr 18 16:16:34 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-18 11:35, Tyrone wrote:
    On Apr 18, 2025 at 12:25:07 AM EDT, "Marion" <marion@facts.com> wrote:

    If someone can explain why "net use Z:" mounts Android as a Windows drive
    letter when I use a WebDav server on Android, but the same command doesn't >> mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not
    allow anyone to use port 445 for servers. iOS does. WebDav is using port 8080. That's why it works on Android.

    Now, now...

    Arlen's going to come back and tell you that it is a "fact" that the
    http protocol uses port 80!

    😜

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Tyrone on Sat Apr 19 01:21:42 2025
    XPost: misc.phone.mobile.iphone

    On Fri, 18 Apr 2025 18:35:32 +0000, Tyrone wrote :


    If someone can explain why "net use Z:" mounts Android as a Windows drive
    letter when I use a WebDav server on Android, but the same command doesn't >> mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not
    allow anyone to use port 445 for servers. iOS does. WebDav is using port 8080. That's why it works on Android.

    Hi Tyrone,

    Thanks for helping out on this thread, where you and Crhis were the only people, other than me, who did any work to solve teh question being asked.

    As a result of our efforts, the rest of the group has learned a ton.
    Which is exactly how Uenet is supposed to work as a team.

    So I thank you very much for all your effort & patience in testing SMB.

    I'm not a network expert by any stretch of the imagination, so I will defer
    to your greater knowledge level, but just to add value to this
    conversation, I had long ago compiled a listing of the available free SMB servers on Android with information from Frank Slootweg and others, oh,
    maybe five years ago.

    Here is that listing.
    But I do not know how many of these are still developed.

    Free Android SMB Servers:

    SimbaDroid (Open Source)
    https://github.com/buttercookie42/SimbaDroid
    SMB Version(s): SMBv1, SMBv2, SMBv3
    Note: This app does not require root.
    Notes: No user authentication; intended for trusted networks.
    Source: https://xdaforums.com/t/app-4-0-3-no-root-lan-drive-samba-filesharing-server-smb1-and-smb2.3790945/page-12#post-90056889

    Samba Server for Android (deprecated)
    SMB Version(s): SMBv1, SMBv2 (no SMBv3 support) https://play.google.com/store/apps/details?id=com.j4velin.samba
    Note: Root not required.

    Droid NAS
    SMB Version(s): SMBv1 only https://play.google.com/store/apps/details?id=com.ragingdev.droidnas
    Note: This app likely requires root.

    SMB Server for Android (by AL-SULTAN)
    Free and Pro versions available
    SMB Version(s): SMBv3 https://play.google.com/store/apps/details?id=alsultan.smbserver https://play.google.com/store/apps/details?id=alsultan.smbserver.pro
    Note: This app uses a non-standard port (4445 instead of 445).

    SambaDroid (deprecated)
    SMB Version(s): SMBv1 only
    https://github.com/SambaDroid
    Note: Currently only available as source, no GitHub APK anymore.

    Samba Server Pro by Ice Cold Apps
    SMB Version(s): SMBv1, SMBv2
    Note: Likely requires root.
    Availability: Available on APK sites.

    File Server (by The Olive Tree) (deprecated)
    SMB Version(s): SMBv2 only (no SMBv3 support) https://play.google.com/store/apps/details?id=com.olive.file.server
    Note: This app likely requires root.

    LAN drive - SAMBA Server by Webrox https://download.cnet.com/lan-drive-samba-server/3000-20432_4-77826371.html
    SMB Version(s): SMBv1 and SMBv2
    Note: Requires root access.
    Additional Information:

    In addition, it's worth noting that Android itself has had a built-in SMB client (as of Android 8.0 Oreo, supporting SMBv2 and SMBv3). This is
    typically accessible through file explorer apps and doesn't turn your
    Android device into a server but allows it to connect to other SMB servers
    as a client.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Marion on Fri Apr 18 19:27:18 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-18 18:21, Marion wrote:
    On Fri, 18 Apr 2025 18:35:32 +0000, Tyrone wrote :


    If someone can explain why "net use Z:" mounts Android as a Windows drive >>> letter when I use a WebDav server on Android, but the same command doesn't >>> mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not
    allow anyone to use port 445 for servers. iOS does. WebDav is using port
    8080. That's why it works on Android.

    Hi Tyrone,

    Thanks for helping out on this thread, where you and Crhis were the only people, other than me, who did any work to solve teh question being asked.

    1. There were other people who told you what was what. I was one of them.

    2. You contributed NOTHING to solving this non-existent "question".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Tyrone on Sat Apr 19 10:22:06 2025
    XPost: misc.phone.mobile.iphone

    Tyrone <none@none.none> wrote:
    On Apr 18, 2025 at 12:25:07?AM EDT, "Marion" <marion@facts.com> wrote:

    If someone can explain why "net use Z:" mounts Android as a Windows drive letter when I use a WebDav server on Android, but the same command doesn't mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not
    allow anyone to use port 445 for servers. iOS does. WebDav is using port 8080. That's why it works on Android.

    ['Arlen' messed up his References:, which caused his post to get
    filtered. Probably for the best, considering his insults and phoney compliments, but al.howardknight.net came to the 'rescue'.]

    I have little experience with 'net use', but can't 'Arlen' just use
    the '/tcpport:NNNN' option and set it to the - 1024 or higher - port
    number of the Android SMB server?

    That way, the Android SMB server would not be a Network *Share* that
    Windows could see/use, but it would be a Network *Drive* for Windows.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Tue Apr 22 03:44:54 2025
    XPost: misc.phone.mobile.iphone

    Marion, 2025-04-19 03:21:

    On Fri, 18 Apr 2025 18:35:32 +0000, Tyrone wrote :


    If someone can explain why "net use Z:" mounts Android as a Windows drive >>> letter when I use a WebDav server on Android, but the same command doesn't >>> mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not
    allow anyone to use port 445 for servers. iOS does. WebDav is using port
    8080. That's why it works on Android.

    Hi Tyrone,

    Thanks for helping out on this thread, where you and Crhis were the only people, other than me, who did any work to solve teh question being asked.

    As a result of our efforts, the rest of the group has learned a ton.
    Which is exactly how Uenet is supposed to work as a team.

    So I thank you very much for all your effort & patience in testing SMB.

    I'm not a network expert by any stretch of the imagination, so I will defer to your greater knowledge level, but just to add value to this
    conversation, I had long ago compiled a listing of the available free SMB servers on Android with information from Frank Slootweg and others, oh,
    maybe five years ago.

    Here is that listing.
    But I do not know how many of these are still developed.

    Free Android SMB Servers:

    SimbaDroid (Open Source)
    https://github.com/buttercookie42/SimbaDroid
    SMB Version(s): SMBv1, SMBv2, SMBv3
    Note: This app does not require root.

    It does, if you want to use the default port - and getting Windows to
    connect to port 4550 is not that simple:

    "Due to Android limitations, this app requires root (as on all Unixoid operating systems, it is not possible to open a port < 1024 otherwise,
    and the default SMB port is 445 and Windows doesn't work with anything
    else). Without root, you either need some sort of SMB client which
    allows configuring the port used (SimbaDroid uses port 4450 behind the
    scenes), or some kind of port mapping software to allow Windows to transparently connect to port 4450."

    Notes: No user authentication; intended for trusted networks.
    Source: https://xdaforums.com/t/app-4-0-3-no-root-lan-drive-samba-filesharing-server-smb1-and-smb2.3790945/page-12#post-90056889

    Samba Server for Android (deprecated)
    SMB Version(s): SMBv1, SMBv2 (no SMBv3 support) https://play.google.com/store/apps/details?id=com.j4velin.samba
    Note: Root not required.

    HTTP 404

    Droid NAS
    SMB Version(s): SMBv1 only https://play.google.com/store/apps/details?id=com.ragingdev.droidnas
    Note: This app likely requires root.

    Of course - like *any* app which wants to open a port below 1024.

    [...]

    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use
    custom ports above 1024.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Arno Welzel on Tue Apr 22 02:06:26 2025
    XPost: misc.phone.mobile.iphone

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :


    SimbaDroid (Open Source)
    https://github.com/buttercookie42/SimbaDroid
    SMB Version(s): SMBv1, SMBv2, SMBv3
    Note: This app does not require root.

    It does, if you want to use the default port - and getting Windows to
    connect to port 4550 is not that simple:

    Thanks for the clarifications as I never said I was a networking expert.
    I'm not. That should be abundantly obvious to everyone by now, right?

    Even so, I don't disagree with you. That listing was made long ago.

    "Due to Android limitations, this app requires root (as on all Unixoid operating systems, it is not possible to open a port < 1024 otherwise,
    and the default SMB port is 445 and Windows doesn't work with anything
    else). Without root, you either need some sort of SMB client which
    allows configuring the port used (SimbaDroid uses port 4450 behind the scenes), or some kind of port mapping software to allow Windows to transparently connect to port 4450."

    Understood. Thanks for unearthing that snippet which fits with what we know about Android non root not being able to bind to (SMB) ports below 1024.

    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point.
    1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports
    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot
    3. Even so, SMB server apps exist on both iOS & Android platforms

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Arno Welzel on Tue Apr 22 07:25:20 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-22 03:44, Arno Welzel wrote:
    Marion, 2025-04-19 03:21:

    On Fri, 18 Apr 2025 18:35:32 +0000, Tyrone wrote :


    If someone can explain why "net use Z:" mounts Android as a Windows drive >>>> letter when I use a WebDav server on Android, but the same command doesn't >>>> mount Android as a drive letter when I use SMB, I'd love to know why.

    Because there is no SMB (port 445) server running on Android. Android does not
    allow anyone to use port 445 for servers. iOS does. WebDav is using port >>> 8080. That's why it works on Android.

    Hi Tyrone,

    Thanks for helping out on this thread, where you and Crhis were the only
    people, other than me, who did any work to solve teh question being asked. >>
    As a result of our efforts, the rest of the group has learned a ton.
    Which is exactly how Uenet is supposed to work as a team.

    So I thank you very much for all your effort & patience in testing SMB.

    I'm not a network expert by any stretch of the imagination, so I will defer >> to your greater knowledge level, but just to add value to this
    conversation, I had long ago compiled a listing of the available free SMB
    servers on Android with information from Frank Slootweg and others, oh,
    maybe five years ago.

    Here is that listing.
    But I do not know how many of these are still developed.

    Free Android SMB Servers:

    SimbaDroid (Open Source)
    https://github.com/buttercookie42/SimbaDroid
    SMB Version(s): SMBv1, SMBv2, SMBv3
    Note: This app does not require root.

    It does, if you want to use the default port - and getting Windows to
    connect to port 4550 is not that simple:

    "Due to Android limitations, this app requires root (as on all Unixoid operating systems, it is not possible to open a port < 1024 otherwise,
    and the default SMB port is 445 and Windows doesn't work with anything
    else). Without root, you either need some sort of SMB client which
    allows configuring the port used (SimbaDroid uses port 4450 behind the scenes), or some kind of port mapping software to allow Windows to transparently connect to port 4450."

    Is not iOS an unixoid system inside? It is based on Darwin, which is an open-source Unix-like operating system developed by Apple. It should
    have the same limitation binding to ports below 1024 for user apps. That
    it doesn't is interesting.



    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Tyrone on Tue Apr 22 15:26:39 2025
    XPost: misc.phone.mobile.iphone

    On Thu, 17 Apr 2025 12:43:29 +0000, Tyrone wrote :


    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    What? Actual documentation from Apple?

    No, it CAN'T be.

    If you are an adult - you will apologize publicly to me for saying that.

    Do any of you know how to read? Seriously. Did you even read that doc?
    I posted it more than a week ago, and I read it. You did not even read it.

    The document says nothing about whether third-party iOS applications have
    the ability to bind to or utilize privileged ports, specifically 445.

    I get it that Apple trolls are desperate for respect, but you're not going
    to get respect from me when you post a document that you didn't even read.

    What it says is...
    a. Port 445 is a TCP port.
    b. Port 445 is associated with "Microsoft SMB Domain Server."
    c. Port 445 is listed as a general port used by Apple software products.
    HINT: Files is an "Apple software product" for example.

    The document confirms that port 445 is used by Apple software related to
    SMB (such as the native Files app). However, that document provides no information whatsoever about the ability of third-party iOS applications to bind to or use this port for their own purposes, such as hosting an
    iOS-based SMB server.

    If you're going to try to insult me, at least read your references first. Please.

    It's inherently childish for you to say what you said.
    And, I don't expect an apology but it would be the adult thing to do.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Carlos E.R. on Tue Apr 22 15:27:00 2025
    XPost: misc.phone.mobile.iphone

    On Tue, 22 Apr 2025 07:25:20 +0200, Carlos E.R. wrote :


    Is not iOS an unixoid system inside? It is based on Darwin, which is an open-source Unix-like operating system developed by Apple. It should
    have the same limitation binding to ports below 1024 for user apps. That
    it doesn't is interesting.

    Hi Carlos,

    I would agree, especially as I researched the question before asking it.

    I couldn't find anything from Apple that says what it does, either way.
    Nor from anywhere else.

    In fact, everything I could find online said iOS acts like Unix when it
    came to privileged ports. And yet, the Apple folks told me otherwise.

    Had I trusted them more than I generally do, I may have more easily
    accepted what the Apple folks like Jolly Roger claimed; but there's a
    mistrust of people like Jolly Roger, especially as he *still* claims that
    iOS can graphically display both Wi-Fi and cellular signal strength for all nearby access points, which it does not - and which it never did.

    Sigh. This time, they were right and I was the one who was dead wrong.
    Heh heh heh... life throws a turn when an Apple troll is actually correct.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Chris on Tue Apr 22 15:26:30 2025
    XPost: misc.phone.mobile.iphone

    On Thu, 17 Apr 2025 06:04:39 -0000 (UTC), Chris wrote :


    Apple also list the ports they commonly use: https://support.apple.com/en-us/103229

    There are many below 1024.

    C'mon Chris,

    Did you even *read* that document (which I posted a week ago myself)?
    I did.

    If you read that document, Chris, did you *understand* what it said?
    I did.

    All that document says is that some Apple software uses port 445.
    An example is the native "Files" app uses port 445 as an SMB client.

    What the document DOES NOT say (regarding third-party apps):
    1. It does not state whether third-party iOS applications are
    permitted or restricted from binding to privileged ports in general.
    2. It makes no specific mention of whether third-party iOS applications
    can bind to port 445.
    3. It does not discuss the security implications or permissions
    required for third-party apps to use specific ports.
    4. It does not differentiate between the port usage of Apple's
    own applications and third-party applications.

    The document says nothing, Chris.
    And I posted it a week ago proving that.

    I could find nothing in Apple's documentation that said anything about the ability of 3rd-party apps to bind to privileged ports such as port 445.

    If you can find *that* document, then it would be worth the post.
    But just posting a random Apple document isn't helpful here.

    Especially as the Apple trolls jumped on it without even reading it.
    They think any mention of port 445 is vindication of their belief systems.

    It's not.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Jolly Roger on Tue Apr 22 15:38:16 2025
    XPost: misc.phone.mobile.iphone

    On 17 Apr 2025 17:02:10 GMT, Jolly Roger wrote :


    Lies and schoolyard insults are all
    you have to offer this newsgroup.

    :)

    I get it that your whole life people told you that you were stupid, Jolly Roger, and I get it that you told us you never could earn your GED either.

    I feel sorry for you, Jolly Roger. I really do.

    I graduated from the finest schools in the country and retired early from decades of working in the silicon valley at highly technical software
    companies working on the toughest problems known to mankind Jolly Roger.

    You barely made it through high school. Your whole life you've been a herd animal trying to compensate for your lack of ability to analyze things.

    In this case, Tyrone & Chris were correct. You simply followed the herd.
    This time you were correct. I'm *happy* for you Jolly Roger.

    I really am.

    I'm *happy* that following the herd has worked this time for you Jolly
    Roger, but it didn't work for you when you followed Snit, now did it?

    *Snit posting "proof" of iOS showing graphical Wi-Fi signal strength"
    <https://youtu.be/7QaABa6DFIo>
    REFERENCE: Oct 10, 2017, 8:50:05 AM
    *It's a fact iOS devices can't even graph Wi-Fi signal strength over time*
    <https://groups.google.com/g/misc.phone.mobile.iphone/c/PZuec56EWB0>
    <https://groups.google.com/forum/#!topic/misc.phone.mobile.iphone/PZuec56EWB0>

    I love when you post though, as I never filter you. I filter Snit.
    I filter Jolly Roger. I filter Joerg Lorenz. But I do not filter you.

    You are the canonical Apple owner.
    I love when you post, Jolly Roger.

    Because when you post, I learn how your strange mind actually works.
    Please keep posting as you are the epitome of the canonical Apple owner.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Marion on Tue Apr 22 16:05:21 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-22, Marion <marion@facts.com> wrote:
    On 17 Apr 2025 17:02:10 GMT, Jolly Roger wrote :

    Lies and schoolyard insults are all you have to offer this newsgroup.

    :)

    I get it that your whole life people told you that you were stupid,
    Jolly Roger, and I get it that you told us you never could earn your
    GED either.

    I feel sorry for you, Jolly Roger. I really do.

    I graduated from the finest schools in the country and retired early
    from decades of working in the silicon valley at highly technical
    software companies working on the toughest problems known to mankind
    Jolly Roger.

    You barely made it through high school. Your whole life you've been a
    herd animal trying to compensate for your lack of ability to analyze
    things.

    The fact that you respond with more schoolyard insults and lies says it
    all, little Arlen.

    In this case, Tyrone & Chris were correct. You simply followed the
    herd. This time you were correct. I'm *happy* for you Jolly Roger.

    Sure, little boy. I'm the one ho showed definitively that SMB servers on
    iOS do indeed use the default privileged port - much to your dismay. And
    the fact that I know more about basic networking and Apple devices than
    you eats you alive, little boy. It's one of the reasons you regularly
    mention my name out of the blue in posts I don't even participate in. I
    live in your tortured little head 24/7. And I'm really happy for you for
    that. I really am. 🙂

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Marion on Tue Apr 22 15:46:01 2025
    XPost: misc.phone.mobile.iphone

    On Tue, 22 Apr 2025 15:38:16 -0000 (UTC), Marion wrote :


    I love when you post though, as I never filter you. I filter Snit.
    I filter Jolly Roger. I filter Joerg Lorenz. But I do not filter you.

    Ooops. That was supposed to be I filter out Alan Baker (et al.).

    Nothing that trio ever said is meaningful. Nothing adds value. In fact, everything Snit, Alan Baker & Joerg Lorenz says actually subtracts value.

    What's no longer shocking is that there are people like that trio who can
    go through their entire lives, and never once say anything meaningful.

    One tutorial is more value than the three have ever provided, combined.
    It's a bitch for me to write a killfile since I don't use a newsreader.

    But I bothered to put them into my regular expressions as reading anything posted by Alan Baker, Snit, or Joerg Lorenz is a waste of usable energy.

    But Jolly Roger?
    He's different.

    Jolly Roger is a herd animal to the core.
    He looks to the herd for affirmation of his religious choices.

    Hence, I read *everything* that Jolly Roger posts to the Usenet newsgroups.
    As his posts teach me exactly how the canonical Apple owner thinks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Thu Apr 24 18:57:15 2025
    XPost: misc.phone.mobile.iphone

    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use: https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does
    not mean you can install and run an *APP* on iOS which does this.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Thu Apr 24 19:02:33 2025
    XPost: misc.phone.mobile.iphone

    Carlos E.R., 2025-04-22 07:25:

    On 2025-04-22 03:44, Arno Welzel wrote:
    [...]
    "Due to Android limitations, this app requires root (as on all Unixoid
    operating systems, it is not possible to open a port < 1024 otherwise,
    and the default SMB port is 445 and Windows doesn't work with anything
    else). Without root, you either need some sort of SMB client which
    allows configuring the port used (SimbaDroid uses port 4450 behind the
    scenes), or some kind of port mapping software to allow Windows to
    transparently connect to port 4450."

    Is not iOS an unixoid system inside? It is based on Darwin, which is an open-source Unix-like operating system developed by Apple. It should
    have the same limitation binding to ports below 1024 for user apps. That
    it doesn't is interesting.

    Correct - iOS also does not allow using ports below 1024 for *servers* implemented in user installable apps without privileged access.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Thu Apr 24 19:00:57 2025
    XPost: misc.phone.mobile.iphone

    Marion, 2025-04-22 04:06:

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use
    custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point. 1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports

    No. iOS has the same limitation. User installable apps can not use ports
    below 1024.

    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot
    3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Thu Apr 24 10:04:05 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-24 10:00, Arno Welzel wrote:
    Marion, 2025-04-22 04:06:

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use >>> custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point. >> 1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports

    No. iOS has the same limitation. User installable apps can not use ports below 1024.

    I'm sorry, but that has been PROVEN to be false.

    I have an iPhone 16 by my right hand and I can start an app called "LAN
    drive" and it will serve files using SMB on port 445.

    I've done it.

    Others have done it.


    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot >> 3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!
    Not true on iOS.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Thu Apr 24 10:16:30 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-24 10:02, Arno Welzel wrote:
    Carlos E.R., 2025-04-22 07:25:

    On 2025-04-22 03:44, Arno Welzel wrote:
    [...]
    "Due to Android limitations, this app requires root (as on all Unixoid
    operating systems, it is not possible to open a port < 1024 otherwise,
    and the default SMB port is 445 and Windows doesn't work with anything
    else). Without root, you either need some sort of SMB client which
    allows configuring the port used (SimbaDroid uses port 4450 behind the
    scenes), or some kind of port mapping software to allow Windows to
    transparently connect to port 4450."

    Is not iOS an unixoid system inside? It is based on Darwin, which is an
    open-source Unix-like operating system developed by Apple. It should
    have the same limitation binding to ports below 1024 for user apps. That
    it doesn't is interesting.

    Correct - iOS also does not allow using ports below 1024 for *servers* implemented in user installable apps without privileged access.



    I'm sorry, but that's incorrect.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Thu Apr 24 10:18:10 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-24 09:57, Arno Welzel wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does
    not mean you can install and run an *APP* on iOS which does this.



    And yet, one clearly CAN do that on iOS.

    Don't take my word for it: download "LAN drive SAMBA Server Client" from
    the iOS App Store and try it for yourself!

    :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Arno Welzel on Thu Apr 24 17:45:21 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-24, Arno Welzel <usenet@arnowelzel.de> wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does
    not mean you can install and run an *APP* on iOS which does this.

    Way to show the world you have no idea what you are talking about,
    Junior.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Arno Welzel on Thu Apr 24 17:47:54 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-24, Arno Welzel <usenet@arnowelzel.de> wrote:
    Marion, 2025-04-22 04:06:
    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use >>> custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point. >> 1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports

    No. iOS has the same limitation. User installable apps can not use ports below 1024.

    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot >> 3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!

    Bullshit:

    # nc -z rogersiphone 445
    Connection to rogersiphone port 445 [tcp/microsoft-ds] succeeded!

    Say more stupid things.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tyrone@21:1/5 to Arno Welzel on Thu Apr 24 23:54:00 2025
    XPost: misc.phone.mobile.iphone

    On Apr 24, 2025 at 1:00:57 PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:

    Marion, 2025-04-22 04:06:

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use >>> custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point. >> 1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports

    No. iOS has the same limitation. User installable apps can not use ports below 1024.

    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot >> 3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!

    No Arlen, you are still wrong. iOS allows this. We are doing this right now.
    On port 445. SMB SERVER on port 445 on iOS.

    It is a fact Arlen.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Fri Apr 25 17:11:07 2025
    XPost: misc.phone.mobile.iphone

    Jolly Roger, 2025-04-24 19:45:

    On 2025-04-24, Arno Welzel <usenet@arnowelzel.de> wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does
    not mean you can install and run an *APP* on iOS which does this.

    Way to show the world you have no idea what you are talking about,
    Junior.

    What iOS app provides SSH or HTTP as *SERVER* and allows INCOMING
    CONNECTIONS from other computers to port 22 or port 80?


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Fri Apr 25 17:10:18 2025
    XPost: misc.phone.mobile.iphone

    Alan, 2025-04-24 19:18:

    On 2025-04-24 09:57, Arno Welzel wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does
    not mean you can install and run an *APP* on iOS which does this.



    And yet, one clearly CAN do that on iOS.

    Don't take my word for it: download "LAN drive SAMBA Server Client" from
    the iOS App Store and try it for yourself!

    This is a *CLIENT* and NOT A SERVER!

    We talk about SERVERS! Which means apps which open ports below 1024 for INCOMING CONNECTIONS!


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Tyrone on Fri Apr 25 15:13:14 2025
    XPost: misc.phone.mobile.iphone

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too)
    late to the thread and apparently has not been following the thread, so
    he was not aware that iOS *can* use servers on ports below 1024.

    AFAICT from the comments from You Guys (TM), Arno's comment on "user installable apps" is incorrect, because AFAIK the iOS SMB server used
    ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Fri Apr 25 17:13:47 2025
    XPost: misc.phone.mobile.iphone

    Alan, 2025-04-24 19:04:

    On 2025-04-24 10:00, Arno Welzel wrote:
    Marion, 2025-04-22 04:06:

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024 >>>> for servers without root access. And not every SMB client is able to use >>>> custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point. >>> 1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports >>
    No. iOS has the same limitation. User installable apps can not use ports
    below 1024.

    I'm sorry, but that has been PROVEN to be false.

    I have an iPhone 16 by my right hand and I can start an app called "LAN drive" and it will serve files using SMB on port 445.

    You refer to this?

    <https://apps.apple.com/us/app/lan-drive-samba-server-client/id1317727404?platform=iphone>

    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot >>> 3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!
    Not true on iOS.

    I stand corrected and wonder why iOS allows this, since it is also a
    "unixoid" system like Android.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Fri Apr 25 17:14:38 2025
    XPost: misc.phone.mobile.iphone

    Jolly Roger, 2025-04-24 19:47:

    Say more stupid things.

    Gurrglglllgelgk, brabble, sadlkfgjasdlkf8ow wqeiojdqwoidqwejoid qwwmdeqwoideewodqw dklqwdqwekljdowd329?JD)("J)(DEJ)?"JUß9ed

    Stupid enough?


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Fri Apr 25 17:15:33 2025
    XPost: misc.phone.mobile.iphone

    Tyrone, 2025-04-25 01:54:

    On Apr 24, 2025 at 1:02:33 PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers*
    implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    What is a "Y.A.S.P."?

    Well - I stand corrected - so what?


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Fri Apr 25 17:33:09 2025
    XPost: misc.phone.mobile.iphone

    Frank Slootweg, 2025-04-25 17:13:

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers*
    implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too)
    late to the thread and apparently has not been following the thread, so
    he was not aware that iOS *can* use servers on ports below 1024.

    AFAICT from the comments from You Guys (TM), Arno's comment on "user installable apps" is incorrect, because AFAIK the iOS SMB server used
    ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that
    like any Linux based systems. But iOS is not Linux based and of course
    it may be that Apple decided to handle that in a different way.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Arno Welzel on Fri Apr 25 15:38:59 2025
    XPost: misc.phone.mobile.iphone

    Arno Welzel <usenet@arnowelzel.de> wrote:
    Alan, 2025-04-24 19:18:

    On 2025-04-24 09:57, Arno Welzel wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does >> not mean you can install and run an *APP* on iOS which does this.



    And yet, one clearly CAN do that on iOS.

    Don't take my word for it: download "LAN drive SAMBA Server Client" from the iOS App Store and try it for yourself!

    This is a *CLIENT* and NOT A SERVER!

    We talk about SERVERS! Which means apps which open ports below 1024 for INCOMING CONNECTIONS!

    Arno, before shouting, you should *read* what people write and *follow
    the thread*.

    Yes, it's *also* a (SMB) client, but - as the name clearly says - also
    a (SMB) server.

    The App Store entry clearly says "Network drive - Samba server" at the
    very top and:

    "LAN Drive is a powerfull and easy SMB server - also known as SAMBA
    server - designed for filesharing.
    LAN drive is also a powerfull client to connect to SMB servers, and
    view/copy/paste files easily."

    Look at the screenshots (the iPhone ones are a bit clearer), which
    clearly says the Server is/uses "SMB TCP 445".

    'LAN drive SAMBA Server Client' <https://apps.apple.com/us/app/lan-drive-samba-server-client/id1317727404>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Arno Welzel on Fri Apr 25 16:00:50 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25, Arno Welzel <usenet@arnowelzel.de> wrote:
    Alan, 2025-04-24 19:18:
    On 2025-04-24 09:57, Arno Welzel wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does >>> not mean you can install and run an *APP* on iOS which does this.

    And yet, one clearly CAN do that on iOS.

    Don't take my word for it: download "LAN drive SAMBA Server Client" from
    the iOS App Store and try it for yourself!

    This is a *CLIENT* and NOT A SERVER!

    We talk about SERVERS! Which means apps which open ports below 1024 for INCOMING CONNECTIONS!

    My god, you trolls are fucking dumb, which is ironic considering you guys regularly claim Apple users are idiots.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Arno Welzel on Fri Apr 25 16:02:42 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25, Arno Welzel <usenet@arnowelzel.de> wrote:
    Jolly Roger, 2025-04-24 19:45:

    On 2025-04-24, Arno Welzel <usenet@arnowelzel.de> wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does >>> not mean you can install and run an *APP* on iOS which does this.

    Way to show the world you have no idea what you are talking about,
    Junior.

    What iOS app provides SSH or HTTP as *SERVER* and allows INCOMING
    CONNECTIONS from other computers to port 22 or port 80?

    There are several available, but this one was discussed right here in
    this very thread:

    <https://apps.apple.com/us/app/lan-drive-samba-server-client/id1317727404?uo=4&at=11l6hc&ct=fnd>

    If you'd bother to read the thread rather than jumping into the middle
    of it and screaming falsehoods you'd know that.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Frank Slootweg on Fri Apr 25 17:06:28 2025
    XPost: misc.phone.mobile.iphone

    On 25 Apr 2025 15:38:59 GMT, Frank Slootweg wrote :


    'LAN drive SAMBA Server Client' <https://apps.apple.com/us/app/lan-drive-samba-server-client/id1317727404>

    Frank is correct as I tested it myself, and unless I made a mistake in my testing (which I documented & posted like any good scientist should), that particular user-installed iOS app does appear to bind to port 445.

    Note that there is also an Android version from the same developer.
    *[APP][4.0.3+][NO Root] LAN drive Samba Filesharing Server SMB1 & SMB2*
    <https://xdaforums.com/t/app-4-0-3-no-root-lan-drive-samba-filesharing-server-smb1-and-smb2.3790945/page-12#post-90056889>

    Since I'm happy with WebDAV servers, I'm not going to test this SMB server
    on Android, but if others test it, I would be interested in the results.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Carlos E.R. on Fri Apr 25 18:41:32 2025
    XPost: misc.phone.mobile.iphone

    Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2025-04-25 17:33, Arno Welzel wrote:
    [...]
    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that like any Linux based systems. But iOS is not Linux based and of course
    it may be that Apple decided to handle that in a different way.

    iOS an unixoid system inside. It is based on Darwin, which is an
    open-source Unix-like operating system developed by Apple. It should
    have the same limitation binding to ports below 1024 for user apps. That
    it doesn't is interesting.

    Indeed both iOS and Android are an unixoid system inside. But as both
    don't have a root-user concept available for the user, they have to
    handle root-capability in some way. Apparently Apple has chosen to give
    the user *this* (binding to ports below 1024) root-capability, while
    Google has chosen not to do so.

    IMO, the 'no-root' philosophy of Android (and iOS?) is broken from the
    start. I can't access my files in Android\data etc.? I can't run a
    server on a <1024 port? Etc., etc.. But I *can* (f.e. Samsung) unlock
    the bootloader and blow everything to bits!?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Arno Welzel on Fri Apr 25 20:11:32 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25 17:33, Arno Welzel wrote:
    Frank Slootweg, 2025-04-25 17:13:

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>> implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too)
    late to the thread and apparently has not been following the thread, so
    he was not aware that iOS *can* use servers on ports below 1024.

    AFAICT from the comments from You Guys (TM), Arno's comment on "user
    installable apps" is incorrect, because AFAIK the iOS SMB server used
    ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that
    like any Linux based systems. But iOS is not Linux based and of course
    it may be that Apple decided to handle that in a different way.

    iOS an unixoid system inside. It is based on Darwin, which is an
    open-source Unix-like operating system developed by Apple. It should
    have the same limitation binding to ports below 1024 for user apps. That
    it doesn't is interesting.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Carlos E.R. on Fri Apr 25 19:20:47 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25 11:11, Carlos E.R. wrote:
    On 2025-04-25 17:33, Arno Welzel wrote:
    Frank Slootweg, 2025-04-25 17:13:

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel"
    <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>>> implemented in user installable apps without privileged access.

    Oh look.  Arlen has Y.A.S.P.  That's so cute.

       Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too) >>> late to the thread and apparently has not been following the thread, so
    he was not aware that iOS *can* use servers on ports below 1024.

       AFAICT from the comments from You Guys (TM), Arno's comment on "user >>> installable apps" is incorrect, because AFAIK the iOS SMB server used
    ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that
    like any Linux based systems. But iOS is not Linux based and of course
    it may be that Apple decided to handle that in a different way.

    iOS an unixoid system inside. It is based on Darwin, which is an open-
    source Unix-like operating system developed by Apple. It should have the
    same limitation binding to ports below 1024 for user apps. That it
    doesn't is interesting.


    Not really.

    It's not like the restriction on "privileged ports" is baked into the
    kernel...

    ...and even if it were, it could be unbaked.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Fri Apr 25 19:18:18 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25 08:10, Arno Welzel wrote:
    Alan, 2025-04-24 19:18:

    On 2025-04-24 09:57, Arno Welzel wrote:
    Chris, 2025-04-17 08:04:

    [...]
    Apple also list the ports they commonly use:
    https://support.apple.com/en-us/103229

    There are many below 1024.

    Sure - things like SSH or HTTP use ports below 1024 - so what? That does >>> not mean you can install and run an *APP* on iOS which does this.



    And yet, one clearly CAN do that on iOS.

    Don't take my word for it: download "LAN drive SAMBA Server Client" from
    the iOS App Store and try it for yourself!

    This is a *CLIENT* and NOT A SERVER!

    No. It is quite clearly a server.

    As I am able to connect to my iPhone from my Windows machine and see
    files that are ON MY iPHONE!


    We talk about SERVERS! Which means apps which open ports below 1024 for INCOMING CONNECTIONS!
    And this does that.

    Grow up.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Fri Apr 25 19:19:34 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25 08:13, Arno Welzel wrote:
    Alan, 2025-04-24 19:04:

    On 2025-04-24 10:00, Arno Welzel wrote:
    Marion, 2025-04-22 04:06:

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024 >>>>> for servers without root access. And not every SMB client is able to use >>>>> custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point.
    1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports >>>
    No. iOS has the same limitation. User installable apps can not use ports >>> below 1024.

    I'm sorry, but that has been PROVEN to be false.

    I have an iPhone 16 by my right hand and I can start an app called "LAN
    drive" and it will serve files using SMB on port 445.

    You refer to this?

    <https://apps.apple.com/us/app/lan-drive-samba-server-client/id1317727404?platform=iphone>

    Yup.


    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot >>>> 3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!
    Not true on iOS.

    I stand corrected and wonder why iOS allows this, since it is also a "unixoid" system like Android.
    Hmmmmmm...

    How about: because things change.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Fri Apr 25 19:21:42 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-25 08:15, Arno Welzel wrote:
    Tyrone, 2025-04-25 01:54:

    On Apr 24, 2025 at 1:02:33 PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers*
    implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    What is a "Y.A.S.P."?

    Well - I stand corrected - so what?



    So you acted like an ass before finally realizing you were wrong.

    Try a little more humility next time.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Alan on Sat Apr 26 04:23:02 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-26, Alan <nuh-uh@nope.com> wrote:
    On 2025-04-25 11:11, Carlos E.R. wrote:
    On 2025-04-25 17:33, Arno Welzel wrote:
    Frank Slootweg, 2025-04-25 17:13:

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel"
    <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>>>> implemented in user installable apps without privileged access.

    Oh look.  Arlen has Y.A.S.P.  That's so cute.

       Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too) >>>> late to the thread and apparently has not been following the thread, so >>>> he was not aware that iOS *can* use servers on ports below 1024.

       AFAICT from the comments from You Guys (TM), Arno's comment on "user >>>> installable apps" is incorrect, because AFAIK the iOS SMB server used
    ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that >>> like any Linux based systems. But iOS is not Linux based and of course
    it may be that Apple decided to handle that in a different way.

    iOS an unixoid system inside. It is based on Darwin, which is an open-
    source Unix-like operating system developed by Apple. It should have the
    same limitation binding to ports below 1024 for user apps. That it
    doesn't is interesting.

    Not really.

    It's not like the restriction on "privileged ports" is baked into the kernel...

    ...and even if it were, it could be unbaked.

    Exactly. It's really not the big deal they think it is.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Jolly Roger on Sat Apr 26 19:41:28 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-26 06:23, Jolly Roger wrote:
    On 2025-04-26, Alan <nuh-uh@nope.com> wrote:
    On 2025-04-25 11:11, Carlos E.R. wrote:
    On 2025-04-25 17:33, Arno Welzel wrote:
    Frank Slootweg, 2025-04-25 17:13:

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel"
    <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>>>>> implemented in user installable apps without privileged access.

    Oh look.  Arlen has Y.A.S.P.  That's so cute.

       Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too) >>>>> late to the thread and apparently has not been following the thread, so >>>>> he was not aware that iOS *can* use servers on ports below 1024.

       AFAICT from the comments from You Guys (TM), Arno's comment on "user
    installable apps" is incorrect, because AFAIK the iOS SMB server used >>>>> ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that >>>> like any Linux based systems. But iOS is not Linux based and of course >>>> it may be that Apple decided to handle that in a different way.

    iOS an unixoid system inside. It is based on Darwin, which is an open-
    source Unix-like operating system developed by Apple. It should have the >>> same limitation binding to ports below 1024 for user apps. That it
    doesn't is interesting.

    Not really.

    It's not like the restriction on "privileged ports" is baked into the
    kernel...

    ...and even if it were, it could be unbaked.

    Exactly. It's really not the big deal they think it is.

    To me, it is interesting that it was unbaked, or however it was done.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Carlos E.R. on Sat Apr 26 19:16:01 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-26, Carlos E.R. <robin_listas@es.invalid> wrote:
    On 2025-04-26 06:23, Jolly Roger wrote:
    On 2025-04-26, Alan <nuh-uh@nope.com> wrote:
    On 2025-04-25 11:11, Carlos E.R. wrote:
    On 2025-04-25 17:33, Arno Welzel wrote:
    Frank Slootweg, 2025-04-25 17:13:

    Tyrone <none@none.none> wrote:
    On Apr 24, 2025 at 1:02:33?PM EDT, "Arno Welzel"
    <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>>>>>> implemented in user installable apps without privileged access. >>>>>>>
    Oh look.  Arlen has Y.A.S.P.  That's so cute.

       Arno Welzel isn't 'Arlen'. As Chris also mentioned, Arno came (too)
    late to the thread and apparently has not been following the thread, so >>>>>> he was not aware that iOS *can* use servers on ports below 1024.

       AFAICT from the comments from You Guys (TM), Arno's comment on "user
    installable apps" is incorrect, because AFAIK the iOS SMB server used >>>>>> ('LAN Drive Samba server') *is* an user-installable app. Correct?
    What about his "apps without privileged access" comment?

    I stand corrected, if iOS allows user installable apps without any
    special permission using ports below 1024 as server. I was just not
    aware of that and did not expect this, since Android does not allow that >>>>> like any Linux based systems. But iOS is not Linux based and of course >>>>> it may be that Apple decided to handle that in a different way.

    iOS an unixoid system inside. It is based on Darwin, which is an open- >>>> source Unix-like operating system developed by Apple. It should have the >>>> same limitation binding to ports below 1024 for user apps. That it
    doesn't is interesting.

    Not really.

    It's not like the restriction on "privileged ports" is baked into the
    kernel...

    ...and even if it were, it could be unbaked.

    Exactly. It's really not the big deal they think it is.

    To me, it is interesting that it was unbaked, or however it was done.

    There's nothing to "unbake". There's no magic involved. It's just a policy.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Sun Apr 27 20:14:30 2025
    XPost: misc.phone.mobile.iphone

    Marion, 2025-04-25 19:06:

    On 25 Apr 2025 15:38:59 GMT, Frank Slootweg wrote :


    'LAN drive SAMBA Server Client'
    <https://apps.apple.com/us/app/lan-drive-samba-server-client/id1317727404>

    Frank is correct as I tested it myself, and unless I made a mistake in my testing (which I documented & posted like any good scientist should), that particular user-installed iOS app does appear to bind to port 445.

    Note that there is also an Android version from the same developer.
    *[APP][4.0.3+][NO Root] LAN drive Samba Filesharing Server SMB1 & SMB2*
    <https://xdaforums.com/t/app-4-0-3-no-root-lan-drive-samba-filesharing-server-smb1-and-smb2.3790945/page-12#post-90056889>

    Read the note:

    OK. So on non-rooted Android, the "Lan Drive - SMB Server" APK won't be
    able to bind to ports lower than 1024.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Sun Apr 27 20:18:28 2025
    XPost: misc.phone.mobile.iphone

    Frank Slootweg, 2025-04-25 20:41:

    [...]
    IMO, the 'no-root' philosophy of Android (and iOS?) is broken from the start. I can't access my files in Android\data etc.? I can't run a
    server on a <1024 port? Etc., etc.. But I *can* (f.e. Samsung) unlock
    the bootloader and blow everything to bits!?

    Yes - because unlocking the bootlader is not possible without wiping the device. So no risk of getting access to data for an attacker. Also this requires understanding how to install ADB and how to enter fast boot
    mode on the device and so on...


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Sun Apr 27 20:19:40 2025
    XPost: misc.phone.mobile.iphone

    Alan, 2025-04-26 04:21:

    On 2025-04-25 08:15, Arno Welzel wrote:
    Tyrone, 2025-04-25 01:54:

    On Apr 24, 2025 at 1:02:33 PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>> implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    What is a "Y.A.S.P."?

    Well - I stand corrected - so what?



    So you acted like an ass before finally realizing you were wrong.

    Huh? Why do you say that I "acted like an ass"?

    Try a little more humility next time.

    I do - all the time. I never call anyone an idiot or a troll.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Sun Apr 27 20:15:31 2025
    XPost: misc.phone.mobile.iphone

    Jolly Roger, 2025-04-25 18:00:

    On 2025-04-25, Arno Welzel <usenet@arnowelzel.de> wrote:
    [...]
    We talk about SERVERS! Which means apps which open ports below 1024 for
    INCOMING CONNECTIONS!

    My god, you trolls are fucking dumb, which is ironic considering you guys regularly claim Apple users are idiots.

    Where did I ever claim such thing?
    I NEVER(!) said, that Apple users are idiots!



    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Arno Welzel on Sun Apr 27 19:56:36 2025
    XPost: misc.phone.mobile.iphone

    Arno Welzel <usenet@arnowelzel.de> wrote:
    Frank Slootweg, 2025-04-25 20:41:

    [...]
    IMO, the 'no-root' philosophy of Android (and iOS?) is broken from the start. I can't access my files in Android\data etc.? I can't run a
    server on a <1024 port? Etc., etc.. But I *can* (f.e. Samsung) unlock
    the bootloader and blow everything to bits!?

    Yes - because unlocking the bootlader is not possible without wiping the device. So no risk of getting access to data for an attacker. Also this requires understanding how to install ADB and how to enter fast boot
    mode on the device and so on...

    Yes, I thought the same, unlocking bootloader wipes the device,
    because that was for example the case for my Huawei phone (in
    preparation of installing TWRP and later Lineage OS).

    However, someone in comp.mobile.android pointed out that (non-US)
    Samsung phones have a bootloader unlock switch in the 'Developer
    options' and indeed my Samsung (Galaxy A51) has such a switch, without
    any comments that it will wipe the device.

    However, now I'm reading it again, the wording of the off/on switch is
    a bit vague:

    "OEM unlocking
    Allow the bootloader to be unlocked <off/on switch>"

    It says it *allows* the bootloader *to be* unlocked, not that
    switching the switch to on will *actually unlock* the bootloader.

    So in hindsight, I think the switch only allows the bootloader to be
    unlocked (by whatever additional means/process) and will not actually
    unlock it.

    Anyway, I'm not going to set the switch to on to see what will happen
    or/and there will be further information/warnings.

    Bottom line: I withdraw the last sentence of my criticism, but the
    rest, especially the "Etc., etc.." bit :-), still stands.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Frank Slootweg on Sun Apr 27 20:28:12 2025
    XPost: misc.phone.mobile.iphone

    On 27 Apr 2025 19:56:36 GMT, Frank Slootweg wrote :


    However, someone in comp.mobile.android pointed out that (non-US)
    Samsung phones have a bootloader unlock switch in the 'Developer
    options' and indeed my Samsung (Galaxy A51) has such a switch, without
    any comments that it will wipe the device.

    Again I agree that Frank brings up a good point, in that I ran SuperSU (as
    I recall) many moons ago on my Samsung Galaxy S3, and, I do think I've seen that non-US A325G versions (mine is a US version) can unlock the booloader.

    Even my bootloader version would have been able to be rooted had it
    remained at subversions below around 3 or 4 or 5 (I don't recall the exact cutoff), but mine have steadily been updated from that to 6,7,8,9,A,B...
    until it's now at H.

    Note I have a thread on XDA Developers will all the gory details; but my
    point is even USA bootloaders used to be unlockable - but, alas no more.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Arno Welzel on Tue Apr 29 09:49:45 2025
    XPost: misc.phone.mobile.iphone

    On 2025-04-27 11:19, Arno Welzel wrote:
    Alan, 2025-04-26 04:21:

    On 2025-04-25 08:15, Arno Welzel wrote:
    Tyrone, 2025-04-25 01:54:

    On Apr 24, 2025 at 1:02:33 PM EDT, "Arno Welzel" <usenet@arnowelzel.de> wrote:
    [...]
    Correct - iOS also does not allow using ports below 1024 for *servers* >>>>> implemented in user installable apps without privileged access.

    Oh look. Arlen has Y.A.S.P. That's so cute.

    What is a "Y.A.S.P."?

    Well - I stand corrected - so what?



    So you acted like an ass before finally realizing you were wrong.

    Huh? Why do you say that I "acted like an ass"?

    Because you came in in the middle of a thread and didn't read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Gardner@21:1/5 to Arno Welzel on Wed May 14 11:01:48 2025
    XPost: misc.phone.mobile.iphone

    Arno Welzel <usenet@arnowelzel.de> wrote:
    Marion, 2025-04-22 04:06:

    On Tue, 22 Apr 2025 03:44:54 +0200, Arno Welzel wrote :
    [...]
    Many apps - and all have same issue: you can not open a port below 1024
    for servers without root access. And not every SMB client is able to use >>> custom ports above 1024.

    Thanks for being another voice where there are three "facts" at this point. >> 1. It turns out that iOS apps, nonjailbroken, can bind to privileged ports

    No. iOS has the same limitation. User installable apps can not use ports below 1024.

    2. Yet, we all always kind of sort of knew Android apps, nonrooted, cannot >> 3. Even so, SMB server apps exist on both iOS & Android platforms

    Yes, but only using NON STANDARD PORTS!



    This is so easy to disprove. Go to the App Store and get the app “GoFTP server” and then in its setting get it to use port 500. Connect to it from your laptop or whatever and transfer a file. I just did it then and it
    works fine.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)